The Corsair User Forums  

Go Back   The Corsair User Forums > Corsair Product Discussion > Solid State Drives (SSD)

Notices

Reply
 
Thread Tools Search this Thread Rating: Thread Rating: 6 votes, 5.00 average. Display Modes
  #1  
Old 10-25-2011, 05:00 PM
edwinclout edwinclout is offline
Registered User
 
Join Date: Sep 2011
Posts: 2
POST ID # = 537284
edwinclout Reputation: 10
Default Corsair 120GB Force 3 SSD with Linux

Hi Guys and Guyettes,


I have just bought a Corsair 120GB Force 3 to try and speed up this Core2Duo laptop.

The laptop has a Silicon Integrated Systems (SiS) chipset, which includes an SiS968 Southbridge that provides support for SATA2.

The original internal HDD has been replaced by the Corsair.

I have tried installing Debian testing and Ubuntu 11.10 onto the new Corsair SSD, but am hitting the same issue..

This from the kernel syslog..
Code:
Oct 25 17:42:20 kernel: [    1.447477] libata version 3.00 loaded.
Oct 25 17:42:20 kernel: [    1.455693] pata_sis 0000:00:02.5: version 0.5.2

Oct 25 17:42:20 kernel: [    1.480712] pata_sis 0000:00:02.5: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Oct 25 17:42:20 kernel: [    1.493927] scsi0 : pata_sis
Oct 25 17:42:20 kernel: [    1.505575] scsi1 : pata_sis
Oct 25 17:42:20 kernel: [    1.516947] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x1080 irq 14
Oct 25 17:42:20 kernel: [    1.528328] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1088 irq 15

Oct 25 17:42:20 kernel: [    1.744260] ata1.00: ATAPI: TSSTcorp CDDVDW TS-L632H, TMC0, max UDMA/33
Oct 25 17:42:20 kernel: [    1.788233] ata1.00: configured for UDMA/33
Oct 25 17:42:20 kernel: [    1.800281] Refined TSC clocksource calibration: 1999.975 MHz.
Oct 25 17:42:20 kernel: [    1.812522] Switching to clocksource tsc
Oct 25 17:42:20 kernel: [    1.825711] scsi 0:0:0:0: CD-ROM            TSSTcorp CDDVDW TS-L632H  TMC0 PQ: 0 ANSI: 5
Oct 25 17:42:20 kernel: [    1.838030] ata2: port disabled. ignoring.

Oct 25 17:42:20 kernel: [    1.880495] sata_sis 0000:00:05.0: version 1.0
Oct 25 17:42:20 kernel: [    1.880534] sata_sis 0000:00:05.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Oct 25 17:42:20 kernel: [    1.880540] sata_sis 0000:00:05.0: Detected SiS 1183/966/966L/968/680 controller in PATA mode
Oct 25 17:42:20 kernel: [    1.947251] scsi2 : sata_sis
Oct 25 17:42:20 kernel: [    1.947388] scsi3 : sata_sis
Oct 25 17:42:20 kernel: [    1.947932] ata3: PATA max UDMA/133 cmd 0x10c8 ctl 0x10bc bmdma 0x10a0 irq 17
Oct 25 17:42:20 kernel: [    1.947935] ata4: PATA max UDMA/133 cmd 0x10c0 ctl 0x10b8 bmdma 0x10a8 irq 17

Oct 25 17:42:20 kernel: [    7.480035] ata3.00: qc timeout (cmd 0x27)
Oct 25 17:42:20 kernel: [    7.493502] ata3.00: failed to read native max address (err_mask=0x4)
Oct 25 17:42:20 kernel: [    7.507191] ata3.00: HPA support seems broken, skipping HPA handling
Oct 25 17:42:20 kernel: [    7.708215] ata3.00: ATA-8: Corsair Force 3 SSD, 1.3, max UDMA/133
Oct 25 17:42:20 kernel: [    7.721907] ata3.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 0/32)
Oct 25 17:42:20 kernel: [    7.756209] ata3.00: configured for UDMA/133
Oct 25 17:42:20 kernel: [    7.770092] scsi 2:0:0:0: Direct-Access     ATA      Corsair Force 3  1.3  PQ: 0 ANSI: 5
Oct 25 17:42:20 kernel: [    7.955617] sr 0:0:0:0: Attached scsi generic sg0 type 5
Oct 25 17:42:20 kernel: [    7.976509] scsi 2:0:0:0: Attached scsi generic sg1 type 0
Oct 25 17:42:20 kernel: [    7.991283] sd 2:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/111 GiB)
Oct 25 17:42:20 kernel: [    8.007956] sd 2:0:0:0: [sda] Write Protect is off
Oct 25 17:42:20 kernel: [    8.021802] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
Oct 25 17:42:20 kernel: [    8.022424] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Oct 25 17:42:20 kernel: [    8.051637]  sda: sda1 sda2 < sda5 >
Oct 25 17:42:20 kernel: [    8.066370] sd 2:0:0:0: [sda] Attached SCSI disk

Oct 25 17:42:20 kernel: [   38.848028] ata3: lost interrupt (Status 0x58)
Oct 25 17:42:20 kernel: [   38.863129] ata3: drained 512 bytes to clear DRQ.
Oct 25 17:42:20 kernel: [   38.863138] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 25 17:42:20 kernel: [   38.877849] ata3.00: failed command: IDENTIFY DEVICE
Oct 25 17:42:20 kernel: [   38.892153] ata3.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
Oct 25 17:42:20 kernel: [   38.892155]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 25 17:42:20 kernel: [   38.920958] ata3.00: status: { DRDY }
Oct 25 17:42:20 kernel: [   38.920986] ata3: soft resetting link
Oct 25 17:42:20 kernel: [   39.212209] ata3.00: configured for UDMA/133
Oct 25 17:42:20 kernel: [   39.226301] ata3: EH complete

Oct 25 17:43:26 kernel: [  104.928061] ata3: lost interrupt (Status 0x58)
Oct 25 17:43:26 kernel: [  104.928430] ata3: drained 512 bytes to clear DRQ.
Oct 25 17:43:26 kernel: [  104.928438] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 25 17:43:26 kernel: [  104.928442] ata3.00: failed command: IDENTIFY DEVICE
Oct 25 17:43:26 kernel: [  104.928448] ata3.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
Oct 25 17:43:26 kernel: [  104.928449]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 25 17:43:26 kernel: [  104.928452] ata3.00: status: { DRDY }
Oct 25 17:43:26 kernel: [  104.928477] ata3: soft resetting link
Oct 25 17:43:26 kernel: [  105.124210] ata3.00: configured for UDMA/133
Oct 25 17:43:26 kernel: [  105.124229] ata3: EH complete

Oct 25 17:45:07 kernel: [  205.920025] ata3: lost interrupt (Status 0x58)
Oct 25 17:45:07 kernel: [  205.920394] ata3: drained 512 bytes to clear DRQ.
Oct 25 17:45:07 kernel: [  205.920402] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 25 17:45:07 kernel: [  205.920406] ata3.00: failed command: IDENTIFY DEVICE
Oct 25 17:45:07 kernel: [  205.920412] ata3.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
Oct 25 17:45:07 kernel: [  205.920414]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 25 17:45:07 kernel: [  205.920417] ata3.00: status: { DRDY }
Oct 25 17:45:07 kernel: [  205.920442] ata3: soft resetting link
Oct 25 17:45:07 kernel: [  206.180210] ata3.00: configured for UDMA/133
Oct 25 17:45:07 kernel: [  206.180230] ata3: EH complete

Oct 25 17:47:16 kernel: [  334.880026] ata3: lost interrupt (Status 0x58)
Oct 25 17:47:16 kernel: [  334.880395] ata3: drained 512 bytes to clear DRQ.
Oct 25 17:47:16 kernel: [  334.880405] ata3.00: limiting speed to UDMA/100:PIO4
Oct 25 17:47:16 kernel: [  334.880409] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 25 17:47:16 kernel: [  334.880413] ata3.00: failed command: IDENTIFY DEVICE
Oct 25 17:47:16 kernel: [  334.880419] ata3.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
Oct 25 17:47:16 kernel: [  334.880420]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 25 17:47:16 kernel: [  334.880423] ata3.00: status: { DRDY }
Oct 25 17:47:16 kernel: [  334.880449] ata3: soft resetting link
Oct 25 17:47:16 kernel: [  335.116210] ata3.00: configured for UDMA/100
Oct 25 17:47:16 kernel: [  335.116229] ata3: EH complete

Oct 25 17:48:18 kernel: [  396.896022] ata3: lost interrupt (Status 0x50)
Oct 25 17:48:18 kernel: [  396.896040] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 25 17:48:18 kernel: [  396.896044] ata3.00: failed command: FLUSH CACHE
Oct 25 17:48:18 kernel: [  396.896049] ata3.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Oct 25 17:48:18 kernel: [  396.896051]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 25 17:48:18 kernel: [  396.896054] ata3.00: status: { DRDY }
Oct 25 17:48:18 kernel: [  396.896079] ata3: soft resetting link
Oct 25 17:48:18 kernel: [  397.164210] ata3.00: configured for UDMA/100
Oct 25 17:48:18 kernel: [  397.164214] ata3.00: retrying FLUSH 0xe7 Emask 0x4
Oct 25 17:48:33 kernel: [  412.164027] ata3.00: qc timeout (cmd 0xe7)
Oct 25 17:48:33 kernel: [  412.164032] ata3.00: FLUSH failed Emask 0x4
Oct 25 17:48:33 kernel: [  412.164054] ata3: soft resetting link
Oct 25 17:48:33 kernel: [  412.400209] ata3.00: configured for UDMA/100
Oct 25 17:48:33 kernel: [  412.400213] ata3.00: retrying FLUSH 0xe7 Emask 0x4
Oct 25 17:48:48 kernel: [  427.400031] ata3.00: qc timeout (cmd 0xe7)
Oct 25 17:48:48 kernel: [  427.400037] ata3.00: FLUSH failed Emask 0x4
Oct 25 17:48:48 kernel: [  427.400042] ata3.00: limiting speed to UDMA/100:PIO3
Oct 25 17:48:48 kernel: [  427.400068] ata3: soft resetting link
Oct 25 17:48:49 kernel: [  427.596210] ata3.00: configured for UDMA/100
Oct 25 17:48:49 kernel: [  427.596213] ata3.00: retrying FLUSH 0xe7 Emask 0x4
Oct 25 17:49:19 kernel: [  457.596031] ata3.00: qc timeout (cmd 0xe7)
Oct 25 17:49:19 kernel: [  457.596037] ata3.00: FLUSH failed Emask 0x4
Oct 25 17:49:19 kernel: [  457.596040] ata3.00: disabled
Oct 25 17:49:19 kernel: [  457.596056] ata3.00: device reported invalid CHS sector 0
Oct 25 17:49:19 kernel: [  457.596082] ata3: soft resetting link
Oct 25 17:49:19 ata_id[4852]: HDIO_GET_IDENTITY failed for '/dev/sda': No message of desired type
Oct 25 17:49:19 kernel: [  457.752059] ata3: EH complete
Oct 25 17:49:19 kernel: [  457.752300] sd 2:0:0:0: [sda] READ CAPACITY(16) failed
Oct 25 17:49:19 kernel: [  457.752303] sd 2:0:0:0: [sda]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Oct 25 17:49:19 kernel: [  457.752308] sd 2:0:0:0: [sda] Sense not available.
Oct 25 17:49:19 kernel: [  457.752342] sd 2:0:0:0: [sda] READ CAPACITY failed
Oct 25 17:49:19 kernel: [  457.752344] sd 2:0:0:0: [sda]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Oct 25 17:49:19 kernel: [  457.752348] sd 2:0:0:0: [sda] Sense not available.
Oct 25 17:49:19 kernel: [  457.752407] sd 2:0:0:0: [sda] Asking for cache data failed
Oct 25 17:49:19 kernel: [  457.752409] sd 2:0:0:0: [sda] Assuming drive cache: write through
Oct 25 17:49:19 kernel: [  457.752417] sda: detected capacity change from 120034123776 to 0
Would flashing the SSD firmware maybe help? Is it possible to determine the firmware version that is currently on the drive?

Any clues for resolving this issue would be greatly appreciately as I am impatiently wanting to enjoy the benefits of the SSD :-)

Cheers,
edwin


EDIT: A few links to those having similar problems in Linux with SSDs other than Corsair..

http://OCZtechnologyforum.com/forum/...ork-with-linux
https://bugs.launchpad.net/ubuntu/+s...ux/+bug/574462
https://bugs.launchpad.net/ubuntu/+bug/555451

Last edited by edwinclout; 10-25-2011 at 05:27 PM.
Reply With Quote


  #2  
Old 10-28-2011, 05:56 PM
semlanik semlanik is offline
Registered User
semlanik's PC Specs
 
Join Date: Oct 2011
Location: Russia
Posts: 1
POST ID # = 537993
semlanik Reputation: 10
Default

Looks like corsair does't support linux users.
Reply With Quote


  #3  
Old 10-30-2011, 05:14 PM
lxtwin lxtwin is offline
Registered User
lxtwin's PC Specs
 
Join Date: Mar 2009
Posts: 52
POST ID # = 538248
lxtwin Reputation: 10
Default

Hi mate,

I run Ubuntu 11.10, and do not see these issues at all. However I notice that your scsi device says "scsi0 : pata_sis" mine say "scsi0 : ahci"

What SATA connection care you using ? what mode is it ?


Code:
kernel: [    2.314017] scsi0 : ahci
kernel: [    2.314118] scsi1 : ahci
kernel: [    2.314199] scsi2 : ahci
kernel: [    2.314285] scsi3 : ahci
kernel: [    2.314366] scsi4 : ahci
kernel: [    2.314430] scsi5 : ahci
kernel: [    2.314870] scsi6 : ahci
kernel: [    2.314931] scsi7 : ahci

kernel: [    2.314496] ata1: SATA max UDMA/133 abar m2048@0xfad25000 port 0xfad25100 irq 68
kernel: [    2.314498] ata2: SATA max UDMA/133 abar m2048@0xfad25000 port 0xfad25180 irq 68
kernel: [    2.314500] ata3: SATA max UDMA/133 abar m2048@0xfad25000 port 0xfad25200 irq 68
kernel: [    2.314503] ata4: SATA max UDMA/133 abar m2048@0xfad25000 port 0xfad25280 irq 68
kernel: [    2.314505] ata5: SATA max UDMA/133 abar m2048@0xfad25000 port 0xfad25300 irq 68
kernel: [    2.314507] ata6: SATA max UDMA/133 abar m2048@0xfad25000 port 0xfad25380 irq 68
kernel: [    2.314956] ata7: SATA max UDMA/133 abar m512@0xfa910000 port 0xfa910100 irq 70
kernel: [    2.314961] ata8: SATA max UDMA/133 abar m512@0xfa910000 port 0xfa910180 irq 70

kernel: [    2.641592] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
kernel: [    2.633683] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
kernel: [    2.633670] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
kernel: [    2.633697] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
kernel: [    2.633653] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
kernel: [    2.633626] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
kernel: [    2.805536] ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
kernel: [    2.805518] ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

kernel: [    2.259337] ahci 0000:00:1f.2: version 3.0
kernel: [    2.259348] ahci 0000:00:1f.2: PCI INT B -> GSI 20 (level, low) -> IRQ 20
kernel: [    2.259447] ahci 0000:00:1f.2: irq 68 for MSI/MSI-X
kernel: [    2.259454] ahci 0000:00:1f.2: controller can't do SNTF, turning off CAP_SNTF
kernel: [    2.273841] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x3f impl RAID mode
kernel: [    2.273843] ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part ems apst
kernel: [    2.273846] ahci 0000:00:1f.2: setting latency timer to 64

kernel: [    2.314525] ahci 0000:0a:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
kernel: [    2.314597] ahci 0000:0a:00.0: irq 70 for MSI/MSI-X
kernel: [    2.314679] ahci 0000:0a:00.0: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
kernel: [    2.314680] ahci 0000:0a:00.0: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs
kernel: [    2.314687] ahci 0000:0a:00.0: setting latency timer to 64


kernel: [    2.661359] scsi 0:0:0:0: Direct-Access     ATA      Corsair Force 3  1.3  PQ: 0 ANSI: 5
kernel: [    2.661464] scsi 1:0:0:0: Direct-Access     ATA      Corsair Force 3  1.3  PQ: 0 ANSI: 5
kernel: [    2.661588] scsi 2:0:0:0: Direct-Access     ATA      ST2000DL003-9VT1 CC32 PQ: 0 ANSI: 5
kernel: [    2.661790] scsi 3:0:0:0: Direct-Access     ATA      ST2000DL003-9VT1 CC32 PQ: 0 ANSI: 5
kernel: [    2.661920] scsi 4:0:0:0: Direct-Access     ATA      ST2000DL003-9VT1 CC32 PQ: 0 ANSI: 5
kernel: [    2.662056] scsi 5:0:0:0: Direct-Access     ATA      ST2000DL003-9VT1 CC32 PQ: 0 ANSI: 5
kernel: [    2.811862] scsi 6:0:0:0: CD-ROM            ATAPI    iHAS624   B      GL27 PQ: 0 ANSI: 5
kernel: [    2.818763] scsi 7:0:0:0: Direct-Access     ATA      SAMSUNG HD154UI  1AG0 PQ: 0 ANSI: 5

kernel: [    2.661963] sd 0:0:0:0: [sda] Attached SCSI disk
kernel: [    2.661446] sd 0:0:0:0: [sda] 468862128 512-byte logical blocks: (240 GB/223 GiB)
kernel: [    2.661477] sd 0:0:0:0: [sda] Write Protect is off
kernel: [    2.661478] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
kernel: [    2.661486] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

kernel: [    2.661930] sd 1:0:0:0: [sdb] Attached SCSI disk
kernel: [    2.661506] sd 1:0:0:0: [sdb] 234441648 512-byte logical blocks: (120 GB/111 GiB)
kernel: [    2.661546] sd 1:0:0:0: [sdb] Write Protect is off
kernel: [    2.661548] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
kernel: [    2.661566] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Last edited by lxtwin; 10-30-2011 at 05:20 PM.
Reply With Quote


Reply

Tags
force 3, linux, lost interrupt, sis, ssd

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 10:17 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.