After many years, I think one of the disks in my NSA325 is crashing.
This is output from "dmesg", showing I/O Errors:
$this->bbcode_second_pass_code('', '[ 34.438768] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem
[ 34.711275] EXT4-fs (sda1): warning: mounting unchecked fs, running e2fsck is recommended
[ 34.792416] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)
[ 40.164842] mv643xx_eth_port mv643xx_eth_port.0 eth0: link down
[ 40.230568] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 40.471920] 8021q: 802.1Q VLAN Support v1.8
[ 43.221589] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[ 43.231583] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 52.312645] NFSD: starting 90-second grace period (net c09161d0)
[ 67.397177] ata1.00: qc timeout (cmd 0x47)
[ 67.401319] ata1.00: READ LOG DMA EXT failed, trying unqueued
[ 67.407101] ata1: failed to read log page 10h (errno=-5)
[ 67.412448] ata1.00: exception Emask 0x1 SAct 0xa SErr 0x0 action 0x6 frozen
[ 67.419522] ata1.00: edma_err_cause=02000084 pp_flags=00000003, dev error, EDMA self-disable
[ 67.428007] ata1.00: failed command: READ FPDMA QUEUED
[ 67.433193] ata1.00: cmd 60/08:08:00:99:84/00:00:ac:00:00/40 tag 1 ncq 4096 in
res 41/40:18:00:cd:09/40:00:00:00:00/40 Emask 0x9 (media error)
[ 67.448226] ata1.00: status: { DRDY ERR }
[ 67.452293] ata1.00: error: { UNC }
[ 67.455799] ata1.00: failed command: READ FPDMA QUEUED
[ 67.460969] ata1.00: cmd 60/20:18:00:cd:09/00:00:00:00:00/40 tag 3 ncq 16384 in
res 41/40:18:00:cd:09/40:00:00:00:00/40 Emask 0x9 (media error)
[ 67.476339] ata1.00: status: { DRDY ERR }
[ 67.480362] ata1.00: error: { UNC }
[ 67.483882] ata1: hard resetting link
[ 67.991812] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[ 68.071839] ata1.00: configured for UDMA/133
[ 68.076167] sd 0:0:0:0: [sda] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 68.084401] sd 0:0:0:0: [sda] tag#1 Sense Key : 0x3 [current] [descriptor]
[ 68.091391] sd 0:0:0:0: [sda] tag#1 ASC=0x11 ASCQ=0x4
[ 68.096570] sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 ac 84 99 00 00 00 08 00
[ 68.104184] blk_update_request: I/O error, dev sda, sector 2894371072
[ 68.110816] sd 0:0:0:0: [sda] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 68.119049] sd 0:0:0:0: [sda] tag#3 Sense Key : 0x3 [current] [descriptor]
[ 68.126063] sd 0:0:0:0: [sda] tag#3 ASC=0x11 ASCQ=0x4
[ 68.131226] sd 0:0:0:0: [sda] tag#3 CDB: opcode=0x28 28 00 00 09 cd 00 00 00 20 00
[ 68.138843] blk_update_request: I/O error, dev sda, sector 642304
[ 68.145078] ata1: EH complete
[ 72.421873] ata1.00: exception Emask 0x0 SAct 0xc00000 SErr 0x0 action 0x6
[ 72.428781] ata1.00: edma_err_cause=02000084 pp_flags=00000003, dev error, EDMA self-disable
[ 72.437277] ata1.00: failed command: READ FPDMA QUEUED
[ 72.442459] ata1.00: cmd 60/b0:b0:58:ac:b5/00:00:5a:00:00/40 tag 22 ncq 90112 in
res 41/40:b8:00:cd:09/40:00:00:00:00/40 Emask 0x9 (media error)
[ 72.457663] ata1.00: status: { DRDY ERR }
[ 72.461688] ata1.00: error: { UNC }
[ 72.465195] ata1.00: failed command: READ FPDMA QUEUED
[ 72.470365] ata1.00: cmd 60/08:b8:00:cd:09/00:00:00:00:00/40 tag 23 ncq 4096 in
res 41/40:08:00:cd:09/00:00:00:00:00/00 Emask 0x409 (media error) <F>
[ 72.486259] ata1.00: status: { DRDY ERR }
[ 72.490281] ata1.00: error: { UNC }
[ 72.493801] ata1: hard resetting link
[ 73.001816] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[ 73.101837] ata1.00: configured for UDMA/133
[ 73.106181] sd 0:0:0:0: [sda] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 73.114498] sd 0:0:0:0: [sda] tag#22 Sense Key : 0x3 [current] [descriptor]
[ 73.121576] sd 0:0:0:0: [sda] tag#22 ASC=0x11 ASCQ=0x4
[ 73.126876] sd 0:0:0:0: [sda] tag#22 CDB: opcode=0x28 28 00 5a b5 ac 58 00 00 b0 00
[ 73.134582] blk_update_request: I/O error, dev sda, sector 1521855576
[ 73.141192] sd 0:0:0:0: [sda] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 73.149520] sd 0:0:0:0: [sda] tag#23 Sense Key : 0x3 [current] [descriptor]
[ 73.156608] sd 0:0:0:0: [sda] tag#23 ASC=0x11 ASCQ=0x4
[ 73.161884] sd 0:0:0:0: [sda] tag#23 CDB: opcode=0x28 28 00 00 09 cd 00 00 00 08 00
[ 73.169569] blk_update_request: I/O error, dev sda, sector 642304
[ 73.177080] ata1: EH complete
[ 321.641792] EXT4-fs (sda2): error count since last fsck: 14
[ 321.647400] EXT4-fs (sda2): initial error at time 1556589755: ext4_journal_check_start:56
[ 321.655621] EXT4-fs (sda2): last error at time 1556659779: ext4_do_update_inode:4697: inode 115527604: block 460854827
[86820.199968] EXT4-fs (sda2): error count since last fsck: 14
[86820.205577] EXT4-fs (sda2): initial error at time 1556589755: ext4_journal_check_start:56
[86820.213798] EXT4-fs (sda2): last error at time 1556659779: ext4_do_update_inode:4697: inode 115527604: block 460854827
')
Because I've been running this server for years without problems, I totally forgot how the system was setup.
I vaguely remember the two disks are setup to share space as one volume.
Luckily, I can still access my data (read-only), but I have not been able to run "e2fsck" as recommended. Seems the two disks are always automatically mounted on boot, and I am unable to unmount.
Any tips on how I can diagnose the problem, find out what disk is failing, and possibly how to recover from this?