vanarebane

That is unfortunate. For the record, I have used both Toshiba MG06ACA800E SATA and the SAS version. The SATA versions did spin down normally without the SAS plugins help. but I did have many Disk failures over three months until the whole array failed with data loss. I figured the SATA drives were old and found a deal on SAS drives that just happened to be the same build and those SAS drives had also disk failures (I managed to include those disks in the SAS spin down plugin) and after removing that plugin, the disks have not failed once. I can only hope that Unraid team sees the need to rework the Unraid internally in the future, but if this is only for old disks I can see that it's not worth ofcourse. By chance, is there any maintained list of the disks that fail over this issue?

Hello! I recently purchased MG06 SAS drives and was trying figure out why the spin-down does not work. So I found this old thread and read that this MG06 drives are not good for SAS spin-down as they expect a spin-up command but unRaid does not work like that. I used to have MG06 SATA drives and I got read-errors rarely (resulting in drive X failed by unRaid), but apparently still enough that I eventually had a failed array with some lost data. Now I replaced all drives with MG06 SAS drives only to find out that the spin-down is disabled for those (I guess from reading thread from 2 years ago). Has this problem been addressed after that? Here is the output of my drives also: sdd | MG06SCA800AY | 1000:0097:15d9:0808 | n/a | sde | MG06SCA800AY | 1000:0097:15d9:0808 | n/a | sdc | MG06SCA800AY | 1000:0097:15d9:0808 | n/a | sdg | MG06SCA800AY | 1000:0097:15d9:0808 | n/a | sdh | MG06SCA800AY | 1000:0097:15d9:0808 | n/a | sdi | MG06SCA800AY | 1000:0097:15d9:0808 | n/a |

@JorgeB Many thanks! I managed to get somehow the existing array to mount. Unfortunately I lost some files as I don't know where those got lost.

Sorry for late reply, Right! it took me some time to understand what you meant. Yes, I can see the mnt/disk2 in the console and there are my files. I'll try to find some way to copy the files off this disk to something external. As there is no FTP in safe-mode, I'm going to try attaching a USB drive and mounting it. Thanks for all the help so far. I'll write if I manage to rescue the files. BTW, is there a way to fix my array instead of rebuilding it?

Thanks so far for the help! in safe-mode As I ran it first, it cave no response. Trying to start the array, the issue was the same. I tried running the command couple times and I finally got this: root@Nassu:~# zpool import -o readonly=on disk2 root@Nassu:~# zpool import -o readonly=on disk2 cannot import 'disk2': a pool with that name already exists use the form 'zpool import <pool | id> <newpool>' to give it a new name root@Nassu:~# When I reboot normally then unRaid still can't mount disk2

Yes, the array is stopped. I have previously rebuilt on top of old disk and the problems started then. Now I'm going to try to rebuild on a one-new disk. Should I build the array in maintenance mode before zpool import disk2?

I have currently a rebuild pending. Would this affect it somehow? root@Nassu:~# zpool import disk2 cannot import 'disk2': insufficient replicas Destroy and re-create the pool from a backup source.

Here is the output: pool: disk2 id: 3587262688972901823 state: ONLINE status: Some supported features are not enabled on the pool. (Note that they may be intentionally disabled if the 'compatibility' property is set.) action: The pool can be imported using its name or numeric identifier, though some features will not be available without an explicit 'zpool upgrade'. config: disk2 ONLINE sdg1 ONLINE pool: disk4 id: 8692533118460009384 state: ONLINE status: Some supported features are not enabled on the pool. (Note that they may be intentionally disabled if the 'compatibility' property is set.) action: The pool can be imported using its name or numeric identifier, though some features will not be available without an explicit 'zpool upgrade'. config: disk4 ONLINE sdh1 ONLINE pool: disk3 id: 7081443555122238920 state: ONLINE status: Some supported features are not enabled on the pool. (Note that they may be intentionally disabled if the 'compatibility' property is set.) action: The pool can be imported using its name or numeric identifier, though some features will not be available without an explicit 'zpool upgrade'. config: disk3 ONLINE sde1 ONLINE

I managed to get new drives now to start to fix this problem, but I don't seem to get Disk 2 to mount. Things I have tried: I tried already replacing the disk - rebuilding in maintenance mode and when done, the error came back when trying to mount. Replacing the SATA cable - I have the disk on a backplane, changing the SATA cable and the problem is same. Swapping the Disk2 in the backplane with Disk4 - there is still the same problem with Disk2. If the backplane was bad, the problem should have had to move to Disk4. When removing the Disk2 and trying to start the Array - still the Disk2 mounting issue. I'm also adding the diagnostics. I was now able to download the diagnostics with unRaid 7.0. nassu-diagnostics-20250226-1259.zip

The unRaid was hanging on diagnostic export before restart, so could not get diagnostic on before. I did rebuild disks and I believe the disks failed after parity check (does parity check fail disks also?). The one thing I have not done since the shares have gone missing is parity check. Perhaps it needs to check parity and rebuild some errors for the shares to reappear? Also trying to run Array in any normal way will run CPU in max and any action like stopping array takes forever. The missing shares were stored on only Disk1 also (and I have the previous disk, so worst-case I can maybe try recovering that disk in some other machine). I have not formatted any disks unbeknownst. I have done rebuilds few times in the past successfully so I'm somewhat familiar with the procedure. -- I managed to boot unRaid to safe mode (without hanging on some mounting process) and I'm running parity check ATM.

I had Disk1 fail and after before I could replace it Disk2 failed (I had some power loss). I knew that those two disks were good so I swapped them, did data rebuild and all the files were there. But the next day, after parity check had completed there were ton of errors and half of the shares are missing now (they were on that first failed disk) and Disk1 was marked failed again. I replaced Disk1 with a new one, did a data rebuild and half the shared folders were not there. Doing restart is not bringing the shares back and I have not run a full parity check yet.. My unRaid tries to do a parity check again, but I stoped it (2 minutes produced already 6 errors). The unRaid seems to hang after some time (CPU usage is high). I'd be very thankful if some expert can tell me how should I get my shares back.. nassu-diagnostics-20240908-0850.zip