May 16, 20251 yr Author 8 minutes ago, trurl said: https://docs.unraid.net/unraid-os/manual/storage-management/#reset-the-array-configuration Just to clarify, to unmount I should do: umount /dev/sds1 Do I need to remove the directory I created as well? Also, when I create the new config, should I preserve the current assignments and swap the old drive back in for disk 13 on Main? Wanting to clarify, before I make any missteps.
May 16, 20251 yr Community Expert 8 minutes ago, chris206 said: Just to clarify, to unmount I should do: I made a typo, it's umount /x 8 minutes ago, chris206 said: Do I need to remove the directory I created as well? You can, but it will disappear after a reboot, and it won't cause any issue while it's there. 9 minutes ago, chris206 said: should I preserve the current assignments and swap the old drive back in for disk 13 on Main? Yes, that makes it easier.
May 16, 20251 yr Author 14 minutes ago, JorgeB said: I made a typo, it's umount /x You can, but it will disappear after a reboot, and it won't cause any issue while it's there. Yes, that makes it easier. One last question before I proceed, should I expect to see activity for the mounting/unmounting of sds1 in its disk log information? I can see the failures from using the UD plugin yesterday, but nothing was logged from mounting via the webterminal? Is that normal/expected? For clarification, I opened disk log information from the drive symbol in unassigned devices. tower-diagnostics-20250516-1300.zip
May 16, 20251 yr Author 18 minutes ago, JorgeB said: Yep. Alright, unmounted, created the new config, and swapped the two drives. Now, I should start in maintenance mode and check parity? How do I go about that without overwriting what's currently on the parity disks? I know it warns about overwriting the parity drives when the array is started. Also, I got this error: Quote May 16 13:17:50 Tower kernel: read_file: error 2 opening /boot/config/super.dat May 16 13:17:50 Tower kernel: md: could not read superblock from /boot/config/super.dat when creating the new config, should I investigate that first or ignore? tower-diagnostics-20250516-1323.zip Edited May 16, 20251 yr by chris206
May 16, 20251 yr Community Expert Solution New Config resets super.dat (your array assignments) so that is OK. Better if you start in normal mode instead of maintenance mode. We can't tell anything about your filesystems in maintenance mode.
May 16, 20251 yr Author 3 minutes ago, trurl said: New Config resets super.dat (your array assignments) so that is OK. Better if you start in normal mode instead of maintenance mode. We can't tell anything about your filesystems in maintenance mode. So, check, "parity is already valid" and then start?
May 16, 20251 yr Author 7 minutes ago, trurl said: Yes, then post new diagnostics Done. tower-diagnostics-20250516-1409.zip
May 16, 20251 yr Author Thanks, I appreciate all the help I received. I've never had issues with mounting before, so I was at a total loss. I suppose the question is, how much should I investigate the cause of the initial failure? I think I may have a few files with filenames that are too long for the filesystem that may remain on the cache drive? I'm not entirely sure, I saw messages about them on the syslog before the drive had a bunch of write errors. So, I wasn't sure if that was the root cause of the issue.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.