Here is my story.

 

A few weeks ago I was getting read only access on a few files.... it spread to all of my shared drives. This really only started when I replaced an IDE drive for a Sata drive. My buddy came over and help me get my unraid back up and running again so that I can save my files again. Now the issue has cropped back up.

I think that I have found the problem... I have gone over all of the forums and have not found a solution. Can anyone please have a look and tell me what they see!

I have posted the log files, but about here is where I think that things go bad!

 

Dec 14 12:25:22 crossfiregaming kernel: can't shrink filesystem on-line

Dec 14 12:26:26 crossfiregaming kernel: REISERFS (device md1): replayed 503 transactions in 64 seconds

Dec 14 12:26:26 crossfiregaming kernel: REISERFS (device md1): Using r5 hash to sort names

Dec 14 12:26:26 crossfiregaming kernel: can't shrink filesystem on-line

Dec 14 12:26:26 crossfiregaming emhttp: shcmd (31): rm /etc/samba/smb-shares.conf >/dev/null 2>&1

Dec 14 12:26:26 crossfiregaming emhttp: shcmd (32): cp /etc/exports- /etc/exports

Dec 14 12:26:26 crossfiregaming emhttp: shcmd (33): mkdir /mnt/user

Dec 14 12:26:26 crossfiregaming emhttp: shcmd (34): /usr/local/sbin/shfs /mnt/user  -o noatime,big_writes,allow_other,default_permissions

Dec 14 12:26:28 crossfiregaming emhttp: get_config_idx: fopen /boot/config/shares/lost+found.cfg: No such file or directory - assigning defaults

Dec 14 12:26:28 crossfiregaming emhttp: shcmd (35): killall -HUP smbd

Dec 14 12:26:28 crossfiregaming emhttp: shcmd (36): /etc/rc.d/rc.nfsd restart | logger

Dec 14 12:31:10 crossfiregaming kernel: attempt to access beyond end of device

Dec 14 12:31:10 crossfiregaming kernel: md1: rw=1, want=976770992, limit=976770984

Dec 14 12:31:10 crossfiregaming kernel: REISERFS abort (device md1): Journal write error in flush_commit_list

syslog_edited.txt

Oh... I did shut down. Did a complete parity check and it all was good... I then moved two of my 6 drives to a Sata controller card and got write access... but it didn't last long

I have isolated the problem.

I have SickBeard and SABnzbd running on another computer... Anytime I load SABnzbd up the drives become read only. Is there a reason why this would be happening?

You posted the clue in your first post

 

Dec 14 12:31:10 crossfiregaming kernel: attempt to access beyond end of device

Dec 14 12:31:10 crossfiregaming kernel: md1: rw=1, want=976770992, limit=976770984

Dec 14 12:31:10 crossfiregaming kernel: REISERFS abort (device md1): Journal write error in flush_commit_list

The file system on disk1 is corrupted.  unRAID is making it read-only when used (once the corruption is identified) to prevent further corruption.

 

you need to run reiserfsck on /dev/md1 as described in the wiki.

http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

We did that before... I think that I figured out what is going on... For some reason Sabzndb was messing things up. I uninstalled and reinstalled.

The problem would only occur if I had ran Sabzndb, now that I have uninstalled and reinstalled everything is running like butter again!