September 28, 20169 yr Hi all I had a bit of a nightmare when attempting to upgrade at the weekend To cut a long story short, i'm now in the following situation - I have unraid v6.2 up and running, but I stupidly don't have my original drive config available and I don't want to mess it up in case I lose everything! I know what the parity drive is but i'm not 100% sure on the ordering of the original drives other than 1 of the 6 in the array. My biggest worry is that disk5 is 'unmountable' for some reason so i don't want to start it up and lose it. In the current config I have everything assigned except for the parity and I can see most of my data. If I start the parity as 'valid' with a new config, am I going to be OK? Will I be able to recover the 'unmountable' drive?
September 28, 20169 yr Author diagnostics should hopefully be attached! tower-diagnostics-20160928-1331.zip
September 28, 20169 yr Community Expert First thing to understand is that doing a rebuild won't fix the file system, ie, the rebuilt disk will have the same issue. I assume the 3TB disk is your parity, and as long as you know which one is parity you're OK, data disk order is not important for single parity (it is for dual parity), so you should assign parity, check "parity is already valid" and start the array, so you don't remain unprotected. After that you can deal with the unmountable disk, you need to start the array in maintenance mode and run reiserfsck on that disk: https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_ReiserFS_using_unRAID_v5_or_later
September 28, 20169 yr Johnnie -- what 3TB drive? The super.dat shows 6 2TB drives (all WD20EARS) olicollett => Assign ALL SIX of the drives to the array as data drives (i.e. NO parity) and see if you have more than one "unmountable" drive. If not, then you were wrong about which one was parity -- the unmountable drive is your parity drive; the others are the data drives. If that indeed seems to be the case, then do a New Config and assign the 5 drives that ARE mountable to the array (still no parity) ... and then Start the array and confirm you can see all your data okay. THEN assign the last drive as parity and let it do a new parity sync.
September 28, 20169 yr Author First thing to understand is that doing a rebuild won't fix the file system, ie, the rebuilt disk will have the same issue. I assume the 3TB disk is your parity, and as long as you know which one is parity you're OK, data disk order is not important for single parity (it is for dual parity), so you should assign parity, check "parity is already valid" and start the array, so you don't remain unprotected. After that you can deal with the unmountable disk, you need to start the array in maintenance mode and run reiserfsck on that disk: https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_ReiserFS_using_unRAID_v5_or_later Thanks for the help! Just to confirm there was a 3tb drive, i had two unmountable on startup, hence why I knew there was an issue I've run a check and have the following results ########### Replaying journal: No transactions found Checking internal tree.. block 433339039: The level of the node (46872) is not correct, (4) expected the problem in the internal node occured (433339039), whole subtree is skipped finished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 1 found corruptions can be fixed only when running with --rebuild-tree So looks like that's my only option?
September 28, 20169 yr Community Expert So looks like that's my only option? Yep, run with --rebuild-tree
September 28, 20169 yr I thought all the drives were shown in super.dat ... apparently that's either not the case or I'm missing something. Clearly with a 3TB drive that HAS to be the parity drive ... so you indeed need to either rebuild the drive with Reiserfsck or restore the data for that drive from your backups.
September 28, 20169 yr Community Expert It's currently unassigned, so it doesn't show up on super.dat
September 28, 20169 yr I would do this a bit differently than what Johnnie suggested... Instead of doing the corrections within a protected array, I would create a one-drive array with ONLY the defective drive ... and then run Reiserfsck on that drive with the rebuild tree option. Why? ... because if for some reason that doesn't work, you could then do a New Config with all of your original drives and the "parity is already valid" option, and do a rebuild of that drive => which MAY (depending on when the corrupted occurred) put you in a better situation for recovery. Note that if you're already been making changes within a protected array it's too late to do that, as parity has already been update to reflect what you've done already, and thus is no longer "valid" r.e. the way things were before.
September 28, 20169 yr Community Expert Your current disk2 doesn't look very healthy, you may want to replace it, at the very least run an extended SMART test. Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA1821372 5 Reallocated_Sector_Ct 0x0033 186 186 140 Pre-fail Always - 277 196 Reallocated_Event_Count 0x0032 001 001 000 Old_age Always - 274 197 Current_Pending_Sector 0x0032 196 196 000 Old_age Always - 1459 This one has a lot of CRC errors, this is usually a bad SATA cable, but it can be old errors, so monitor it for a couple of weeks and if it keeps increasing replace cable. Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA1693352 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 67740
September 28, 20169 yr Community Expert Instead of doing the corrections within a protected array, I would create a one-drive array with ONLY the defective drive ... and then run Reiserfsck on that drive with the rebuild tree option. This is a good idea if you think your parity is not in sync and corruption happened while not using parity, my advice assumes parity is in sync. Edit: Though if disk2 is as bad as it looks a perfect rebuilt will not be possible.
September 28, 20169 yr Author ah, i've already kicked off the rebuild-tree so a bit late for other options! There wasn't anything super important on any of the drives so if i do lose some of the disk i'm rebuilding it's not the end of the world. The corruption shouldn't have happened out of sync - i do wonder if that disk had been in some kind of failed state for a while though. I probably hadn't checked on it in the past year as i've not been using the server for long, I was looking at upgrading on sunday so that i could look at running Plex or some other services from there.
September 28, 20169 yr ... I probably hadn't checked on it in the past year as i've not been using the server for long, I was looking at upgrading on sunday so that i could look at running Plex or some other services from there. Did you run a parity check before starting the upgrade? I gather from this comment that the answer is likely No ... in which case I would definitely NOT check the "parity is already valid" box. If you did that, I would do a New Config after the rebuild-tree completes and generate a new parity sync, so you'll at least have a known-good parity and the array will be protected for any future work you do on it.
September 28, 20169 yr Author ... I probably hadn't checked on it in the past year as i've not been using the server for long, I was looking at upgrading on sunday so that i could look at running Plex or some other services from there. Did you run a parity check before starting the upgrade? I gather from this comment that the answer is likely No ... in which case I would definitely NOT check the "parity is already valid" box. If you did that, I would do a New Config after the rebuild-tree completes and generate a new parity sync, so you'll at least have a known-good parity and the array will be protected for any future work you do on it. My approach to the upgrade was.. shambolic It looks like the rebuild will take some time so I'll leave it be and revisit tomorrow or friday - I've not touched the array and don't need to use it right now so I can re-sync after as you suggest
September 29, 20169 yr One great thing about v6 is Notifications, so make sure they are turned on, and you can be notified of anything wrong, with the system as a whole, and the health of each drive. You want to know as soon as possible if a drive is starting to fail.
September 30, 20169 yr Author Just a quick update - currently doing a parity sync after doing the rebuild tree. There's a fair few files in lost and found which are worth restoring which i'll look at sorting after the parity sync is complete. I'm then going to switch out drive 2 as there are indeed a lot of errors! Thanks again for all the help!
Archived
This topic is now archived and is closed to further replies.