@justsumdood:
that was the exact same way I did it - up until NOW
with kernel 3.3 rc3 & rc4 (afaik it worked with 3.2)
I only get the following:
that means when after that I plug in another harddrive and power it up - it won't be recognized
the controller is the (in)famous Jmicron 36x (dunno 368 or 363, something)
the same happens when stopping via sdparm and remounting read-only (sdparm -C stop -r /dev/foo )
any idea how to get it recognize the new disk ?
that was the exact same way I did it - up until NOW
with kernel 3.3 rc3 & rc4 (afaik it worked with 3.2)
I only get the following:
[ 2093.960134] ata8: exception Emask 0x10 SAct 0x0 SErr 0x990000 action 0xe frozen
[ 2093.960139] ata8: irq_stat 0x00400000, PHY RDY changed
[ 2093.960144] ata8: SError: { PHYRdyChg 10B8B Dispar LinkSeq }
[ 2093.960151] ata8: hard resetting link
[ 2094.681797] ata8: SATA link down (SStatus 0 SControl 300)
[ 2099.673242] ata8: hard resetting link
[ 2099.977646] ata8: SATA link down (SStatus 0 SControl 300)
[ 2099.977660] ata8: limiting SATA link speed to 1.5 Gbps
[ 2104.969034] ata8: hard resetting link
[ 2105.273515] ata8: SATA link down (SStatus 0 SControl 310)
[ 2105.273528] ata8.00: disabled
[ 2105.273544] ata8: EH complete
[ 2105.273553] ata8.00: detaching (SCSI 7:0:0:0)
[ 2105.274064] sd 7:0:0:0: [sde] Synchronizing SCSI cache
[ 2105.274094] sd 7:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 2105.274100] sd 7:0:0:0: [sde] Stopping disk
[ 2105.274108] sd 7:0:0:0: [sde] START_STOP FAILED
[ 2105.274111] sd 7:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 2093.960139] ata8: irq_stat 0x00400000, PHY RDY changed
[ 2093.960144] ata8: SError: { PHYRdyChg 10B8B Dispar LinkSeq }
[ 2093.960151] ata8: hard resetting link
[ 2094.681797] ata8: SATA link down (SStatus 0 SControl 300)
[ 2099.673242] ata8: hard resetting link
[ 2099.977646] ata8: SATA link down (SStatus 0 SControl 300)
[ 2099.977660] ata8: limiting SATA link speed to 1.5 Gbps
[ 2104.969034] ata8: hard resetting link
[ 2105.273515] ata8: SATA link down (SStatus 0 SControl 310)
[ 2105.273528] ata8.00: disabled
[ 2105.273544] ata8: EH complete
[ 2105.273553] ata8.00: detaching (SCSI 7:0:0:0)
[ 2105.274064] sd 7:0:0:0: [sde] Synchronizing SCSI cache
[ 2105.274094] sd 7:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 2105.274100] sd 7:0:0:0: [sde] Stopping disk
[ 2105.274108] sd 7:0:0:0: [sde] START_STOP FAILED
[ 2105.274111] sd 7:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
that means when after that I plug in another harddrive and power it up - it won't be recognized
the controller is the (in)famous Jmicron 36x (dunno 368 or 363, something)
the same happens when stopping via sdparm and remounting read-only (sdparm -C stop -r /dev/foo )
any idea how to get it recognize the new disk ?
Comment