Netgate 3100 - Kernel Error in Logs
-
Hello,
From time to time I can see an error in the logs:
Oct 7 19:25:39 kernel ahcich0: stopping AHCI engine failed Oct 7 19:25:39 kernel (ada0:ahcich0:0:0:0): Retrying command, 3 more tries remain Oct 7 19:25:39 kernel (ada0:ahcich0:0:0:0): CAM status: Command timeout Oct 7 19:25:39 kernel (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 40 00 c3 2c 40 00 00 00 00 00 00 Oct 7 19:25:39 kernel ahcich0: is 00000000 cs 001ffe00 ss 001ffff8 rs 001ffff8 tfd 40 serr 00000000 cmd 00718317 Oct 7 19:25:39 kernel ahcich0: Timeout on slot 3 port 0Why is there that error and is it a problem?
Can there be a problem with my 3100 Unit?
It is upgraded with a SSD. -
Yes, it could be a bad SSD. It could also be a timing at boot or something like a power saving setting.
Does it appear repeatedly?Steve
-
@stephenw10 Only once every couple of days
-
Just a random in the system log? Or at boot in the same place?
I assume it has just started doing that? Or at least it didn't do it initially?
Steve
-
@stephenw10 Random in system log. not at boot yet.
I filtered it in the system logs.
It started after switch to the SSD.
Should the SSD be replaced?Sep 13 13:06:06 snmpd 41129 disk_OS_get_disks: adding device 'ada0' to device list Sep 18 12:12:01 kernel ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 Sep 18 12:12:01 kernel ada0: <TS128GMTS830S R0427GN1> ACS-3 ATA SATA 3.x device Sep 18 12:12:01 kernel ada0: Serial Number G540610146 Sep 18 12:12:01 kernel ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) Sep 18 12:12:01 kernel ada0: Command Queueing enabled Sep 18 12:12:01 kernel ada0: 122104MB (250069680 512 byte sectors) Sep 18 12:12:26 snmpd 44432 disk_OS_get_disks: adding device 'ada0' to device list Sep 18 12:16:08 snmpd 12260 disk_OS_get_disks: adding device 'ada0' to device list Sep 22 13:36:31 kernel (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 40 c0 c2 2c 40 00 00 00 00 00 00 Sep 22 13:36:31 kernel (ada0:ahcich0:0:0:0): CAM status: Command timeout Sep 22 13:36:31 kernel (ada0:ahcich0:0:0:0): Retrying command, 3 more tries remain Sep 24 06:01:01 kernel (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 40 c0 c2 2c 40 00 00 00 00 00 00 Sep 24 06:01:02 kernel (ada0:ahcich0:0:0:0): CAM status: Command timeout Sep 24 06:01:02 kernel (ada0:ahcich0:0:0:0): Retrying command, 3 more tries remain Sep 27 17:07:52 kernel (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 40 80 fa 16 40 00 00 00 00 00 00 Sep 27 17:07:52 kernel (ada0:ahcich0:0:0:0): CAM status: Command timeout Sep 27 17:07:52 kernel (ada0:ahcich0:0:0:0): Retrying command, 3 more tries remain Sep 28 16:41:02 snmpd 66634 disk_OS_get_disks: adding device 'ada0' to device list Oct 7 08:09:55 kernel (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 40 80 c3 2d 40 00 00 00 00 00 00 Oct 7 08:09:55 kernel (ada0:ahcich0:0:0:0): CAM status: Command timeout Oct 7 08:09:55 kernel (ada0:ahcich0:0:0:0): Retrying command, 3 more tries remain Oct 7 19:25:39 kernel (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 40 00 c3 2c 40 00 00 00 00 00 00 Oct 7 19:25:39 kernel (ada0:ahcich0:0:0:0): CAM status: Command timeout Oct 7 19:25:39 kernel (ada0:ahcich0:0:0:0): Retrying command, 3 more tries remain -
Yes, I would replace that. It's possible the controller just doesn't like that SSD but either way those errors are bad.
-
@stephenw10 Thank you. removed the ssd and went back to the eMMC. Unfortunately I had to reinstall it as boot did not boot from eMMC anymore.
-
For future reference, when you reinstall it sets the boot env to the chosen install media. It is possible to set that manually from the uboot prompt though. For example:
setenv bootcmd 'run setLED; run emmcboot;' saveenv resetYou would only ever need to do that if for some reason you need to change boot media without reinstalling.
Steve
