-
Changing data Disks with 4 parity check errors
Thank you all you guys for the comments, I think I have not explain it well. I was following this instruction: upgrading the 1TB data drive to 4TB data drive. the parity disk was not changed at all. I was using the rebuild process to fill the new disk with data, just the parity check shows 4 errors, I'm not sure if I should be very worried about the error. the 2nd time when I did the parity check, it show 0 errors now.
-
Changing data Disks with 4 parity check errors
thanks, this is without rebooting. new diagnostics of non-correcting parity check. m17-diagnostics-20211210-0900.zip
-
Changing data Disks with 4 parity check errors
thank you for the explanation. yes, I only format before I assign the disk of course. my question is still do I need to worry about the 4 errors? anyway to check what exactly the error is about? I'm attaching diagnostic file. m17-diagnostics-20211209-0849.zip
-
Changing data Disks with 4 parity check errors
yes, you are right, I meant 'assign'. it was a new disk, so it need to be formatted before I can use it for anything. yes, the disk I changed was data disk, not a parity disk.
-
Changing data Disks with 4 parity check errors
Hi Experts here: I'm using unraid for more than a year but still new to it. today I had to change my 1TB data disk to a 4TB one by swapping it.(no additional ports to add). the steps I took was turn off the server, replace the disk; turn on the server and format the new disk, then mount Assign the new disk to replace the old and start the parity rebuild process. after around 9 hours parity recovery data rebuild, the array is working with error saying 4 errors. should I worry about it? what should I do to check? cause I still have another 1TB data disk need to change to 4TB one thank you very much in advance for your kind answer.
-
-
[6.9.2] emhttpd: read SMART keeps disks spin up
Dear all, I've been trying to figure out why 2 of my disks keep awake: (No docker/VM running, Tunable (md_write_method): is auto) Fall back to 6.9.1: noticed that the WebUI shows the disk already spin down, but in reality the disks are still spinning. Upgrade to 6.9.2/6.10.0-rc1, shows the spin up/down correctly, but disks keep reading SMART to awake disks, see pic 2. https://forums.unraid.net/topic/106508-advanced-disk-spindown/, I also tried this solution. it didi not help. my findings: 2 spin up disks are HGST 4tb, format in GPT, see pic 4. 2 spin down disks are Toshiba 1TB, format in MBR, see pic 3. this is all my findings, really struggled by this issue for a long time, not sure if Unraid is good solution any more. could anyone gives some suggestions how to troubleshoot? any other NAS solution to recommend? pic 1: 2 Hitachi disks keeps UP all the time. Pic 2: Disks keep reading SMART
-
[SOLVED] Spinning down
6.9.2 turned off all VM and docker. Jul 11 23:16:39 M17 emhttpd: spinning down /dev/sde Jul 11 23:17:28 M17 emhttpd: read SMART /dev/sde Jul 11 23:32:04 M17 emhttpd: spinning down /dev/sde same problem here. the disk is format in GPT instead of MBR, this is the only difference compare to other sleeping disks
moguiyu
Members
-
Joined
-
Last visited