Hi, Jason. Please also include support case ID for this issue, as requested when you click New Topic - as we need access to debug logs as well. Thanks!
You cannot mount your extended partition because in fact it's not a partition at all, but a container for your logical partitions (which are sda5, sda7, sda8, I guess).
You can see that your sda5 starts almost at the same point as sda2 (okay, there is a 2 sectors offset, who cares):
Thanks PTide, but I guess I wasn't entirely clear. I understand why the FLR can't mount sda2 (and therefore why restores work fine); I was curious why the FLR was telling me it couldn't, since my expectation would be that message would be suppressed. (Which is why I didn't open a support ticket because it's not really an issue.)
Normally I wouldn't even bother about something like that, but we are finishing up our evaluation of Veeam (quitting BE). Our most critical server is a Linux box and my boss is really uptight about backups on it, so anything that indicates it isn't 100% okay stresses him out.
mcsmithSOP wrote:(Which is why I didn't open a support ticket because it's not really an issue.)
Well, it is most certainly an issue (looks like a bug to me if we attempt to mount what is not a valid partition). However, without a single support case open it will be very challenging for us to move this forward to the resolution...
Gostev wrote:Well, it is most certainly an issue (looks like a bug to me if we attempt to mount what is not a valid partition). However, without a single support case open it will be very challenging for us to move this forward to the resolution...
Due to the nature of how we back up, meaning image of VM, when we bring up in FLR appliance, we will present all that disks and its partitions that were backed up. Even if we decided to restore just the disk. we will still bring up all it's partitions. Now I can suggest you enter our forums and submit an feature request.
But at this time that is how our software is designed to run.
To be honest, it's not that big of a deal (to me) to bother putting in a feature request because I am sure there are many other more important things for the team to work on.
We are already discussing this issue with the devs and if it's possible to adjust the appliance not to mount this type of partitions at all (or at least if we could enhance error handling in the UI). Any support issue that is easy to fix, we try to address without looking back at other factors. Only when something appears hard to fix or change, then we will start also considering priority and importance.