March 24, 201115 yr Thanks Joe--here's the output of the command given: Deed login: root Password: Linux 2.6.32.9-unRAID. root@Deed:~# dd status=noxfer count=1 if=/dev/sdh | od -Ad -t x1 0000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1+0 records in 1+0 records out * 0000512 root@Deed:~# ouch... There is no partition table. The MBR is completely blank. Easiest thing to try. Unplug that drive from the array (or, even easier, un-assign it on the "devices" page), see if the array will start without it. If it does, and you can get to the "re-constructed" files on it, we can try putting the MBR back to is intended form. Did you write zeros to it (or rather, did you knowingly write to its MBR?) did you issue any manual "dd" commands to write to your disks?
March 24, 201115 yr Author Thanks Joe--here's the output of the command given: Deed login: root Password: Linux 2.6.32.9-unRAID. root@Deed:~# dd status=noxfer count=1 if=/dev/sdh | od -Ad -t x1 0000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1+0 records in 1+0 records out * 0000512 root@Deed:~# ouch... There is no partition table. The MBR is completely blank. Easiest thing to try. Unplug that drive from the array (or, even easier, un-assign it on the "devices" page), see if the array will start without it. If it does, and you can get to the "re-constructed" files on it, we can try putting the MBR back to is intended form. Did you write zeros to it (or rather, did you knowingly write to its MBR?) did you issue any manual "dd" commands to write to your disks? Success! I removed sdh from the devices page and was able to start the array successfully. I have never issued any manual command to my disks. I've only used screen to preclear them and a couple of times just let unraid handle it as I didn't mind the downtime. Thanks for helping me get back to this point Joe. What's my next step? I was only using about 35% of my array's capacity so there's a chance there's nothing on that drive...but I'm not sure.
March 24, 201115 yr you can browse to that disk share and see what is on it. What you see is what is being simulated and reconstructed from the other disks in your array. (assuming you un-assigned the disk) easiest way to recover is to re-assign the disk and start the array once more. It will re-construct the disk onto itself. If you un-plugged the drive instead of un-assigning it, you'll need to un-assign it, start the array with it un-assigned, then stop the array and re-assign it. (and plug it back in too) Joe L.
March 25, 201115 yr Author Array rebuilt successfully without problems. Added disk and everythings working as expected. Thanks again all!!
Archived
This topic is now archived and is closed to further replies.