CaptainTivo

Actually, why don't you need to do a "new config"? This sounds like a new config to me. When is "new config" actually needed?

Thanks. I googled but ended up in "parity swap" page instead of this one.

I want to replace my current 10TB parity drive with a 14TB. After some research, some say it is as simple as 1. stop array 2. select parity drive and then "unassigned" 3. select new drive and the select "parity" 4. start array But don't I need to do a "new config" for this?

Thank you for that. I suppose I did this years ago when I last reset my config but forgot about it.

I just finished removing a disk and rebuilding parity after a new config. I find that user shares are visible on SMB (Windows 10) but disk shares are not. They were mounted before I did the new config and they show that they are still enabled in Setting/Global share settings (see below). I have stopped the array, disabled disk shares, then restarted and stopped again and set enable disk shares and restarted. The disk shares are still not visible on \Tower. (see below) Is there something else I need to do the have Unraid mount them on SMB? Thanks.

D'oh. I did not notice the apply, just the "Done". I don't do this often..

Hello, I am attempting to re-assign all my disks to new disk slots. I am following this guide: https://docs.unraid.net/unraid-os/manual/storage-management/#reset-the-array-configuration I have done steps 1, 2, 3 and returned to the main page However, even though I selected to save none of the current assignments, they are still there. Worse, if I attempt to unassign a disk to a current slot, it will then show "missing". If I assign a different disk to that slot, it will show "missing". Here is what it looks like after doing the "New Config" And here is what it looks like after selecting "no device" for a slot. Shouldn't I have the choice to "unassign" a slot and then get a dropdown with the list of unassigned disks to select from? What should I do now? Thanks for any help.

Hello, I am going to remove a drive from my array. I copied all the data from it to a new disk (already in the array) and will now un-assign it remove it from the array. Over the years, I have removed and added many drives and the disk numbers are really fragmented so I would like reassign all the disks in numerical order before I rebuild the parity. I currently have only two top-level shares: Backup and Videos. Of course, they are defined using the current disk numbers. After I do the New Config, I will re-assign all the disks and so I need to reassign which disks are included in the Shares definitions. Now, I have never "redefined" a share before. I know that a share must have no data in it before it can be deleted, so I can't just delete the shares. So, should I just leave the share definitions as is? Will they have the same include/excluded disks after the new config reboot? Or shoud I delete all the "Included disk(s)" numbers before the "new config" and then change these numbers to the correct disk numbers after the restart? Any help is appreciated. Thanks.

I have two shares, Backup1 and Backup2 Backup1 is defined as: Included Disk(s): disk4, disk10 Backup2 is defined as: Included Disk(s): disk1 I want to combine the two shares into a single share named Backup1 and containing only the three disks: disk1, disk4 and disk10. Is this as simple as renaming the top directory on disk1 to "Backup1"? I don't see a "delete share" button so I don't see a way to delete a share? Thanks.

D'oh! Of course, the reconstructed disk would be bit-for-bit, wouldn't it? See, I knew I should ask first before acting! I have never before had to reformat a disk. Ok. Plan B. Should I use unbalance or just rsync myself?

I have been getting a warning "reiserfs on disk8" and I am running out of space on one of my shares so I thought I would fix both problems. The only disk I have that is RFS formatted is disk8 (4 TB) I have a new disk (10 TB) which I have pre-cleared. I would like to: 1. add the new 10 TB disk to the array 2. move the data from disk8 (RFS) to the new disk 3. reformat disk8 to XFS At first, I planned to simply add the new disk to the array and use rsync to copy the data from the old RFS disk to the new one and then shrink the array. But multiple sources say the better way is to simply rebuild the disk. Here is my plan: 1. Replace disk8 with the new 10 TB disk a. stop array b. unassign disk8 c. start array d. stop array e. assign 10TB disk to slot disk8 f. start the array - this will rebuild the data from old disk8 (4 TB) onto new disk8 (10 TB) When will all the data be copied to the new disk8? How will I know when to copy is finished? 2. preclear old disk8 RFS disk 3. add old disk8 to array, format as SFS and assign it to share Backup1 a. stop array b. assign old disk8 to a new slot c. start array d. since disk have been pre-cleared, now format disk as XFS e. after disk is mounted, add this disk to Backup1 share I know this extremely detailed but I just don't do this stuff often and I have upgraded the Unraid since then so I want to be sure that I have all the details right. Any advice/comments are appreciated. Thanks.

Thank you! It had been so many years since I enabled reconstruct writes that I had forgotten the "side effect". Mystery solved!

After some investigation, I found the cause. I had specified a network share on the server as the target for a Windows backup, including "Back up using File History" and I specified "Every hour" as the frequency. The target is a share on the server which I I defined a Share on the server with "Included disks" set to "Disk1" and "Excluded disks" set to empty (no entry). My understanding is that you either use "Included disks" OR "Excluded disks" to define your share, not both. So why did Unraid to spin up ALL the disks in the server if the share is only on one disk? If I additionally excluded the other disks in the server would it then not spin them up? Anyway, I will mark this SOLVED and ask the other question in a new thread. Thanks.

Correction: my spindown time is 15 minutes. This makes more sense when you read the log. Sorry about that 🙂

I was poking around in my newly updated server (6.11.5) and noticed in the system log that SMART data is being read on every drive every half hour! By default, I spin down all drives after 30 minutes of idle (no access) so this means that they are all spinning about half of the time, 24/7! This not good. I run the Scrutiny docker so I thought that might be doing it, but I stopped that docker and that did not stop the SMART reads. Apr 7 23:06:27 Tower emhttpd: read SMART /dev/sdk Apr 7 23:06:27 Tower emhttpd: read SMART /dev/sdh Apr 7 23:06:27 Tower emhttpd: read SMART /dev/sde Apr 7 23:06:27 Tower emhttpd: read SMART /dev/sdf Apr 7 23:06:27 Tower emhttpd: read SMART /dev/sdc Apr 7 23:06:38 Tower emhttpd: read SMART /dev/sdg Apr 7 23:06:38 Tower emhttpd: read SMART /dev/sdl Apr 7 23:07:31 Tower emhttpd: read SMART /dev/sdj Apr 7 23:07:31 Tower emhttpd: read SMART /dev/sdd Apr 7 23:22:32 Tower emhttpd: spinning down /dev/sdj Apr 7 23:22:32 Tower emhttpd: spinning down /dev/sdk Apr 7 23:22:32 Tower emhttpd: spinning down /dev/sdh Apr 7 23:22:32 Tower emhttpd: spinning down /dev/sdd Apr 7 23:22:32 Tower emhttpd: spinning down /dev/sde Apr 7 23:22:32 Tower emhttpd: spinning down /dev/sdf Apr 7 23:22:32 Tower emhttpd: spinning down /dev/sdc Apr 7 23:23:02 Tower emhttpd: spinning down /dev/sdg Apr 7 23:23:02 Tower emhttpd: spinning down /dev/sdl Has anyone noticed this or it just my system? Any ideas what is causing this and how to stop it? As always, thanks for any help. tower-diagnostics-20230427-1538.zip