You are not logged in.
So I have an old HP Pavilion that was running XP on an IDE drive. I bought an SSD with the thought that I'd move the XP image over to the SSD and then play with a multiboot setup.
I ended up with a SI3114 4-port sata controller, which finally recognized the SSD at POST time, and eventually got the XP image cloned over to the SSD.
Figured I was good to go.
Booted the current 32-bit PAE image and while it can find the controller, it doesn't seem to be able to startup/connect to the SSD. Obviously, I know the controller/disk pair are working because it boots XP in 2 secs. :-) I hot plugged an old 2.5" Fujitsu HD to the controller and the system recognized it.. I hot plugged the SSD and the controller attempts to connect to the disk, but that fails and it doesn't see it. I have to believe that there may be something fixable in this controller to start an SSD.
Thoughts?
Here's the snippet from the install dmesg where I connected the Fujitsu and re-hotplugged the SSD again.
[55505.785404] ata8: exception Emask 0x10 SAct 0x0 SErr 0x50000 action 0xe frozen
[55505.785410] ata8: SError: { PHYRdyChg CommWake }
[55505.785424] ata8: hard resetting link
[55506.496086] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[55506.498566] ata8.00: ATA-8: FUJITSU MHW2080BJ G2, 0000001A, max UDMA/100
[55506.498569] ata8.00: 156301488 sectors, multi 16: LBA48 NCQ (depth 0/32)
[55506.503218] ata8.00: configured for UDMA/100
[55506.503228] ata8: EH complete
[55506.503584] scsi 7:0:0:0: Direct-Access ATA FUJITSU MHW2080B 001A PQ: 0 ANSI: 5
[55506.507592] sd 7:0:0:0: [sdf] 156301488 512-byte logical blocks: (80.0 GB/74.5 GiB)
[55506.507674] sd 7:0:0:0: [sdf] Write Protect is off
[55506.507678] sd 7:0:0:0: [sdf] Mode Sense: 00 3a 00 00
[55506.507712] sd 7:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[55506.543944] sdf:
[55506.544620] sd 7:0:0:0: [sdf] Attached SCSI disk
[55546.513039] ata6: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0xe frozen
[55546.513045] ata6: SError: { PHYRdyChg }
[55546.513059] ata6: hard resetting link
[55547.224049] ata6: SATA link down (SStatus 0 SControl 310)
[55547.224070] ata6: EH complete
[55550.722096] ata6: exception Emask 0x10 SAct 0x0 SErr 0x50000 action 0xe frozen
[55550.722102] ata6: SError: { PHYRdyChg CommWake }
[55550.722116] ata6: hard resetting link
[55551.432045] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[55556.576040] ata6.00: qc timeout (cmd 0xec)
[55556.576048] ata6.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[55556.576060] ata6: hard resetting link
[55556.890609] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[55567.072072] ata6.00: qc timeout (cmd 0xec)
[55567.072080] ata6.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[55567.072093] ata6: hard resetting link
[55567.386686] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[55598.048066] ata6.00: qc timeout (cmd 0xec)
[55598.048074] ata6.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[55598.048086] ata6: hard resetting link
[55598.362666] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[55598.362680] ata6: EH complete
--- Mod edit: added code tags ---
Last edited by damo (2019-04-13 13:51:53)
Offline
So it appears that the particular brand of SSD I'm using, is a little dubious on the SATA protocol. While interesting that the old Windows XP drivers has no problem activating it as a boot device, I guess the sata_sil driver doesn't have those tricks up its sleeve.
A teamgroup SSD hot plugged was recognized immediately.
Offline