March 11, 201610 yr Hi, First of all sorry for my english its not my main language. I recently build a new server. Everything seemed ok. I moved all my disk to the new server everything was working perfectly. No data loss. Parity check no error In the new build I bought a new bigger disk to replace my parity. Pre-cleared it during the week and eveything went fine no error. This morning I made the switch. - Stopped the array - Assigned the new disk (3TB Toshiba) as parrity - Old parrity (2TB WD Red) Un-assigned for future pre-clear to add it as a data disk - Parity Sync - Parity check : lost 4 disk (unreadable) had like 1 500 000 000 error on my first 4 disk that are all on the same controller. I stop the check and the 4 disk disapear (disconnected) Restart the server and the 4 disk came back. Righ now my data 1 have a red X. (smart test ok) all the other disk are there and I can read from them. Really afraid to loose everything right now. Checked everything, cable, bios all the disk are there. What to do ? Plug back my old parity disk with the backup of my usb ? Information on my server : Unraid 6.19 Plus - Xeon e5 2670 (dual) - Asrock EP2C602 - 32GB ecc - 3 x WD red 2TB - 3 x Toshiba 2TB - 1 x Toshiba 3TB Thank you for your help.
March 11, 201610 yr Author Here is my syslog when I lost 4 disk Can it be caused by a bad controller? Good timing to crash when you upgrade your parity.. syslog.txt
March 11, 201610 yr If I’m understanding correctly, the problem happened during the parity check, after the parity sync, so you’re new parity is valid, correct? If that’s the case, and assuming that 4 disks dropping at the same time was a controller/cable issue and you think that’s resolved you can do a new config: -take a screenshot of current assignments -stop array, go to tools and click new config -re-assign all disks, double ckeck parity is on the parity slot -before starting array check “parity is already valid” -start array *edited to add*-check that all disks mount and data is available -start a new parity check to make sure parity is in sync Don’t preclear your old parity and don’t write anything to the array until this is resolved.
March 11, 201610 yr Just to add that before starting the parity check at the end make sure disk1 mounts, i.e., you can see its content.
March 11, 201610 yr Author Thanks for your reply, The errors were there after the parity sync Can I do the same procedure?
March 11, 201610 yr That’s what I understood: ... the problem happened during the parity check, after the parity sync, so you’re new parity is valid, correct? You replaced your parity and completed the parity sync. You then started a parity check and the issue occurred, correct?
March 12, 201610 yr Author At the end of the parity sync I saw errors next to the drive on the same controller. So to fix those errors I started a parity check. At that time I didn't suspects faulty controller.. So there was error at the end of parity sync and parity check. Can I fix the faulty disk1 if parity sync had errors? I know it's not a bad drive when disk is detected Smart is good.
March 12, 201610 yr In that case the current parity can’t be trusted, you need to do a new parity sync, procedure is similar: 1-take a screenshot of current assignments 2-stop array, go to tools and click new config 3-re-assign all disks, leave the parity slot empty for now 4-start array, check that all disks mount and all data is available 5-if all looks ok, stop array and assign parity 6-start array to begin parity sync If the parity sync doesn’t complete without errors, go to tools and click diagnostics, attach full zip. Keep your old parity intact and don’t write/modify anything on the array until the new sync finishes successfully.
March 12, 201610 yr Before you do anything, shutdown the server, remove the power cable and remove and replug ALL the drives/controllers/SATA/Power cables. Sounds like the infamous bumped a cable while putting a new drive in error
March 13, 201610 yr Author In that case the current parity can’t be trusted, you need to do a new parity sync, procedure is similar: 1-take a screenshot of current assignments 2-stop array, go to tools and click new config 3-re-assign all disks, leave the parity slot empty for now 4-start array, check that all disks mount and all data is available 5-if all looks ok, stop array and assign parity 6-start array to begin parity sync If the parity sync doesn’t complete without errors, go to tools and click diagnostics, attach full zip. Keep your old parity intact and don’t write/modify anything on the array until the new sync finishes successfully. Thank you for your help! I'm doing right now. We will see the result in 6 hours.
Archived
This topic is now archived and is closed to further replies.