Trouble with SSD on SATA

[Peter Maloney]

Willem,

I can only guess, but...

Is AHCI enabled in the bios? If you are not using 'fake-raid' for any
disks, you should [depending on FreeBSD version, HBA, etc.] probably
enable AHCI. Some servers actually come with SATA set in IDE mode. And
if you are using zfs, the controller optimally should not be RAID at
all. And if you have AHCI enabled already, try disabling it (losing hot
swapping ability, and some performance).

What version of FreeBSD are you using? I had a terrible experience with
ZFS on FreeBSD 8.2 release, and 8.2-stable-April2011. I would recommend
upgrading to the latest 8-stable with cvsup.

This thread seems related:
http://forums.freebsd.org/showthread.php?t=24189

The guy was using 8.2 release, and he downgraded to an old version of
the driver to fix, saying that a patch also existed in 8-stable that
fixes the problem.

Are you using an expander?

What HBA / hard disk controller are you using?


Peter

Am 16.11.2011 17:12, schrieb Willem Jan Withagen:
> Hi,
>
> I'm getting these:
>
> Nov 16 16:40:49 zfs kernel: ata6: port is not ready (timeout 15000ms)
> tfd = 00000080
> Nov 16 16:40:49 zfs kernel: ata6: hardware reset timeout
> Nov 16 16:41:50 zfs kernel: ata6: port is not ready (timeout 15000ms)
> tfd = 00000080
> Nov 16 16:41:50 zfs kernel: ata6: hardware reset timeout
>
> When inserting the tray with a SSD disk connected to that controller.
>
> Which is probably due to a BIOS upgrade....
> At least it started after upgrading the BIOS. So I'm asking SuperMicro
> for an older version.
>
> When this happens, the system sometimes panics, haven't written the
> details yet down right now. somewhere in get_devices...
>
> After the panic I really need to powerdown the machine, otherwise it
> boots but stalls at finding any disks. It does not just find no disks,
> it "freezes" at the point it should report the found disks in the
> bios-boot.
> So apparently the ata controller are left in a very confused state.
>
> Why is the controller found at boot, and works as it should.
> And why later it just starts generating these hardware resets??
>
> --WjW
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"