March 4, 201610 yr Hi All, Today my server didnt startup properly. I noticed that docker didnt start and i couldnt get it to work either. So i thought it was my SSD. I couldnt write to it and also couldnt setup a new Docker img since i was thinking it went corrupt or something. So i reformatted the SSD as XFS and then back to btrfs. Then added the docker folder to it and tried to enable docker again so it would build a new docker_img. But it didnt work again. I noticed this in the logfile: Mar 4 20:21:05 Tower kernel: [<ffffffff81115977>] vfs_kern_mount+0x5f/0xf8 Mar 4 20:21:05 Tower kernel: [<ffffffff8111856f>] do_mount+0x985/0xa7c Mar 4 20:21:05 Tower kernel: [<ffffffff810c5753>] ? strndup_user+0x37/0x82 Mar 4 20:21:05 Tower kernel: [<ffffffff81118878>] SyS_mount+0x72/0xa1 Mar 4 20:21:05 Tower kernel: [<ffffffff815f74ee>] system_call_fastpath+0x12/0x71 Mar 4 20:21:05 Tower kernel: ---[ end trace 7ba2021ff8dff0e8 ]--- Mar 4 20:21:05 Tower kernel: BTRFS: error (device loop0) in cleanup_transaction:1692: errno=-5 IO failure Mar 4 20:21:05 Tower kernel: BTRFS info (device loop0): delayed_refs has NO entry Mar 4 20:21:05 Tower kernel: BTRFS: failed to create the UUID tree -5 Mar 4 20:21:05 Tower kernel: BTRFS error (device loop0): commit super ret -30 Mar 4 20:21:05 Tower kernel: ata2: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen Mar 4 20:21:05 Tower kernel: ata2: irq_stat 0x00000040, connection status changed Mar 4 20:21:05 Tower kernel: ata2: SError: { CommWake DevExch } Mar 4 20:21:05 Tower kernel: ata2: hard resetting link Mar 4 20:21:05 Tower kernel: sd 3:0:0:0: [sdi] Synchronizing SCSI cache Mar 4 20:21:05 Tower logger: Not starting Docker: mount error Mar 4 20:21:05 Tower kernel: BTRFS: open_ctree failed Mar 4 20:21:06 Tower kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 4 20:21:06 Tower kernel: ata2.00: supports DRM functions and may not be fully accessible Mar 4 20:21:06 Tower kernel: ata2.00: disabling queued TRIM support Mar 4 20:21:06 Tower kernel: ata2.00: ATA-9: Crucial_CT256MX100SSD1, 14320CE5C111, MU01, max UDMA/133 Mar 4 20:21:06 Tower kernel: ata2.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Mar 4 20:21:06 Tower kernel: ata2.00: supports DRM functions and may not be fully accessible Mar 4 20:21:06 Tower kernel: ata2.00: disabling queued TRIM support Mar 4 20:21:06 Tower kernel: ata2.00: configured for UDMA/133 Mar 4 20:21:06 Tower kernel: ata2: EH complete Mar 4 20:21:06 Tower kernel: sd 3:0:0:0: [sdi] Stopping disk Mar 4 20:21:06 Tower kernel: scsi 3:0:0:0: Direct-Access ATA Crucial_CT256MX1 MU01 PQ: 0 ANSI: 5 Mar 4 20:21:06 Tower kernel: ata2.00: Enabling discard_zeroes_data Mar 4 20:21:06 Tower kernel: sd 3:0:0:0: [sdb] 500118192 512-byte logical blocks: (256 GB/238 GiB) Mar 4 20:21:06 Tower kernel: sd 3:0:0:0: [sdb] 4096-byte physical blocks Mar 4 20:21:06 Tower kernel: sd 3:0:0:0: [sdb] Write Protect is off Mar 4 20:21:06 Tower kernel: sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Mar 4 20:21:06 Tower kernel: sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 4 20:21:06 Tower kernel: ata2.00: Enabling discard_zeroes_data Mar 4 20:21:06 Tower kernel: sd 3:0:0:0: Attached scsi generic sg1 type 0 Mar 4 20:21:06 Tower kernel: sdb: sdb1 Mar 4 20:21:06 Tower kernel: ata2.00: Enabling discard_zeroes_data Mar 4 20:21:06 Tower kernel: sd 3:0:0:0: [sdb] Attached SCSI disk Can anyone tell me what is going on and how to solve this? Is my SSD dead or is it some configuration issue? tower-diagnostics-20160304-2049.zip
March 5, 201610 yr Community Expert Device Model: Crucial_CT256MX100SSD1 Serial Number: 14320CE5C111 199 UDMA_CRC_Error_Count 0x0032 100 100 000 Old_age Always - 30523 Replace sata cable, if it continues to increase try different sata port.
March 7, 201610 yr Author I have replaced the sata cable and added it on a different sata port. Also i have precleared the SDD succesfully and it seams to be working fine again. Hopefully it will continue to do so.
March 8, 201610 yr Go to Crucial's site and confirm you've got the latest firmware for your MX100 ... and upgrade it if not. http://www.crucial.com/usa/en/support-ssd-firmware The firmware update significantly improves the stability and reliability of the drive.
March 8, 201610 yr ... Note: You'll need to attach the SSD to a Windows system to run the Storage Executive to check the firmware version and do the upgrade
Archived
This topic is now archived and is closed to further replies.