February 8, 201115 yr A breakdown of what happened: 1) Read about the HPA problem with Gigabyte boards and found one drive (400GB IDE drive) had an HPA on it. 2) Stopped my array and proceeded to use HDAT2 to remove the HPA (as shown here http://lime-technology.com/forum/index.php?topic=6806.0) 3) Attempted reassigned the drive back to it's original slot, but did not start the array because the option to rebuild did not appear. I assumed Unraid didn't detect that the drive had changed, so... 4) Unassigned the drive and ran a preclear to force the Unraid to recognized it as a new disk 5) Reassigned the drive back to the original slot, but Unraid just recognized it as an unformatted drive and did not rebuild the drive I have stopped the array again. There were about 3000 writes made to the parity and 400 GB drive. Have I lost the data on that drive or can I still rebuild it? My Syslog is attached. Thanks in advance! syslog-2011-02-08.txt
February 9, 201115 yr Author Bumping. I am still confused about what happened. If I precleared the drive before reassigning the disk into the array, how can Unraid think that the drive was unaltered and not rebuild the disk?
February 9, 201115 yr Bumping. I am still confused about what happened. If I precleared the drive before reassigning the disk into the array, how can Unraid think that the drive was unaltered and not rebuild the disk? It is still the same model/serial number and size. It will not overwrite it since it thinks it might have your data. To get it to forget the old model/serial number, you need to start the array with the slot un-assigned, then stop the array re-assign the disk, and start it again. Starting the array with the slot un-assigned will cause it to forget the old disk's model/serial. when you re-assign it, unRAID will think it is a different drive and re-construct onto it.
February 9, 201115 yr Author There were multiple reboots between when I unassigned the disk, when I precleared it, and when I reassigned it. I was rebooting because a) I was also battling with a failing 2TB EARS drive and b) because I needed to run HDAT2 to remove the HPA infection from the 400 GB drive in question. Also, if I successfully removed the HPA crap from the disk, the disk size should appear larger to Unraid. I confirmed that I did remove the HPA crap via HDAT2 and by comparing the outputs from "hdparm -i -I /dev/hdb." I will give it another reboot just in case though. I have been sifting through the syslog (attached to my first post) and at 12:31:10 I reassigned the 400 GB disk as "Disk 5". At 12:31:46 things appear to turn sour and a mount error occurs: Feb 8 12:31:46 Tower kernel: mdcmd (13): check Feb 8 12:31:46 Tower kernel: md: recovery thread woken up ... Feb 8 12:31:46 Tower emhttp: shcmd (30): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md1 /mnt/disk1 2>&1 | logger Feb 8 12:31:46 Tower kernel: md: recovery thread has nothing to resync Feb 8 12:31:46 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md5, Feb 8 12:31:46 Tower logger: missing codepage or helper program, or other error Feb 8 12:31:46 Tower logger: In some cases useful info is found in syslog - try Feb 8 12:31:46 Tower logger: dmesg | tail or so Feb 8 12:31:46 Tower logger: Feb 8 12:31:46 Tower emhttp: _shcmd: shcmd (30): exit status: 32 Feb 8 12:31:46 Tower emhttp: disk5 mount error: 32 Feb 8 12:31:46 Tower emhttp: shcmd (31): rmdir /mnt/disk5 Could this have anything to do with my problem? In the mean time I'll go ahead and try unassigning the disk, rebooting, and reassigning.
February 9, 201115 yr Author I tried unassigning, powering down, powering up, reassigning. The disk was accepted with no option to rebuild the disk. What do I do now?
February 10, 201115 yr Author Wanted to post an update. I repeatedly assigned/started/stopped/unassigned (without rebooting) and out of the blue the option to rebuild disk 5 came up. I'm not sure how/why, but I'm now rebuilding the disk. I guess this issue is close, although I don't know why it didn't work the first 9 or 10 times I tried it?!? I'm sure the answer is in the syslog I posted, but it's way beyond my unraid knowledge. Thanks Joe L. for your help.
February 10, 201115 yr Wanted to post an update. I repeatedly assigned/started/stopped/unassigned (without rebooting) and out of the blue the option to rebuild disk 5 came up. I'm not sure how/why, but I'm now rebuilding the disk. I guess this issue is close, although I don't know why it didn't work the first 9 or 10 times I tried it?!? I'm sure the answer is in the syslog I posted, but it's way beyond my unraid knowledge. Thanks Joe L. for your help. You must Start the array with the disk un-assigned for it to forget the model/serial number. Simply un-assigning and then re-assigning is not enough. The sequence is Stop the array Un-assign the drive Start the array Stop the array RE-assign the drive Start the array (it will offer to rebuild) You must have hit that sequence, so it offered to re-construct onto the same disk. Joe L.
February 10, 201115 yr Author I could have sworn I did that too, but I guess the fact that it didn't rebuild shows that I didn't! Sorry for wasting your time, I'm an idiot!
Archived
This topic is now archived and is closed to further replies.