File system has become read only suddenly

This is a new one to me. I thought i had seen all possible issues with these drives.

So out of no where today, when i woke up and saw that a transmission torren download was stuck with an error  message

“Error: Read-only file system”. At first I thought this was an issue with transmissin etc…

Then i find out that the entire drive has become read only. i have ssh access.

The persmissions are still fine. None of the disk partition is full or anything…

nas1:/shares/Public# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 1.9G 920M 906M 51% /
/dev/root 1.9G 920M 906M 51% /
tmpfs 40M 4.9M 36M 13% /run
tmpfs 40M 128K 40M 1% /run/lock
tmpfs 10M 0 10M 0% /dev
tmpfs 5.0M 0 5.0M 0% /run/shm
tmpfs 100M 2.2M 98M 3% /tmp
/dev/root 1.9G 920M 906M 51% /var/log.hdd
ramlog-tmpfs 20M 13M 7.7M 62% /var/log
/dev/sda4 2.7T 1.3T 1.4T 50% /DataVolume
/dev/sda4 2.7T 1.3T 1.4T 50% /CacheVolume
/dev/sda4 2.7T 1.3T 1.4T 50% /nfs/personal
/dev/sda4 2.7T 1.3T 1.4T 50% /nfs/data
/dev/sda4 2.7T 1.3T 1.4T 50% /nfs/Public
/dev/sda4 2.7T 1.3T 1.4T 50% /nfs/backups

drwxrwxrwx+ 3 ali share 4096 Feb 26 23:00 Avant-2_BMW_E46_05-11-2014_Update
-rwxrwxrwx+ 1 ali share 336869457 Jun 14 2014 Avant-2_BMW_E46_Software_Update_06-13-2014_BETA.zip
drwxrwxrwx+ 3 ali share 4096 Feb 26 23:00 Avant-2_BMW_E46_Software_Update_06-16-2014_BETA
drwxrwxrwx+ 3 ali share 4096 Feb 26 23:00 Avant-2_BMW_E46_Software_Update_06-26-2014_BETA
drwxrwxrwx+ 3 ali share 4096 Feb 26 23:01 Avant-2_BMW_E46_Software_Update_07-10-2014_BETA
drwxrwxrwx+ 3 ali share 4096 Feb 26 23:01 Avant-2_BMW_E46_Software_Update_07-18-2014_BETA_CD
drwxrwxrwx+ 3 ali share 4096 Feb 26 23:01 Avant-2_BMW_E46_Software_Update_july_07-06-2014_BETA
drwxrwxrwx+ 3 ali share 4096 Feb 26 23:01 Avant-2_BMW_Software_Update_10-31-2014_MirrorLink_BETA

nas1:/shares/data/Drivers/Android/Avin# rm Avant-2_BMW_E46_Software_Update_06-13-2014_BETA.zip
rm: remove regular file Avant-2\_BMW\_E46\_Software\_Update\_06-13-2014\_BETA.zip'? y rm: cannot removeAvant-2_BMW_E46_Software_Update_06-13-2014_BETA.zip’: Read-only file system

mount command shows read only also

/dev/sda4 on /DataVolume type ext4 (ro,noatime,nodiratime,user_xattr,barrier=0,data=writeback)

/dev/sda4 on /CacheVolume type ext4 (ro,noatime,nodiratime,user_xattr,barrier=0,data=writeback)

A reboot might fix the issue, but i would like to know why this happened.Also im afraid that a reboot might fail and cause to loose access to the data.

Help please

The Kernel will move a file system to READ ONLY if it detects certain errors.

the output of “dmesg” might indicate what happened.

hmmm running that command does show some errors:

Note that this is new drive i got from WD. But i opened it up and copied over EVERYthing from my old WD drive using the “dd” command to copy ALL partiions to the new one. Long story behind why i did that. My old drive never had this issue. They were both on the same FW.

You think i should do a system restore? I’m afraid of doing that as in the past i’ve always lost dashboard login after a reset.

[26143.495832] ata1.00: status: { DRDY DF ERR }
[26143.500135] ata1.00: error: { ABRT }
[26148.580559] ata1.00: configured for UDMA/100
[26148.584886] ata1.00: device reported invalid CHS sector 0
[26148.590362] ata1: EH complete
[26153.838813] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[26153.845298] ata1.00: irq_stat 0x40000000
[26153.849266] ata1.00: failed command: FLUSH CACHE EXT
[26153.854278] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[26153.854284] res 61/04:00:00:80:98/00:00:ff:ff:ff/a0 Emask 0x1 (device error)
[26153.868372] ata1.00: status: { DRDY DF ERR }
[26153.872666] ata1.00: error: { ABRT }
[26161.660348] ata1.00: configured for UDMA/100
[26161.664661] ata1.00: device reported invalid CHS sector 0
[26161.670145] ata1: EH complete
[26167.077544] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[26167.084046] ata1.00: irq_stat 0x40000000
[26167.087995] ata1.00: failed command: FLUSH CACHE EXT
[26167.093016] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[26167.093022] res 61/04:00:00:80:98/00:00:ff:ff:ff/a0 Emask 0x1 (device error)
[26167.107116] ata1.00: status: { DRDY DF ERR }
[26167.111423] ata1.00: error: { ABRT }
[26172.188504] ata1.00: configured for UDMA/100
[26172.192817] ata1.00: device reported invalid CHS sector 0
[26172.198356] ata1: EH complete
[26177.304879] ata1.00: limiting speed to UDMA/33:PIO4
[26177.309834] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[26177.316311] ata1.00: irq_stat 0x40000000
[26177.320281] ata1.00: failed command: READ DMA
[26177.324692] ata1.00: cmd c8/00:80:b0:b2:37/00:00:00:00:00/e0 tag 0 dma 65536 in
[26177.324700] res 41/04:80:b0:b2:37/00:00:00:00:00/e0 Emask 0x1 (device error)
[26177.339925] ata1.00: status: { DRDY ERR }
[26177.343958] ata1.00: error: { ABRT }
[26177.347569] ata1: hard resetting link
[26187.388250] ata1: softreset failed (device not ready)
[26187.393343] ata1: hard resetting link
[26197.418251] ata1: softreset failed (device not ready)
[26197.423343] ata1: hard resetting link
[26208.048518] ata1: link is slow to respond, please be patient (ready=0)
[26232.468259] ata1: softreset failed (device not ready)
[26232.473354] ata1: hard resetting link
[26234.698264] ata1: SATA link down (SStatus 1 SControl 310)
[26239.698251] ata1: hard resetting link
[26243.668259] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[26243.675618] ata1.00: configured for UDMA/33
[26243.679979] ata1: EH complete
[26243.730046] EXT3-fs (md0): error in ext3_new_inode: IO failure
[31328.994667] EXT4-fs error (device sda4): ext4_remount:4538: Abort forced by user
[31329.002217] EXT4-fs (sda4): re-mounted. Opts: user_xattr,barrier=0,data=writeback,noinit_itable
[31329.595694] md: cannot remove active disk sda1 from md0 …
[31329.685819] md: unbind
[31329.738296] md: export_rdev(sda2)
[31329.905086] md: export_rdev(sda2)
[31330.756954] md: bind
[31332.153840] RAID1 conf printout:
[31332.157117] — wd:1 rd:2
[31332.159918] disk 0, wo:0, o:1, dev:sda1
[31332.163878] disk 1, wo:1, o:1, dev:sda2
[31332.172419] md: recovery of RAID array md0
[31332.176580] md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
[31332.182496] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
[31332.192151] md: using 2048k window, over a total of 1999808k.
[31784.241514] md: md0: recovery done.
[31784.857194] RAID1 conf printout:
[31784.860505] — wd:2 rd:2
[31784.863234] disk 0, wo:0, o:1, dev:sda1
[31784.867181] disk 1, wo:0, o:1, dev:sda2
[31786.682392] EXT4-fs error (device sda4): ext4_remount:4538: Abort forced by user
[31786.689928] EXT4-fs (sda4): re-mounted. Opts: user_xattr,barrier=0,data=writeback,noinit_itable,init_itable=10
nas1:/DataVolume#

ok i rebooted and now the drive is stuck on a blinking white led. Dashboard comes up but shows “initialising device”

Lost ssh access  @##MF#$#$

Do  just leave it like that for now?

Edit: After about 30 min of bliking white led, the drive came back online.

Is there something i can run to verify partition structure etc…without wiping my data…

UPDATE

no luck saving data. Had to do a quick restore from dashboard and that seems to have fixed the filesystem…
I thought I knew a lot about these drives but today I learnt A LOT more…good for future issues :slight_smile: