Filesystem crash

Francois Tigeot ftigeot at wolfpond.org
Sat Jul 25 11:05:49 PDT 2015


Hi,

On Sat, Jul 25, 2015 at 05:33:31PM +0100, nans_nans1 at yahoo.de wrote:
> 
> during "buildworld" the compiling stops. I saw that the filesystem switched to "read-only".
> A dmesg -a gave me horrible messages (see below). Whats that?
> 
> #dmesg -a
> ahci1.1: Unrecoverable errors (IS: 8000002<IFS,PSS>, SERR: 1400000<DIAG.T,DIAG.H>), disabling port.
> ahci1.1: Failing all commands: 003f8000
> ahci1.1: disk_rw: timeout

[...]

> ahci1.1: REINIT - Attempting to reinitialize the port after it had a horrible accident
> ahci1.1: disk_rw: error
> ahci1.1: Waiting 10 seconds on insertion
> ahci1.1: PMPROBE(1) No Port Multiplier was found.
> ahci1.1: Found SSD "KINGSTON SMS200S360G 541ABBF0" serial="50026B7251144D35"
> (da1:ahci1:1:0:0): WRITE(10). CDB: 2a 0 1 5d 1e 40 0 0 20 0
> (da1:ahci1:1:0:0): CAM Status: SCSI Status Error
> (da1:ahci1:1:0:0): SCSI Status: Check Condition
> (da1:ahci1:1:0:0): MEDIUM ERROR asc:0,0
> (da1:ahci1:1:0:0): No additional sense information
> (da1:ahci1:1:0:0): Retrying Command (per Sense Data)
> ahci1.1: Unrecoverable errors (IS: 8000002<IFS,PSS>, SERR: 1400000<DIAG.T,DIAG.H>), disabling port.
> ahci1.1: Failing all commands: ff8003fd

It looks like your SSD has disconnected itself but can still somewhat be seen
if the operating system keeps insisting.

This is a hardware failure.

It could simply be a bad SATA cable or bad SATA connection but there is also a
very real possibility the SSD itself is failing.

-- 
Francois Tigeot



More information about the Users mailing list