Hi all,

 

I've just installed unRAID 4.5 onto a new box, the parity sync has finished and the array in now online. However, when I try and add a user share the page refreshes and I don't see the user share I just added, looking at the screen on the server it shows:

 

root@Tower: mkdir: cannot create directory '/mnt/user/Media' :  read-only file system

chmod: cannot access '/mnt/user/Media' : No such file or directory

 

Looks like the drive is set to read-only? When I try and copy files directly onto a drive (i.e. disk1) is says I don't have permissions (using Windows 7 x64). Any ideas?

 

Thanks!

No ideas so far, but something sounds 'fubar', so capture and attach your syslog (see the Troubleshooting link in my sig).

I took down the syslog and noticed an error on the screen after a recent restart (also tried re-downloading unRAID 4.5 but still have the same issues). Here's the area that I think is causing the problem:

 

 

Dec 12 09:38:55 Tower kernel: REISERFS error (device md1): reiserfs-2025 reiserfs_cache_bitmap_metadata: bitmap block 366280704 is corrupted: first bit must be 1

Dec 12 09:38:55 Tower kernel: REISERFS (device md1): Remounting filesystem read-only

 

I'm about to try 4.4.2 to see if that works.

I took down the syslog and noticed an error on the screen after a recent restart (also tried re-downloading unRAID 4.5 but still have the same issues). Here's the area that I think is causing the problem:

 

 

Dec 12 09:38:55 Tower kernel: REISERFS error (device md1): reiserfs-2025 reiserfs_cache_bitmap_metadata: bitmap block 366280704 is corrupted: first bit must be 1

Dec 12 09:38:55 Tower kernel: REISERFS (device md1): Remounting filesystem read-only

 

I'm about to try 4.4.2 to see if that works.

If you have a corrupted reiser file system, you'll need to repair it by running reiserfsck as described in the wiki.

 

It won't matter which version of unRAID you use.

 

Joe L.

Your syslog is a little troubling, both drives have issues.

 

Disk 1 (sdb, ata1.00, serial ending in 095) had a little difficulty being setup, then shows evidence of a crash or improper shutdown in the previous session, plus has a corrupted Reiser file system, sufficiently corrupted to be restricted to read-only (which blocked the transaction replay and User Share setup and makes the drive unusable).  This kind of error is comparable to an error requiring ScanDisk or CheckDisk in Windows.  For a brand new system though, file system corruption seems really strange, very rare, unless power was turned off while it was being formatted, or this disk has been in use in another Linux system?  Normally we would recommend running reiserfsck on the disk, as Joe said, see Check Disk File systems, but if you have no data yet on the drive, I would just clear the drive and start over.

 

The Parity disk (sdc, ata4.00, serial ending in 667) did not report any issues on initial setup, but later on each attempt to build parity, quickly reported exceptions (timeout, but no specific error), then went through a series of unsuccessful resets, then slowed the SATA link speed to 1.5, then reported "ata4.00: device reported invalid CHS sector 0", then was finally ready to continue, not very confidence building.  I would recommend starting over with this drive too, clearing it, so that it has a correct MBR.

 

I also recommend changing the SATA drives to AHCI in the BIOS settings, may make a difference.

 

FYI:  Disk 1 has the Gigabyte HPA installed on it, so I would leave it where it is connected, to the first onboard SATA port.