So after somewhat recovering from this mess: http://lime-technology.com/forum/index.php?topic=13278.0

 

My unraid setup is suffering a lingering problem: I can't delete some files or create some directories in some places.  I have a feeling one or more drives are causing this, but am not sure how to find out which ones or how to fix it.

 

Log is attached, and also getting a bunch of these errors when I instigate the mover:

 

Jun 14 02:41:47 Cooper logger: rsync: recv_generator: mkdir "/mnt/user/Backup/Don Backup" failed: Read-only file system (30)
Jun 14 02:41:47 Cooper logger: *** Skipping any contents from this failed directory ***
Jun 14 02:41:47 Cooper logger: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1042) [sender=3.0.7]
Jun 14 02:41:47 Cooper shfs: shfs_mkdir: create_path: /mnt/disk9/Backup Backup/Don Backup /mnt/disk1/Backup (30) Read-only file system
Jun 14 02:41:47 Cooper logger: cd+++++++++ Backup/Don Backup/
Jun 14 02:41:47 Cooper logger: rsync: recv_generator: mkdir "/mnt/user/Backup/Don Backup" failed: Read-only file system (30)
Jun 14 02:41:47 Cooper logger: *** Skipping any contents from this failed directory ***
Jun 14 02:41:47 Cooper logger: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1042) [sender=3.0.7]
Jun 14 02:41:47 Cooper logger: mover finished
Jun 14 02:41:59 Cooper ntpd_intres[1394]: DNS time.nist.gov -> 192.43.244.18

 

Thanks!

syslog.txt

Disk9 has some corruption and needs to be fixed.

Jun 14 02:20:21 Cooper kernel: REISERFS error (device md9): reiserfs-2025 reiserfs_cache_bitmap_metadata: bitmap block 97648640 is corrupted: first bit must be 1

Jun 14 02:20:21 Cooper kernel: REISERFS (device md9): Remounting filesystem read-only

 

To prevent more damage, the OS is mounting disk9 ( /dev/md9 ) as read-only.

 

Follow the procedure described here to fix:

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

That was it, thanks!