Strange ATA status error (SETFEATURES. ACB ? )
Alixy last edited by
Quick recap: this is on an alix2d13 with 256mb of ram, a new SanDisk CF 8gb card, and no other added peripherals (no minipci, no usb, no ide) that is crashing constantly (roughly 30-75min between crashes). The CF card was bought a few days ago, but the alix2d13 and power supply were bought in the beginning of 2014, but I haven't had time to try setting it up until now.
I thought the ATA controller just managed the IDE port, but looking at the boot messages, it appears that the CF card is also attached to ata0:
2015/08/13 17:31:48 PDT : ada0 at ata0 bus 0 scbus0 target 0 lun 0 2015/08/13 17:31:48 PDT : ada0: <sandisk sdcfhsnjc-008g="" hdx="" 7.08="">CFA-0 device 2015/08/13 17:31:48 PDT : ada0: Serial Number BKZ062415183916 2015/08/13 17:31:48 PDT : ada0: 100.000MB/s transfers (UDMA5, PIO 512bytes) 2015/08/13 17:31:48 PDT : ada0: 7629MB (15625216 512 byte sectors: 16H 63S/T 15501C) 2015/08/13 17:31:48 PDT : ada0: Previously was known as ad0</sandisk>
Later on in the serial console output (still while booting, just before the pfsense console menu), this error pops up:
2015/08/13 17:31:51 PDT : (pass0:ata0:0:0:0): SETFEATURES. ACB: ef 85 00 00 00 40 00 00 00 00 00 00 2015/08/13 17:31:51 PDT : (pass0:ata0:0:0:0): CAM status: ATA Status Error 2015/08/13 17:31:51 PDT : (pass0:ata0:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT ) 2015/08/13 17:31:51 PDT : (pass0:ata0:0:0:0): RES: 51 04 00 00 00 00 00 00 00 00 00
Anyone know what that's about?
PS, if it helps, here is a pastebin of the serial console output from a full boot->crash cycle: http://pastebin.com/Y0KHza54
(I removed the ipv6 ip listed in the pfsense menu, but let me know if there is anything else I should have redacted).
All the lines are preceded by a timestamp by a script I wrote that is logging the serial console and creating a new log each time it sees the "PC Engines ALIX.2 v0.99m" boot banner.
Alixy last edited by
Googled and found this freebsd thread: https://forums.freebsd.org/threads/camcontrol-error-sending-command.35548/
It turns out to just be an error from attempting to disable APM on the card (which is denoted by the first line before and after the error).
My first thought was that the card didn't support APM, but I ssh'd in and used camcontrol identify on ada0 and the card does indeed support APM:
[2.2.4-RELEASE][firstname.lastname@example.org]/root: camcontrol identify ada0 pass0: <sandisk sdcfhsnjc-008g="" hdx="" 7.08="">CFA-0 device pass0: 100.000MB/s transfers (UDMA5, PIO 512bytes) protocol ATA/ATAPI-0 device model SanDisk SDCFHSNJC-008G firmware revision HDX 7.08 serial number BKZ062415183916 cylinders 15501 heads 16 sectors/track 63 sector size logical 512, physical 512, offset 0 CFA supported LBA supported 15625216 sectors LBA48 supported 15625216 sectors PIO supported PIO4 w/o IORDY DMA supported WDMA2 UDMA5 Feature Support Enabled Value Vendor read ahead no no write cache yes yes flush cache yes no overlap no Tagged Command Queuing (TCQ) no no Native Command Queuing (NCQ) no NCQ Queue Management no NCQ Streaming no Receive & Send FPDMA Queued no SMART no no microcode download no no security no no power management no no advanced power management yes no 0/0x00 automatic acoustic management no no media status notification no no power-up in Standby no no write-read-verify no no unload no no general purpose logging yes no free-fall no no Data Set Management (DSM/TRIM) yes DSM - max 512byte blocks yes 1 DSM - deterministic read yes zeroed Host Protected Area (HPA) no [2.2.4-RELEASE][email@example.com]/root:</sandisk>
Perhaps because APM is already disabled?
In any case, it's a red herring and not related to my hourly crashes at all.