moguiyu

I have all docker vm turned off. But it still spin up. And checked no file is active.

Tried everything but still fail. Now waiting for Sinologist discount and switch to synology

they are just most common sata disks, I did not use spindown plugin, attached are the diagnose file. now i have removed the Toshiba disks with only HGST/ST disk installed. m17-diagnostics-20220801-2150.zip

Thank you very much for sharing the experience, the following scenarios were all tried: 1. turn off vm/docker, smb service. 2. running in maintenance mode. no usb other than the system is mounted. the disks(HGST/Seagate 4TB) that are not comes with the dell T130 server are spinning up; the disk (Toshiba 1T oemed) came with the server works fine which spin off normally. so i wonder if it is disk controller compatability issue?

This solution unfortunately did not help us which i tried twice before: turn off both the docker and VM then triggered the mover, but the disks are still read smart. i also used all these 3 apps to track, there is no sign of disk use or file read. but i did checked some spindown-read smart intervals and find out it usually take 5min'38 sec and average is around 350 second. which looks like some system level thing triggered this instead of application. any guys have ideas how to dig?

thanks for sharing this. after stop docker and start mover, twice, the OS still reads SMART to wake up the disks. very unfortunately. i wonder if it is because it is dell server only can get info from authorized disks, cause the embeded disks was fine, only the new disks keeps reading smart.

unfortunately this does not work for me...

nope, Im already check rack for hiding the disk noise... unfortunately.

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.

thanks, this is without rebooting. new diagnostics of non-correcting parity check. m17-diagnostics-20211210-0900.zip

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

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.

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.

I have tried safe mode, without any docker or plugin or vm. 2 disks formatted in GPT are still spin up. other disks formatted in MBR does spin down correctly.

I have turn off the scan long time ago. does not help. I even turn off all VM docker. still spin up. there must be bug.