With the size of hard drives these days are more then a 2-bay NAS really needed? How do you all decide how many drive bays are needed??
Thanks in advance.
I'll try to give a l the pertainent details.
I have a Lenovo Flex 4 1580 that came with a 512GB Liteon SSD. That drive failed, and I'm trying to replace it with a 1TB Sandisk SSD.
I used network PE boot to launch the restore, and then used ctrl-alt-shift to run diskpart. In diskpart, I created the two partitions on the existing drive, a 1GB WINRE_DRV partition and the remainder of the disk (I think) as a primary NTFS partition (which came out to 930GB approx).
After restoring 100% (0% remaining, more precisely), it timed out and gave this error:
[08/19/2019 00:33:04 664] RestoreHelper::FixBootBlock: fixing boot block [08/19/2019 00:33:04 664] RestoreHelper::ExtendVolume: extending the volume [08/19/2019 00:33:27 664] Restoring ESP [08/19/2019 00:33:27 664] existing offset: 0x0, size: 0x4400 [08/19/2019 00:33:27 664] existing offset: 0x4400, size: 0xfbc00 [08/19/2019 00:33:27 664] existing offset: 0x100000, size: 0x6400000 [08/19/2019 00:33:27 664] existing offset: 0x6500000, size: 0x8000000 [08/19/2019 00:33:27 664] existing offset: 0xe500000, size: 0xe891900000 [08/19/2019 00:33:27 664] Found existing volume [08/19/2019 00:33:27 664] existing offset: 0xe89fe00000, size: 0x41000000 [08/19/2019 00:33:27 664] existing offset: 0xe8e0e00000, size: 0x1fbe00 [08/19/2019 00:33:27 664] FormatPartitionEsp called for disk \\?\PhysicalDrive0 [08/19/2019 00:33:27 664] Formatting ESP partition at offset 0x8100000 [08/19/2019 00:33:27 664] ERROR: FormatPartitionEx failed, error 0x80042405 [08/19/2019 00:33:27 664] ERROR: FormatPartitionEsp failed, error 0x80042405 [08/19/2019 00:33:27 664] RestoreHelper::T_Restore: failed to restore ESP, error 0x80042405 [08/19/2019 00:33:27 664] RestoreHelper::T_Restore: restore complete with return value 536870914 [08/19/2019 00:33:27 664] ERROR: CDialog_Restore::Completed failed, HR=0x80070002 (at func: CDialog_Restore::Completed, admin\serveressentials\backup\pc\bmr\restorewizard\dialog_restore.cpp (97) I tried the instructions in Client BMR failed for UEFI machine in advanced mode , but the calculation in powershell yielded a non-integer, negative number of -2048.74120616913.
Based on the article, I'm assuming that instead of padding, I need to reduce the size of SOMETHING by 2GB, but I'm not clear how to do that so it lands on precisely the same address, particularly because of my fractional results from the powershell calculation.
Is there a way to determine the EXACT sizes for the WINRE_DRV, Windows, EFI, and MSR partitions from the backup itself. It seems odd that it handles what should be a straightforward restore so poorly (and manually). the Restore UI provides "human readable" sizes, but what is really needed are exact sizes in MB blocks, apparently.
Thanks for your assistance. This was my primary client machine and I really need it back!
I just upgraded my laptop to the latest Windows 10 1903 (18362.53) which is in release preview. The following issue may or may not be resulting from that.
My WS2012R2 Essentials server is now reporting this laptop as Offline. On the other hand the connector icon on the laptop is green, I can launch the Dashboard through it, so everything seems to be connected.
More importantly, I now cannot backup this laptop: it tries and complains that it cannot connect to the WS Essentials Client Computer Management Service. I have tried reinstalling the Connector to no avail. It used to work a couple of weeks ago, before this upgrade, but in principle it could have been some other unrelated change.
Does anyone else have a similar problem with Windows 1903? Or is it just me? Is there something I can try?
I've been banging my head for a few days now trying to figure this out and I've run out of ideas. Hoping the very intelligent crew here can help me out.
I have a Drobo 5N and a Synology RS816 on my network, both of which have been working without issue for quite some time now. I've always connected to both via Windows Explorer by simply going to the network address i.e., \\N5 and \\SYN (sample names).
I recently got a new desktop which is where the issues are coming up. When I try to go to \\N5, it results in a message saying it cannot find that location. However, \\SYN works just fine. What's strange is that I can see and manage the Drobo through the Drobo Dashboard software. What could be preventing Windows from seeing the Drobo on the network?
I've already enabled the SMB 1.x protocol, ensured the workgroup names are the same, rebooted both the machine and the Drobo, made sure network sharing is enabled, and even did a fresh install to ensure that some program I installed didn't cause the issue. Every other machine I have can access the Drobo without issue. It's just this new desktop, and everything is running Windows 10.
Another strange phenomenon that I discovered is that if I go to "\\DROBO" (verbatim, not a sample name) it leads me to the Synology. Where is Windows getting the mapping from that it is directing that address to the Synology?
This is driving me nuts so any advice would be greatly appreciated.
Currently have N40 which I used to backup my laptop to using Crashplan (as well as to Crashplan cloud), replaced Crashplan with Backblaze when CP removed consumer backup, but BB does not have a local backup.
Have a Gen8 which I am in the process of transitioning to and would like to have local/lan backup of my laptop (plus other PCs) to my server.
I have previously tried Cobien, but had issues with it backing up over a network, constant fails.
Also looked at rsync, but concerned it is very old and unsupported.
Can someone recommend software I could run on my laptop to backup to my server, would be ok with software on server to receive backup as well.
Note: I realize this isn't strictly a Gen8 issue, but as this is far and away the most popular forum I thought I'd try my luck here.
Thanks for any help/advice people can offer.