Find the answer to your Linux question:
Results 1 to 4 of 4
Hello, i've recently(month-month and a half) build new a computer (details listed below) And under both windows and linux my ssd card seems very unstable. After some firmware updates and ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Dec 2009
    Posts
    7

    SSD 'freezes'


    Hello, i've recently(month-month and a half) build new a computer (details listed below)

    And under both windows and linux my ssd card seems very unstable. After some firmware updates and driver fixed windows does not bsod anymore but sometimes hangs. On Linux however i ofter find the following in 'dmesg':

    Code:
    [ 7543.367938] ata7.00: status: { DRDY }
    [ 7543.367985] ata7.00: failed command: WRITE FPDMA QUEUED
    [ 7543.368038] ata7.00: cmd 61/18:18:98:f4:5a/00:00:03:00:00/40 tag 3 ncq 12288 out
    [ 7543.368040]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 7543.368166] ata7.00: status: { DRDY }
    [ 7543.368216] ata7: hard resetting link
    [ 7543.912167] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 370)
    [ 7543.912808] ata7.00: configured for UDMA/100
    [ 7543.912814] ata7.00: device reported invalid CHS sector 0
    [ 7543.912819] ata7.00: device reported invalid CHS sector 0
    [ 7543.912829] ata7: EH complete
    [ 7568.775726] lo: Disabled Privacy Extensions
    [ 7568.871714] EXT4-fs (sdb3): re-mounted. Opts: errors=remount-ro,commit=0
    [12724.141678] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x180000 action 0x6 frozen
    [12724.141685] ata7: SError: { 10B8B Dispar }
    [12724.141688] ata7.00: failed command: FLUSH CACHE
    [12724.141696] ata7.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0
    [12724.141697]          res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    [12724.141701] ata7.00: status: { DRDY }
    [12724.141706] ata7: hard resetting link
    [12724.689309] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 370)
    [12724.690054] ata7.00: configured for UDMA/100
    [12724.690059] ata7.00: retrying FLUSH 0xe7 Emask 0x4
    [12724.692961] ata7.00: device reported invalid CHS sector 0
    [12724.692969] ata7: EH complete
    [33802.071030] ata7.00: exception Emask 0x0 SAct 0x3ff SErr 0x180000 action 0x6 frozen
    [33802.071037] ata7: SError: { 10B8B Dispar }
    [33802.071041] ata7.00: failed command: WRITE FPDMA QUEUED
    [33802.071049] ata7.00: cmd 61/08:00:10:48:0d/00:00:04:00:00/40 tag 0 ncq 4096 out
    [33802.071051]          res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    [33802.071054] ata7.00: status: { DRDY }
    [33802.071057] ata7.00: failed command: WRITE FPDMA QUEUED
    [33802.071065] ata7.00: cmd 61/08:08:28:48:4d/00:00:03:00:00/40 tag 1 ncq 4096 out
    [33802.071066]          res 40/00:14:48:95:41/00:00:03:00:00/40 Emask 0x4 (timeout)
    [33802.071070] ata7.00: status: { DRDY }
    [33802.071073] ata7.00: failed command: WRITE FPDMA QUEUED
    [33802.071080] ata7.00: cmd 61/08:10:90:48:8d/00:00:03:00:00/40 tag 2 ncq 4096 out
    [33802.071082]          res 40/00:14:48:95:41/00:00:03:00:00/40 Emask 0x4 (timeout)
    [33802.071085] ata7.00: status: { DRDY }
    [33802.071088] ata7.00: failed command: WRITE FPDMA QUEUED
    [33802.071095] ata7.00: cmd 61/08:18:e0:5e:8d/00:00:03:00:00/40 tag 3 ncq 4096 out
    [33802.071097]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [33802.071100] ata7.00: status: { DRDY }
    [33802.071103] ata7.00: failed command: WRITE FPDMA QUEUED
    [33802.071110] ata7.00: cmd 61/10:20:00:6d:8d/00:00:03:00:00/40 tag 4 ncq 8192 out
    [33802.071112]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [33802.071115] ata7.00: status: { DRDY }
    [33802.071118] ata7.00: failed command: WRITE FPDMA QUEUED
    [33802.071125] ata7.00: cmd 61/08:28:b0:86:8e/00:00:03:00:00/40 tag 5 ncq 4096 out
    [33802.071126]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [33802.071130] ata7.00: status: { DRDY }
    [33802.071133] ata7.00: failed command: WRITE FPDMA QUEUED
    [33802.071140] ata7.00: cmd 61/08:30:60:57:cd/00:00:03:00:00/40 tag 6 ncq 4096 out
    [33802.071141]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [33802.071145] ata7.00: status: { DRDY }
    [33802.071148] ata7.00: failed command: WRITE FPDMA QUEUED
    [33802.071155] ata7.00: cmd 61/08:38:10:5c:cd/00:00:03:00:00/40 tag 7 ncq 4096 out
    [33802.071156]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [33802.071160] ata7.00: status: { DRDY }
    [33802.071163] ata7.00: failed command: WRITE FPDMA QUEUED
    [33802.071170] ata7.00: cmd 61/08:40:70:72:4d/00:00:04:00:00/40 tag 8 ncq 4096 out
    [33802.071171]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [33802.071175] ata7.00: status: { DRDY }
    [33802.071178] ata7.00: failed command: WRITE FPDMA QUEUED
    [33802.071184] ata7.00: cmd 61/08:48:38:81:5c/00:00:03:00:00/40 tag 9 ncq 4096 out
    [33802.071186]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [33802.071190] ata7.00: status: { DRDY }
    [33802.071195] ata7: hard resetting link
    [33802.617156] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 370)
    [33802.617928] ata7.00: configured for UDMA/100
    [33802.617935] ata7.00: device reported invalid CHS sector 0
    [33802.617939] ata7.00: device reported invalid CHS sector 0
    [33802.617942] ata7.00: device reported invalid CHS sector 0
    [33802.617945] ata7.00: device reported invalid CHS sector 0
    [33802.617948] ata7.00: device reported invalid CHS sector 0
    [33802.617950] ata7.00: device reported invalid CHS sector 0
    [33802.617953] ata7.00: device reported invalid CHS sector 0
    [33802.617956] ata7.00: device reported invalid CHS sector 0
    [33802.617971] ata7: EH complete
    [40654.136797] ata7.00: exception Emask 0x0 SAct 0x6 SErr 0x180000 action 0x6 frozen
    [40654.136804] ata7: SError: { 10B8B Dispar }
    [40654.136808] ata7.00: failed command: WRITE FPDMA QUEUED
    [40654.136816] ata7.00: cmd 61/10:08:70:68:6f/00:00:03:00:00/40 tag 1 ncq 8192 out
    [40654.136818]          res 40/00:14:48:95:41/00:00:03:00:00/40 Emask 0x4 (timeout)
    [40654.136821] ata7.00: status: { DRDY }
    [40654.136825] ata7.00: failed command: WRITE FPDMA QUEUED
    [40654.136832] ata7.00: cmd 61/08:10:30:82:5c/00:00:03:00:00/40 tag 2 ncq 4096 out
    [40654.136833]          res 40/00:14:48:95:41/00:00:03:00:00/40 Emask 0x4 (timeout)
    [40654.136837] ata7.00: status: { DRDY }
    [40654.136843] ata7: hard resetting link
    [40654.685280] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 370)
    [40654.685922] ata7.00: configured for UDMA/100
    [40654.685934] ata7: EH complete
    And when it actually 'crashes' it's just the ssd which is frozen (downloads with go to another hdd continue for example) i get some other but similar error, next time i'll write it down and post it here.

    I have no idea if it's the motherboard or the ssd, it does not seems to be de sata3 card cause if i connect the ssd directly to a sata2 port on the motherboard i get the same freezes.

    Could anyone provide me with pointers how to find the problem?

    SSD crucial C300 64gb - connected via an marvell sata3 pci card - AHCI
    Asrock p55 deluxe
    nvidia gts 450
    intel core i5 - 760

  2. #2
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, in Chicago, or in a galaxy far, far away.
    Posts
    11,533
    From what you describe, it has to be a faulty card. With a Linux file system (or ntfs) you can map out bad sectors to keep using the device until you get a replacement. What file system is running on the card? Since you are running both Windows and Linux with it, I have to assume either FAT32 or NTFS. If FAT32, then change it to NTFS, and run the full disc scan for bad blocks. They will be mapped out of use by the file system. Remember that current flash technology has a limited number of write cycles, though the disc onboard controller should implement a wear-leveling algorithm in order to spread that write load across all sectors in order to lengthen the time-to-failure.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  3. #3
    Just Joined!
    Join Date
    Dec 2009
    Posts
    7
    Thanks for your reply.

    Actually the ssd card is not the problem it seems.

    I've looked in to it some more, and when i connect the ssd to a sata2 slot (on the motherboard) it works perfectly, although slower than the sata3 which is to be expected.

    And when i connect a hdd to the marvell sata3 slot it gets errors aswell, quite the same as when i connect the ssd infact.

    Could it be that linux has problems with the sata3 pci card? if so how can i proceed in trying to get it to work?

  4. #4
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, in Chicago, or in a galaxy far, far away.
    Posts
    11,533
    Well, remember that until very recently, sata3 was a "draft" standard. It is possible that newer devices won't work well with older ones, even though they are purportedly sata3. Is there a way to force the PCI card to use sata2 to communicate with the storage device, or to force the storage device into sata2? I know that sata3 controllers are supposed to work with sata1 or sata2 storage devices if they are connected to it.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •