Hi,

 

I just started using unRAID, so my appollogies if I am stuck in a standard situation here, but I couldnt find any hints with the search. I am using unRAID version: 5.0-beta14.

 

So here is the situation: I set up a share in freshly created array and started copying files to it over a smb share. After copying a few files, the copy process terminated with an error message (about write permission) and ever since I cannot write to that share (or any other one) anymore. "Access denied" and some hints that I shall check for write permissions and full disk.

I am not aware doing anything but watching the status bar of the copy process, while it happened. About 1 GB was copied so I doubt the disk is full ...

 

Anyone has a clue what happened?

What can I do to fix this?

 

Additional information, which is maybe important:

This is the first time I set up unRAID. I set up unraid with 4 disks. I have to say, that I first added the parity disk along with two other disks and that a power failure occured during the format. However, all 3 drives showed up "green" after reboot.

I then copied over my license file, rebooted once more added another disk to the array. I somehow, again, managed to interrupt the format process. I was exploring the GUI and cant quite remember how it happned. However, that drive also made its way into the array without any hassle.

 

EDIT: added my unRAID version

Post a syslog for us to see what's happening.

 

In the meantime, check to see if you had  file-system corruption that would mark the drive as read-only.

 

I copied the (hopefully) relevant part of the syslog. Yes it tells about read-only.

 

May  4 23:01:04 Tower emhttp: Spinning up all drives...
May  4 23:01:04 Tower kernel: mdcmd (39): spinup 0
May  4 23:01:04 Tower kernel: mdcmd (40): spinup 1
May  4 23:01:04 Tower kernel: mdcmd (41): spinup 2
May  4 23:01:04 Tower kernel: mdcmd (42): spinup 3
May  4 23:05:27 Tower emhttp: shcmd (112): mkdir '/mnt/user/movies'
May  4 23:05:27 Tower emhttp: shcmd (113): chmod 770 '/mnt/user/movies'
May  4 23:05:27 Tower emhttp: shcmd (114): chown nobody:users '/mnt/user/movies'
May  4 23:05:27 Tower emhttp: shcmd (115): :>/etc/samba/smb-shares.conf
May  4 23:05:27 Tower emhttp: Restart SMB...
May  4 23:05:27 Tower emhttp: shcmd (116): killall -HUP smbd
May  4 23:05:28 Tower emhttp: shcmd (117): ps axc | grep -q rpc.mountd
May  4 23:05:28 Tower emhttp: _shcmd: shcmd (117): exit status: 1
May  4 23:05:28 Tower emhttp: shcmd (118): /usr/local/sbin/emhttp_event svcs_restarted
May  4 23:05:28 Tower emhttp_event: svcs_restarted
May  4 23:05:38 Tower emhttp: shcmd (119): mkdir '/mnt/user/series'
May  4 23:05:38 Tower emhttp: shcmd (120): chmod 770 '/mnt/user/series'
May  4 23:05:38 Tower emhttp: shcmd (121): chown nobody:users '/mnt/user/series'
May  4 23:05:38 Tower emhttp: shcmd (122): :>/etc/samba/smb-shares.conf
May  4 23:05:38 Tower emhttp: Restart SMB...
May  4 23:05:38 Tower emhttp: shcmd (123): killall -HUP smbd
May  4 23:05:38 Tower emhttp: shcmd (124): ps axc | grep -q rpc.mountd
May  4 23:05:38 Tower emhttp: _shcmd: shcmd (124): exit status: 1
May  4 23:05:38 Tower emhttp: shcmd (125): /usr/local/sbin/emhttp_event svcs_restarted
May  4 23:05:38 Tower emhttp_event: svcs_restarted
May  4 23:08:18 Tower emhttp: shcmd (126): :>/etc/samba/smb-shares.conf
May  4 23:08:18 Tower emhttp: Restart SMB...
May  4 23:08:18 Tower emhttp: shcmd (127): killall -HUP smbd
May  4 23:08:18 Tower emhttp: shcmd (128): ps axc | grep -q rpc.mountd
May  4 23:08:18 Tower emhttp: _shcmd: shcmd (128): exit status: 1
May  4 23:08:18 Tower emhttp: shcmd (129): /usr/local/sbin/emhttp_event svcs_restarted
May  4 23:08:18 Tower emhttp_event: svcs_restarted
May  4 23:08:28 Tower emhttp: shcmd (130): :>/etc/samba/smb-shares.conf
May  4 23:08:28 Tower emhttp: Restart SMB...
May  4 23:08:28 Tower emhttp: shcmd (131): killall -HUP smbd
May  4 23:08:28 Tower emhttp: shcmd (132): ps axc | grep -q rpc.mountd
May  4 23:08:28 Tower emhttp: _shcmd: shcmd (132): exit status: 1
May  4 23:08:28 Tower emhttp: shcmd (133): /usr/local/sbin/emhttp_event svcs_restarted
May  4 23:08:28 Tower emhttp_event: svcs_restarted
May  4 23:08:47 Tower emhttp: shcmd (134): :>/etc/samba/smb-shares.conf
May  4 23:08:47 Tower emhttp: Restart SMB...
May  4 23:08:47 Tower emhttp: shcmd (135): killall -HUP smbd
May  4 23:08:47 Tower emhttp: shcmd (136): ps axc | grep -q rpc.mountd
May  4 23:08:47 Tower emhttp: _shcmd: shcmd (136): exit status: 1
May  4 23:08:47 Tower emhttp: shcmd (137): /usr/local/sbin/emhttp_event svcs_restarted
May  4 23:08:47 Tower emhttp_event: svcs_restarted
May  4 23:09:00 Tower emhttp: shcmd (138): :>/etc/samba/smb-shares.conf
May  4 23:09:00 Tower emhttp: Restart SMB...
May  4 23:09:00 Tower emhttp: shcmd (139): killall -HUP smbd
May  4 23:09:00 Tower emhttp: shcmd (140): ps axc | grep -q rpc.mountd
May  4 23:09:00 Tower emhttp: _shcmd: shcmd (140): exit status: 1
May  4 23:09:00 Tower emhttp: shcmd (141): /usr/local/sbin/emhttp_event svcs_restarted
May  4 23:09:00 Tower emhttp_event: svcs_restarted
May  4 23:10:45 Tower emhttp: shcmd (142): :>/etc/samba/smb-shares.conf
May  4 23:10:45 Tower emhttp: Restart SMB...
May  4 23:10:45 Tower emhttp: shcmd (143): killall -HUP smbd
May  4 23:10:45 Tower emhttp: shcmd (144): ps axc | grep -q rpc.mountd
May  4 23:10:45 Tower emhttp: _shcmd: shcmd (144): exit status: 1
May  4 23:10:45 Tower emhttp: shcmd (145): /usr/local/sbin/emhttp_event svcs_restarted
May  4 23:10:45 Tower emhttp_event: svcs_restarted
May  4 23:11:13 Tower emhttp: shcmd (146): :>/etc/samba/smb-shares.conf
May  4 23:11:13 Tower emhttp: Restart SMB...
May  4 23:11:13 Tower emhttp: shcmd (147): killall -HUP smbd
May  4 23:11:13 Tower emhttp: shcmd (148): ps axc | grep -q rpc.mountd
May  4 23:11:13 Tower emhttp: _shcmd: shcmd (148): exit status: 1
May  4 23:11:13 Tower emhttp: shcmd (149): /usr/local/sbin/emhttp_event svcs_restarted
May  4 23:11:13 Tower emhttp_event: svcs_restarted
May  4 23:14:03 Tower shfs/user: shfs_ftruncate: ftruncate: (5) Input/output error
May  4 23:14:03 Tower shfs/user: shfs_utimens: utimes: /mnt/disk1/series/SuI/SuI/SuI.03/filename.txt (30) Read-only file system
May  4 23:14:03 Tower shfs/user: shfs_utimens: utimes: /mnt/disk1/series/SuI/SuI/SuI.03/filename.txt (30) Read-only file system
May  4 23:14:03 Tower shfs/user: shfs_open: open: /mnt/disk1/series/SuI/SuI/SuI.03/filename.txt (30) Read-only file system
May  4 23:14:03 Tower shfs/user: shfs_chmod: chmod: /mnt/disk1/series/SuI/SuI/SuI.03/filename.txt 0100660 (30) Read-only file system
May  4 23:14:03 Tower kernel: REISERFS error (device md1): reiserfs-2025 reiserfs_cache_bitmap_metadata: bitmap block 119701504 is corrupted: first bit must be 1
May  4 23:14:03 Tower kernel: REISERFS (device md1): Remounting filesystem read-only
May  4 23:14:03 Tower kernel: REISERFS warning (device md1): clm-6006 reiserfs_dirty_inode: writing inode 15 on readonly FS
May  4 23:14:03 Tower shfs/user: shfs_create: open: /mnt/disk1/series/SuI/SuI/SuI.03/SuI.03.avi (30) Read-only file system
May  4 23:14:34 Tower last message repeated 48 times
May  4 23:14:35 Tower shfs/user: shfs_mkdir: mkdir: /mnt/disk1/series/SuI/SuI/SuI.04 (30) Read-only file system
May  4 23:14:37 Tower shfs/user: shfs_mkdir: mkdir: /mnt/disk1/series/SuI/SuI/SuI.05 (30) Read-only file system
May  4 23:14:38 Tower shfs/user: shfs_mkdir: mkdir: /mnt/disk1/series/SuI/SuI/SuI.06 (30) Read-only file system
May  4 23:17:56 Tower shfs/user: shfs_mkdir: mkdir: /mnt/disk1/series/SuI/SuI/SuI.08 (30) Read-only file system
May  4 23:17:57 Tower shfs/user: shfs_mkdir: mkdir: /mnt/disk1/series/SuI/SuI/SuI.09 (30) Read-only file system
May  4 23:17:58 Tower shfs/user: shfs_mkdir: mkdir: /mnt/disk1/series/SuI/SuI/SuI.10 (30) Read-only file system
May  4 23:24:12 Tower shfs/user: shfs_mkdir: mkdir: /mnt/disk1/series/SuI/SuI/SuI.08 (30) Read-only file system
May  4 23:24:12 Tower shfs/user: shfs_mkdir: mkdir: /mnt/disk1/series/SuI/SuI/SuI.08 (30) Read-only file system
May  4 23:24:22 Tower shfs/user: shfs_mkdir: mkdir: /mnt/disk1/series/SuI/SuI/SuI.04 (30) Read-only file system
May  4 23:24:31 Tower shfs/user: shfs_mkdir: mkdir: /mnt/disk1/series/SuI/SuI/Neuer Ordner (30) Read-only file system
May  4 23:24:31 Tower shfs/user: shfs_mkdir: mkdir: /mnt/disk1/series/SuI/SuI/Neuer Ordner (30) Read-only file system
May  4 23:24:31 Tower shfs/user: shfs_mkdir: mkdir: /mnt/disk1/series/SuI/SuI/Neuer Ordner (2) (30) Read-only file system
May  4 23:24:31 Tower shfs/user: shfs_mkdir: mkdir: /mnt/disk1/series/SuI/SuI/Neuer Ordner (2) (30) Read-only file system
May  4 23:26:55 Tower shfs/user: shfs_create: open: /mnt/disk1/movies/Staplerfahrer Klaus.avi (30) Read-only file system
May  4 23:26:55 Tower last message repeated 2 times
May  4 23:27:01 Tower shfs/user: shfs_mkdir: mkdir: /mnt/disk1/movies/Neuer Ordner (30) Read-only file system
May  4 23:27:01 Tower shfs/user: shfs_mkdir: mkdir: /mnt/disk1/movies/Neuer Ordner (30) Read-only file system
May  4 23:27:01 Tower shfs/user: shfs_mkdir: mkdir: /mnt/disk1/movies/Neuer Ordner (2) (30) Read-only file system
May  4 23:27:01 Tower shfs/user: shfs_mkdir: mkdir: /mnt/disk1/movies/Neuer Ordner (2) (30) Read-only file system

Ok, I think these two line are most relevant:

May  4 23:14:03 Tower kernel: REISERFS error (device md1): reiserfs-2025 reiserfs_cache_bitmap_metadata: bitmap block 119701504 is corrupted: first bit must be 1

May  4 23:14:03 Tower kernel: REISERFS (device md1): Remounting filesystem read-only

 

Now, how do I fix it?

There is only very little data on the array yet, so I think just reformat everything could be a good option as this never completed porperly. But how? The format button is not present anymore.

 

Here's one place to start: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

 

You merely need to do a filesystem check and follow the proper steps that will be indicated on your system when you run the first check command.

 

Hi. I feel your pain. I had lots of trouble when I first built my array with copy and permission errors. Check the smart info for your disks as I had one failing.

 

The steps to do the file system check are good. Follow them exactly - even as a fresh user I managed it and it solved my mounted as read only issues.

 

The support on here is very good. Provide as much info as possible and you will get good help

 

 

Thanks for the link. It did help. I unmounted all drives, check them and, as suggested by the check report, had them fixed with the --fix-fixable option.

I could not remount drives as was explained in the Wiki, so I went to the GUI and simply stopped and restarted the array.

Write access is back. Thanks!

 

Just one thing I am wondering. As far as I understand, the format takes long as it fills the drive with zeros. This process was not accomplished an any of my drives (see first post). Is this something I should worry about?

The format takes a minute or two. Clearing the drive with zeros takes several hours. The drives are not required to be cleared for a new array, only when adding a disk to an existing array. It is still a very good idea to pre-clear all disks to verify reliability.