Leaderboard

Thank you for the report and blog post. It's going to take a while for me to fully digest what you're doing. There's nothing really 'magic' about the Unraid SMB implementation - we use pretty much the latest releases of Samba. You can tweak yourself via Network/SMB/SMB extra configuration.

As far as I know this feature has always been there (well at least since Unraid v5 which is when I started with it). The only thing I can remember that changed was making it default to non-correcting rather than correcting. Any time Unraid cannot successfully unmount the drives there is quite likely to be some invalid sectors on the parity drive so I cannot see why a normal user would EVER want this feature disabled. The correct solution is for you to resolve what is stopping the unmounting from succeeding so the shutdown completes cleanly. What are you using to trigger your unmount scripts - maybe that is where the issue lies and they are not getting run successfully?

Something is preventing Unraid from unmounting the disks: Apr 30 01:27:07 Unraid-Server emhttpd: shcmd (416): umount /mnt/user Apr 30 01:27:07 Unraid-Server root: umount: /mnt/user: target is busy. Hence the unclean shutdowns.

So you expect the disks to fail after 4 scheduled parity checks?

I kept trying each RC until I found a stable one. RC4 had been the most stable with an uptime of about 2 weeks which usually means I am in the clear. I just upgraded to RC5 a couple days ago and that has been solid as well so far.