April 1, 20242 yr HI, I never had a problem with the speed of r/w during the parity; always around 200 MB/s. Recently I have added a new drive to the array with no issues on the GUI console, all looking good. The new drive was pre-cleared and the speed was around 200MB/s during the process. Yesterday my monthly parity started and to my surprise the speed in in 67MB/s range resulting in 3 times more time to complete (still not done). While investigating I found the error in the log (see below). My new disk9 is still empty, nothing was written. Have anyone seen a similar issue? The parity is still running. Please advise. Regards Bob From the log: Mar 6 11:42:11 Tower root: mount: /mnt/disk9: wrong fs type, bad option, bad superblock on /dev/md9, missing codepage or helper program, or other error. Mar 6 11:42:11 Tower emhttpd: /mnt/disk9 mount error: No file system
April 1, 20242 yr Community Expert 3 hours ago, BobNik said: Mar 6 11:42:11 Tower root: mount: /mnt/disk9: wrong fs type, bad option, bad superblock on /dev/md9, missing codepage or helper program, or other error. Mar 6 11:42:11 Tower emhttpd: /mnt/disk9 mount error: No file system Had you actually gotten around to formatting the disk from within Unraid? When you first add a new drive it will shows as unmountable until you format it to create an empty file system ready to receive files.
April 1, 20242 yr Author The Log is attached. Yes, I have formatted the drive. Since nothing is written on that drive, I can reformat again and restart but after the parity is done. Still one hour to go. tower-syslog-20240401-1949.zip
April 2, 20242 yr Author Well, I have restarted the PC and the log after the boot doesn't show any prior errors. Tonight I will do another parity check (without error corrections) just to see the speed. If back to normal, I would consider this problem gone.
April 2, 20242 yr Community Expert OK, check was already stopped on the diags posted, post new diags during it if it happens again.
April 2, 20242 yr Author Solution The new parity check had speed of 190MB/s, so I assumed that the issue is now fully resolved with the reboot. My next scheduled parity check is on May 1 and I will post new diagnostic if the same thing happens. Thank you for listening. Regards Bob
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.