johnnya1306 Posted May 13, 2017 Share Posted May 13, 2017 Hi, Started parity rebuild with freshly precleared, new WD 4Tb RED last night. Woke up to what looked like an array disk showing I/O errors and parity build slowed to a crawl (xx.x Kb/sec). Syslog zip attached, sent here by "Fix Common Problems". I know my disks are old but they all passed preclear (I'm upgrading from WHS v1). Still have last good parity disk which was being replaced but system won't recognize as such. Restarted parity rebuild after stopping to investigate. What do I need to do to get to next stable point? Thanks in advance for any help, John tower-diagnostics-20170513-0613.zip Link to comment
JorgeB Posted May 13, 2017 Share Posted May 13, 2017 Disk13 needs replacing: Device Model: SAMSUNG HD204UI Serial Number: S2H7J9BB104868 197 Current_Pending_Sector 0x0032 077 077 000 Old_age Always - 2851 Link to comment
johnnya1306 Posted May 13, 2017 Author Share Posted May 13, 2017 OK, thanks! I'm working on replacing them all. Not sure how to go about it. The system won't recognize the old parity disk and I can't complete a new parity rebuild. I have new drives available and the old parity drive. Link to comment
JorgeB Posted May 13, 2017 Share Posted May 13, 2017 7 minutes ago, johnnya1306 said: I have new drives available and the old parity drive. Was anything written (or any change) to the array after removing the old parity? Link to comment
johnnya1306 Posted May 13, 2017 Author Share Posted May 13, 2017 Just installed Krusader but haven't touched the array. Link to comment
JorgeB Posted May 13, 2017 Share Posted May 13, 2017 Since you're not using cache the docker files are on the array, so there were changes and old parity is not valid anymore, you can still use it to rebuild disk13 but there will be some corrupt files. Link to comment
johnnya1306 Posted May 13, 2017 Author Share Posted May 13, 2017 When I first stopped the rebuild, before doing anything, I put the original parity disk back. It wasn't recognized as the original (valid) parity disk. How do I use the original parity disk to restore the array? Won't it just effectively "uninstall" Krusader? Link to comment
JorgeB Posted May 13, 2017 Share Posted May 13, 2017 4 minutes ago, johnnya1306 said: Won't it just effectively "uninstall" Krusader? No, krusader will remain installed and because of it and any other changes old parity is no longer valid, disk13 looks really bad so you can still try a rebuild using the old parity and then replace all files you can copy from the old disk. To do it you need to do a new config (select retain all disks) with the old parity and current disk13, check the box "parity is already valid" before starting the array, start array, stop array, power down, replace disk13, power back up, assign new disk, start array to begin rebuild. Link to comment
johnnya1306 Posted May 13, 2017 Author Share Posted May 13, 2017 There isn't a "parity is already valid" box. Only "replacement disk installed" Link to comment
JorgeB Posted May 13, 2017 Share Posted May 13, 2017 You need to do a new config, tools -> new config -> retain all disks Then assign old parity and don't forget to check the box before starting the array. Link to comment
johnnya1306 Posted May 13, 2017 Author Share Posted May 13, 2017 OK, great, Thanks! Gotta preclear new drive first. Uncheck "write corrections to parity" before rebuild, right? Link to comment
JorgeB Posted May 13, 2017 Share Posted May 13, 2017 7 minutes ago, johnnya1306 said: Uncheck "write corrections to parity" before rebuild, right? That option won't be available before a rebuild, it's only for parity checks. Link to comment
johnnya1306 Posted May 14, 2017 Author Share Posted May 14, 2017 Should I uninstall Krusader before rebuild? Link to comment
JorgeB Posted May 14, 2017 Share Posted May 14, 2017 It doesn't matter now, leave it be. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.