MS Server 2012 R2 BMR backup failed to complete
-
@tim_g Unable to read a sector on the OS. I tried writing to multiple usb disks and they both have the same warning. I may have discovered more info, I loaded a gparted Live CD to take a look at the partition layout of the server and received a message:
“Can’t have a partition outside the disk!”Failed to read last sector (1952800766): Invalid argument HINTS: Either the volume is a RAID/LDMbut it wasn’t’…… Unable to read the contents of the filesystem.
When I run fdisk –l I get
/dev/sdb
/dev/sda
/dev/md126
/dev/loop0Fdisk lists the Last sector of all three devices being smaller than the End Sector.
This is a SuperMicro server using Intel RAID. Two 1tb disks in a RAID 1.
I was hoping to use NTFSfix in Ubuntu to repair the NTFS partition but do not know which device I should run the command on.Should I issue the NTFSfix on the /dev/md126 device? Is that the RAID volume? Or should I perform the command on each of the /dev/sdb and /dev/sda devices?
-
@i3 said in MS Server 2012 R2 BMR backup failed to complete:
@syko24 It is a SuperMicro server with Intel Raid.
The reason I asked was there was an issue on certain HP servers where the raid controller did not properly size the disk. The fix was to go into disk management and shrink the volume a couple GB and then resize it back. Might be worth a try.
-
@i3 - just to be clear you would resize using windows disk manager not the raid controller.
-
@syko24 said in MS Server 2012 R2 BMR backup failed to complete:
@i3 said in MS Server 2012 R2 BMR backup failed to complete:
@syko24 It is a SuperMicro server with Intel Raid.
The reason I asked was there was an issue on certain HP servers where the raid controller did not properly size the disk. The fix was to go into disk management and shrink the volume a couple GB and then resize it back. Might be worth a try.
SmartArray did that? Any additional details?
-
@scottalanmiller - This is not official from HP although one of the posters mentions he got the info from HP support.
-
This was a similar situation that I ran into with a client a year or two ago. The fix was to shrink the volume a little bit and then extend it.
-
@syko24 said in MS Server 2012 R2 BMR backup failed to complete:
@scottalanmiller - This is not official from HP although one of the posters mentions he got the info from HP support.
Odd, taht thread is tough as it almost never mentions what storage platform is being used, just stuff that doesn't mean anything like the chassis model
-
@scottalanmiller - The link I posted was just something I pulled up on my phone. Again, this is something I experienced in the past and was hoping it may help resolve @i3's issue. There are a lot of similar threads out there with similar suggestions.
Here's another one. Again does not mention specific hardware but mentions HP servers:
-
Thank you to everyone who replied. So the issue was that the partition exceeded the disk layout. I ended up adding a 2TB blank disk to the system and booted into Acronis TrueImage 2014. It discovered both the RAID and the newly added disk. I performed a clone and choose the proportional option which allowed Acronis to change the partition layout on the new disk. This completed successfully. I then took out the original two WD Red drives and set them aside as an "undo" plan. I was then able to boot from the newly cloned disk and used Veeam to successfully take an image. I then inserted the 4 new disks, created the new Raid 10 virtual disk and restored the Veeam image to the Raid 10 without issue.
I realize that @Dashrender suggestion of installing the Hypervisor on the new drives would have been a better route to go, however, I am still having issues reliably managing Hyper-V Server installations in a non-domain environment. It seems like I can get it working initially, but then when I want to connect to it again from the same machine, some other part fails to connect. I feel until I can get whatever issue I am having resolved, I don't feel comfortable moving to that scenario.
-
@i3 said in MS Server 2012 R2 BMR backup failed to complete:
I realize that @Dashrender suggestion of installing the Hypervisor on the new drives would have been a better route to go, however, I am still having issues reliably managing Hyper-V Server installations in a non-domain environment. It seems like I can get it working initially, but then when I want to connect to it again from the same machine, some other part fails to connect. I feel until I can get whatever issue I am having resolved, I don't feel comfortable moving to that scenario.
It's a huge pain. If you don't want to spend time on it, then the obvious answer is to switch to KVM which is super easy. Hyper-V is a great product, but is loaded with "pain in the butt" problems to overcome that KVM does not. KVM is the super simple option that doesn't require you to fight through complexity to use it.
-
@scottalanmiller Thank you for the suggestion. I will have to look into KVM.
Thanks again!
