ewhac
Contributor
- Joined
- Aug 20, 2013
- Messages
- 177
I have an adorable little HP N54L microserver with 8GiB of RAM on which I originally installed FreeNAS 8.3.1. The machine comes with a 250GB HP drive (rebranded Seacrate), and I added three 2TB Hitachi 5K3000-series drives in a RAID-Z1 configuration.
After upgrading from 8.3.1 to 9.1.0 via the GUI upgrade image, a new message is appearing in the boot logs that I've never seen before:
(aprobe0:ahcich0:0:0:0): SETFEATURES ENABLE SATA FEATURE. ACB: ef 10 00 00 00 40 00 00 00 00 02 00
(aprobe0:ahcich0:0:0:0): CAM status: ATA Status Error
(aprobe0:ahcich0:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
(aprobe0:ahcich0:0:0:0): RES: 51 04 00 00 00 40 00 00 00 02 00
(aprobe0:ahcich0:0:0:0): Retrying command
(aprobe0:ahcich0:0:0:0): SETFEATURES ENABLE SATA FEATURE. ACB: ef 10 00 00 00 40 00 00 00 00 02 00
(aprobe0:ahcich0:0:0:0): CAM status: ATA Status Error
(aprobe0:ahcich0:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
(aprobe0:ahcich0:0:0:0): RES: 51 04 00 00 00 40 00 00 00 02 00
(aprobe0:ahcich0:0:0:0): Error 5, Retries exhausted
...And then later (curious part bolded)...
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <VB0250EAVER HPG7> ATA-8 SATA 2.x device
ada0: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 238475MB (488397168 512 byte sectors: 16H 63S/T 16383C)
ada0: Previously was known as ad4
ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
da0 at umass-sim0 bus 0 scbus6 target 0 lun 0
da0: <SanDisk Cruzer Fit 1.26> Removable Direct Access SCSI-5 device
da0: 40.000MB/s transfers
da0: 3819MB (7821312 512 byte sectors: 255H 63S/T 486C)
da0: quirks=0x2<NO_6_BYTE>
ada1: <Hitachi HDS5C3020ALA632 ML6OAA10> ATA-8 SATA 3.x device
ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada1: Previously was known as ad6
ada2 at ahcich2 bus 0 scbus2 target 0 lun 0
ada2: <Hitachi HDS5C3020ALA632 ML6OAA10> ATA-8 SATA 3.x device
ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada2: Command Queueing enabled
ada2: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada2: Previously was known as ad8
ada3 at ahcich3 bus 0 scbus3 target 0 lun 0
ada3: <Hitachi HDS5C3020ALA632 ML6OAA10> ATA-8 SATA 3.x device
ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada3: Command Queueing enabled
ada3: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada3: Previously was known as ad10
These messages only appear once at boot, and then everything comes up as before.
Googling for the SETFEATURES message in particular suggests that this is a dire problem. However, to all outward appearances, the machine is operating fine, and no data is lost.
Googling for the "Previously was known as" messages suggests these only appear if you move the drives around behind ZFS's back. However, the hardware was not touched before, during, or after the upgrade to 9.1.0.
The drive throwing the SATA error appears to be the 250GB Seacrate that came with the machine. However, this drive has been acting suspiciously since day one (SMART reports an excessive number of corrected read errors), and it has never earned my trust. As such, it's being treated as a junk drive -- it's currently formatted ZFS, is in a pool all by itself, and contains no important data.
So: What's going on? Is there anything I need to worry about?
After upgrading from 8.3.1 to 9.1.0 via the GUI upgrade image, a new message is appearing in the boot logs that I've never seen before:
(aprobe0:ahcich0:0:0:0): SETFEATURES ENABLE SATA FEATURE. ACB: ef 10 00 00 00 40 00 00 00 00 02 00
(aprobe0:ahcich0:0:0:0): CAM status: ATA Status Error
(aprobe0:ahcich0:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
(aprobe0:ahcich0:0:0:0): RES: 51 04 00 00 00 40 00 00 00 02 00
(aprobe0:ahcich0:0:0:0): Retrying command
(aprobe0:ahcich0:0:0:0): SETFEATURES ENABLE SATA FEATURE. ACB: ef 10 00 00 00 40 00 00 00 00 02 00
(aprobe0:ahcich0:0:0:0): CAM status: ATA Status Error
(aprobe0:ahcich0:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
(aprobe0:ahcich0:0:0:0): RES: 51 04 00 00 00 40 00 00 00 02 00
(aprobe0:ahcich0:0:0:0): Error 5, Retries exhausted
...And then later (curious part bolded)...
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <VB0250EAVER HPG7> ATA-8 SATA 2.x device
ada0: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 238475MB (488397168 512 byte sectors: 16H 63S/T 16383C)
ada0: Previously was known as ad4
ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
da0 at umass-sim0 bus 0 scbus6 target 0 lun 0
da0: <SanDisk Cruzer Fit 1.26> Removable Direct Access SCSI-5 device
da0: 40.000MB/s transfers
da0: 3819MB (7821312 512 byte sectors: 255H 63S/T 486C)
da0: quirks=0x2<NO_6_BYTE>
ada1: <Hitachi HDS5C3020ALA632 ML6OAA10> ATA-8 SATA 3.x device
ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada1: Previously was known as ad6
ada2 at ahcich2 bus 0 scbus2 target 0 lun 0
ada2: <Hitachi HDS5C3020ALA632 ML6OAA10> ATA-8 SATA 3.x device
ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada2: Command Queueing enabled
ada2: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada2: Previously was known as ad8
ada3 at ahcich3 bus 0 scbus3 target 0 lun 0
ada3: <Hitachi HDS5C3020ALA632 ML6OAA10> ATA-8 SATA 3.x device
ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada3: Command Queueing enabled
ada3: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada3: Previously was known as ad10
These messages only appear once at boot, and then everything comes up as before.
Googling for the SETFEATURES message in particular suggests that this is a dire problem. However, to all outward appearances, the machine is operating fine, and no data is lost.
Googling for the "Previously was known as" messages suggests these only appear if you move the drives around behind ZFS's back. However, the hardware was not touched before, during, or after the upgrade to 9.1.0.
The drive throwing the SATA error appears to be the 250GB Seacrate that came with the machine. However, this drive has been acting suspiciously since day one (SMART reports an excessive number of corrected read errors), and it has never earned my trust. As such, it's being treated as a junk drive -- it's currently formatted ZFS, is in a pool all by itself, and contains no important data.
So: What's going on? Is there anything I need to worry about?