jbuszkie

Ok.. I uninstalled the older version. How does one reinstall this plugin? I don't see it in the apps?

I was very happy to see all my drives spun down when I checked on them today!!! 😁

ooh.... Maybe... About a year ago I reduced the number of slots I had. I might have had to do a new config for that!! I'll bet you that was it. Ugh! that means I've been wasting a whole bunch of energy for a year now!!! 😲 Thanks for probably helping me solve that mystery!!!

Was this recently added or changed? I've been noticing that over the past couple months, my disks were always spinning. I used to see most of them spun down when I checked but now they spinning all the time unless I hit the spin down button then they stay off until accessed. I saw this Default spin down delay in the settings and I swore I had something like this set to 15 minutes. But mine was set to "Never" I didn't change that. Did the parameter change or somehow get reset to "Never" with some OS upgrade I did? Thanks, Jim

Well I did end up getting the MDD drive from Amazon.. We'll see so long it lasts. It passed the preclear test and is currently serving parity

I posted as a bug in the bug reports section as well..

I did try to re-mount by doing something like mount /dev/md9p1 and it complained about not being in fstab or something. I then tried to mount to /mnt/disk9 and it also complained. I ended up having to do a hard power cycle. That seems to work ok and didn't start a parity check. Jim

Ok I did the above steps and I seen to be working ok. (parity 2 is in the process of rebuilding) caveats: This documentation needs to be updated: It's pre 6.12 and the mdX device numbers have changed to mdXp1 for 6.12 The Clear Drive script as I had loaded in User Scripts plugins is not working for my unraid. The script used pre 6.12 nomenclature. The procedure calls for unmounting the drive before doing the zeroing.. umount /mnt/diskX dd bs=1M if=/dev/zero of=/dev/mdX status=progress Again the mdX needs to be mdXp1 And this worked fine until I tried to shutdown the array. The shutdown script didn't like the fact that the drive was already unmounted and looped trying to unmount that drive. I believe this is a bug and the shutdown script should check to see if the drive is already unmounted... Now one can just do a new config make all the changes you want and just have it reconstruct the parity.. but even though my system is healthy and I'm sure it would have been fine... I'm paranoid and wanted to be protected at (almost) all times! Thanks for the input, guys!

I'm in the process of removing a disk from the array. I ran these commands umount /mnt/diskX dd bs=1M if=/dev/zero of=/dev/mdX status=progress where X was 9 and mdX was actually md9p1 (someone needs to update the docs) I got them from here When I tried to stop the array it's now stuck on retry unmounting shares. In the log I get this Sep 21 10:51:21 Tower emhttpd: shcmd (3175801): umount /mnt/disk9 Sep 21 10:51:21 Tower root: umount: /mnt/disk9: not mounted. Sep 21 10:51:21 Tower emhttpd: shcmd (3175801): exit status: 32 Sep 21 10:51:21 Tower emhttpd: Retry unmounting disk share(s)... Sep 21 10:51:26 Tower emhttpd: Unmounting disks... It looks like the shutdown script expects something from the umount command and doesn't check to see if it's already unmounted. How can I re-mount the disk so the shutdown script can unmount it and I can have a clean shutdown?

It's always scary doing that! lol

Ok.. So something like this: Zero the disk (I'm like 25% done with that.) Take a screen shot the array config stop the array. unassign disk10 assign disk10's drive to disk 9 unassign parity2 New configuration (keep existing assignments) start array with trust parity Start a parity check and let it go a little to make sure it starts and doesn't report tons of errors. (sanity check) Stop parity check Stop array re-assign parity2 Start array Parity 2 rebuild done? Jim Edit: added/changed the steps I did.

Will the array be protected while it rebuilds parity2? Is this documented somewhere? Thanks!

Is there a way to remove the hole? and make disk10 -> disk9?

I'm consolidating a couple disks and will remove them from my system to save a little power. I'm following this to remove the drive. The drive I'm removing is disk9 I have a disk 10 that's staying. Will disk10 become disk9? or will I have a hole where disk9 used to be? will it go disk7, disk8, disk10? Also.. If I don't zero out the drive first and do the rebuild.. Will I still be protected if I have dual parity? I'm thinking no since it "resets the array configuration" and has to rebuild parity from scratch? Thanks, Jim