Could not read MBR. Error message: CreateFile of Volume 'F'... But there is no volume F!

1

My UrBackup server runs Linux and has about 9TB of storage. Five servers (all but one are Windows Server 2008) backup just fine. One Windows Server 2008 does not backup, though.

It appears UrBackup is trying to do something with volume F, but there is no such volume!

Screenshot - 4_18_2016 , 11_21_22 AM.PNG797×107 62.3 KB

Screenshot - 4_18_2016 , 11_19_19 AM.PNG785×170 68.6 KB

This is the debug.log file:

2016-04-15 10:32:29: WARNING: Upgrading…
2016-04-15 10:32:29: ERROR: Error preparing Query [SELECT tvalue FROM misc WHERE tkey=‘db_version’]: no such table: misc
2016-04-15 10:32:32: ERROR: Error preparing Query [DROP INDEX filehashes_idx]: no such index: filehashes_idx
2016-04-16 03:19:50: ERROR: CreateFile of volume ‘F:’ failed. - sendMBR. Errorcode: 2
2016-04-16 03:19:50: ERROR: GetVolumePathName(dir.target, volume_path, MAX_PATH) failed
2016-04-16 03:19:50: ERROR: Creating shadowcopy of “F:” failed.
2016-04-16 03:19:50: ERROR: Creating Shadow drive failed. Stopping.
2016-04-16 04:00:01: ERROR: CreateFile of volume ‘F:’ failed. - sendMBR. Errorcode: 2
2016-04-16 04:00:01: ERROR: GetVolumePathName(dir.target, volume_path, MAX_PATH) failed
2016-04-16 04:00:01: ERROR: Creating shadowcopy of “F:” failed.
2016-04-16 04:00:01: ERROR: Creating Shadow drive failed. Stopping.
2016-04-16 05:20:12: ERROR: CreateFile of volume ‘F:’ failed. - sendMBR. Errorcode: 2
2016-04-16 05:20:12: ERROR: GetVolumePathName(dir.target, volume_path, MAX_PATH) failed
2016-04-16 05:20:12: ERROR: Creating shadowcopy of “F:” failed.
2016-04-16 05:20:12: ERROR: Creating Shadow drive failed. Stopping.
2016-04-16 08:00:23: ERROR: CreateFile of volume ‘F:’ failed. - sendMBR. Errorcode: 2
2016-04-16 08:00:23: ERROR: GetVolumePathName(dir.target, volume_path, MAX_PATH) failed
2016-04-16 08:00:23: ERROR: Creating shadowcopy of “F:” failed.
2016-04-16 08:00:23: ERROR: Creating Shadow drive failed. Stopping.
2016-04-16 13:20:35: ERROR: GetVolumePathName(dir.target, volume_path, MAX_PATH) failed
2016-04-16 13:20:35: ERROR: Creating shadowcopy of “F:” failed.
2016-04-16 13:20:35: ERROR: Creating Shadow drive failed. Stopping.
2016-04-16 13:20:35: ERROR: CreateFile of volume ‘F:’ failed. - sendMBR. Errorcode: 2
2016-04-16 21:48:29: ERROR: CreateFile of volume ‘F:’ failed. - sendMBR. Errorcode: 2
2016-04-16 21:48:31: ERROR: GetVolumePathName(dir.target, volume_path, MAX_PATH) failed
2016-04-16 21:48:31: ERROR: Creating Shadow drive failed. Stopping.
2016-04-16 21:48:31: ERROR: Creating shadowcopy of “F:” failed.
2016-04-17 19:08:36: ERROR: CreateFile of volume ‘F:’ failed. - sendMBR. Errorcode: 2
2016-04-17 19:08:36: ERROR: GetVolumePathName(dir.target, volume_path, MAX_PATH) failed
2016-04-17 19:08:37: ERROR: Creating shadowcopy of “F:” failed.
2016-04-17 19:08:37: ERROR: Creating Shadow drive failed. Stopping.

2

Double-check your backup settings on either your client or on your web-interface and make sure that (F:) is not specified to be backed up for that server.

3

Ok, for all of them I used the ALL_NONUSB. But I am overriding that client’s settings with just C,D to see if it will work.

4

If this works:

That is strange how ALL_NONUSB works for all your other clients except this one; however, if it was working before and then it stopped there should be an explanation.

Have you attached any other drives to this machine recently - USBs (shouldn’t have done anything with ALL_NONUSB), network mapping, new partitions, or otherwise?

5

I haven’t recently, but prior to installing UrBackup a week ago, each of the servers had a directly attached SCSI external drive with that drive letter. I wonder if Windows is just providing some misleading device info to the UrBackup Client app on this particular server. Should clear up after a reboot if so, which is what I was thinking about doing tomorrow AM.

6

It enumerates the drives once after booting and then does not refresh that information so rebooting should indeed fix the problem.

Edit: Hmm ok you said it was only attached prior to installing UrBackup…

7

Yeah, that’s why I’m thinking maybe there is a glitch in the OS that would be refreshed by a reboot. Then UrBackup would enumberate the drives and not find the phantom drive letter maybe? Just thinking.

8

Worth a shot; you have nothing to lose but some down-time by bringing down the server…

9

All is well.

Adding just C and D allowed for a backup that evening. I was able to reboot the next morning, after which time I removed the custom client config and switched it back to ALL_NONUSB. But after the reboot that worked as well.

Thank you for the support!