Code: Select all
WARNING: Kernel Errors Present
ata3.00: irq_stat 0x08000000, interface fatal error ...: 1 Time(s)
ata3: SError: { CommWake 10B8 ...: 1 Time(s)
1 Time(s): ata3.00: cmd 61/00:00:f8:8e:aa/04:00:03:00:00/40 tag 0 ncq 524288 out
1 Time(s): ata3.00: cmd 61/00:08:f8:92:aa/04:00:03:00:00/40 tag 1 ncq 524288 out
1 Time(s): ata3.00: cmd 61/00:10:f8:96:aa/04:00:03:00:00/40 tag 2 ncq 524288 out
...
1 Time(s): ata3.00: cmd 61/00:f0:f8:8a:aa/04:00:03:00:00/40 tag 30 ncq 524288 out
1 Time(s): ata3.00: configured for UDMA/133
1 Time(s): ata3.00: exception Emask 0x10 SAct 0x7fffffff SErr 0x4c0000 action 0x6 frozen
31 Time(s): ata3.00: failed command: WRITE FPDMA QUEUED
31 Time(s): ata3.00: status: { DRDY }
1 Time(s): ata3: EH complete
1 Time(s): ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
1 Time(s): ata3: hard resetting link
The disk I have attached to Sata-3 is a secondary disk (not used for the O/S partitions). I'm trying to check the disk health but am running into problems and could use some help. When I 'umount' it, I can run fsck, but then within a few minutes, the disk is mounted again. I'm guessing something auto-mounts it? Here is what I see in /var/log/messages:
Code: Select all
Dec 20 10:32:06 stargate kernel: sdb: sdb1
Dec 20 10:32:07 stargate systemd: Mounting /meh...
Dec 20 10:32:07 stargate kernel: XFS (sdb1): Mounting V4 Filesystem
Dec 20 10:32:07 stargate kernel: XFS (sdb1): Ending clean mount
Dec 20 10:32:07 stargate systemd: Mounted /meh.
During the time it is unmounted, I run fsck passing the device (/dev/sdb) of the disk and get the following error:
Code: Select all
# fsck /dev/sdb
fsck from util-linux 2.23.2
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Thanks for any help.