I recently replaced a drive and despite some issues everything seemed like it was ok, until I noticed that the cache drive filled up because the mover was reporting read only errors.

 

Here is an excerpt from the syslog of the last couple of manual triggers of the mover:

 

I put unraid into maintenance mode and tried running "reiserfsck --check /dev/md2" but get this error: 

 

• bread: Cannot read the block (943196360): (Invalid argument).
• Failed to open the device '/dev/md2': Unknown code er3k 125

 

Same message when using --fix. I have run a full SMART test on all drives and they come back fine. I have also enabled disk shares and can see data on the disk in question, so not sure why it would be considered read only.

 

There was a 4kb file on the disk share for one of the files the mover could not move, which I deleted from the cache and then the disk, but it kept reappearing on the disk from somewhere. About an hour after I last tried, it's suddenly gone... 

 

What is most strange though, is that the dashboard reports the drive as being bigger than it actually is (3.9Tb instead of 3Tb):

 

 

If you see my link above, Unraid previously identified that drive's capacity correctly.

 

Not sure if I have a hardware or a software issue.. or gemlins?

Just for laughs I tried again, and to my surprise a file moved successfully.. so i tried a second time and got some new errors:

 

 

8 minutes ago, o0X0o said:

Just for laughs I tried again, and to my surprise a file moved successfully.. so i tried a second time and got some new errors:

 

Yeah, it would depend upon whether the filesystem hit a section that had corruption

 

https://wiki.unraid.net/Check_Disk_Filesystems against disk2 .  May also have to run it against the cache drive

When I run it on the cache drive it seems to work

 

Quote

reiserfsck 3.6.27 Will read-only check consistency of the filesystem on /dev/sdh1 Will put log info to 'stdout' ########### reiserfsck --check started at Fri Jan 3 11:58:22 2020 ########### Replaying journal: Replaying journal: Done. Reiserfs journal '/dev/sdh1' in blocks [18..8211]: 0 transactions replayed

But when I run it on disk 2 I get the same error as when I did it through the console ("reiserfsck --check /dev/md2"):

 

Quote

 

reiserfsck 3.6.27 Will read-only check consistency of the filesystem on /dev/md2 Will put log info to 'stdout' bread: Cannot read the block (943196360): (Invalid argument). Failed to open the device '/dev/md2': Unknown code er3k 125

 

4 hours ago, o0X0o said:

Unknown code er3k 125

That's a reisefs bug, not sure what version comes with v6.6.6 but likely no the latest, you should upgrade Unraid and try again, you should also convert from all reiser filesystems, reiserfs it's not recommended for years now for various reasons.

Thanks. I was cautious of upgrading as I didn't want to introduce more changes, but I've done it now (to 6.8.0) and the result is the same.

 

Looks like I'm off to pickup a new drive so I can have space to move data and convert the file system...