October 31, 20178 yr So I was 40% into rebuilding a drive I recently upgraded when another drive threw an error. I know now it was because of a loose cable and the drive is fine but it now has a red X. I only have one parity drive what is the best procedure around this? Do I start the array with both the drives set to no device then start them again the normal procedure or is all hope lost? I just want to get it to the state where it can start rebuilding the first drive again. Any help will be great! Fun in part is my second parity drive is currently being precleared on another machine. Ugh. Plan is to upgrade from these Marvell cards as well but have to save up.
October 31, 20178 yr Author 2 hours ago, johnnie.black said: Post your diagnostics. Here you go diagnostics-20171031-0634.zip
October 31, 20178 yr Community Expert Lots of Marvell controllers, there are ATA errors on disks 7 and 16, just a couple, but array is not even started, so not very encouraging... As to re-enable the disable disk, and assuming array data is static since the beginning of the rebuild, you can try this: -Tools -> New Config -> Retain current configuration: All -> Apply -if needed assign any missing disk(s), all disks should be assigned, including the disable disk3 and new disk9-check both "parity is already valid" and "maintenance mode" before starting the array -start the array -stop array, unassign disk9 -start array, check emulated disk9 mounts and contents look correct -stop array, reassign disk9 -start array to begin rebuild Hope there are no more errors during the rebuild and get rid of those Marvell controllers ASAP.
October 31, 20178 yr Author 2 minutes ago, johnnie.black said: Lots of Marvell controllers, there are ATA errors on disks 7 and 16, just a couple, but array is not even started, so not very encouraging... As to re-enable the disable disk, and assuming array data is static since the beginning of the rebuild, you can try this: -Tools -> New Config -> Retain current configuration: All -> Apply -if needed assign any missing disk(s), all disks should be assigned, including the disable disk3 and new disk9-check both "parity is already valid" and "maintenance mode" before starting the array -start the array -stop array, unassign disk9 -start array, check emulated disk9 mounts and contents look correct -stop array, reassign disk9 -start array to begin rebuild Hope there are no more errors during the rebuild and get rid of those Marvell controllers ASAP. Definitely will, just needing to do more research on what to replace it with and if it will work with my mother board. Just checking will this erase disk3 or keep contents intact and rebuild disk 9 only?
October 31, 20178 yr Community Expert Just now, Wavey said: Just checking will this erase disk3 or keep contents intact and rebuild disk 9 only? Disk3 will have the same data it had when it was disabled.
October 31, 20178 yr Author 56 minutes ago, johnnie.black said: Disk3 will have the same data it had when it was disabled. Perfect. Thank you. It restarted, my files all seem to be there and the drives being written to but the only difference now is that it says unmountable, is that a problem? Any more steps I should take after it’s done rebuilding? PS it was the Marvell card. Tried plugging another drive in and no bueno. I really wish sata expanders were a common thing that you could easily buy for your mother board. Looking into LSI and other stuff and it all seems to need special flashing or costs $500+.
October 31, 20178 yr Community Expert 1 hour ago, johnnie.black said: -start array, check emulated disk9 mounts and contents look correct If the disk9 doesn't mount it would be better to try and fix the filesystem before rebuilding, as there's no point in rebuilding if it's not fixable, but you can still let the rebuild finish and then run xfs_repair or cancel the rebuild and run it now. https://wiki.lime-technology.com/Check_Disk_Filesystems#Drives_formatted_with_XFS
October 31, 20178 yr Author 19 minutes ago, johnnie.black said: If the disk9 doesn't mount it would be better to try and fix the filesystem before rebuilding, as there's no point in rebuilding if it's not fixable, but you can still let the rebuild finish and then run xfs_repair or cancel the rebuild and run it now. https://wiki.lime-technology.com/Check_Disk_Filesystems#Drives_formatted_with_XFS Sorry for the mixup it’s disk3 that says it’s unmountable. It’s still rebuilding and even has a ETA but I wasn’t sure if I should let it keep doing it or stop it. Disk9 is perfectly fine. Sorry you were right it’s disk 9 that’s unmountable disk3 is fine. Edited October 31, 20178 yr by Wavey Sorry I’m an idiot
October 31, 20178 yr Community Expert As you prefer, but since it's being going for some time might as well let the rebuild finish, only then run xfs_repair, if parity was valid it should be fixable.
October 31, 20178 yr Author 12 minutes ago, johnnie.black said: As you prefer, but since it's being going for some time might as well let the rebuild finish, only then run xfs_repair, if parity was valid it should be fixable. It was only at 1% so I ended up stopping it and running xfs repair, it told me to run -L and I did. It’s now mountable and back at rebuilding. Thanks for all the help.
Archived
This topic is now archived and is closed to further replies.