Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    CAM STATUS: ATA Status Error

    General pfSense Questions
    5
    11
    3.9k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      muneebkalathil
      last edited by

      I am getting CAM STATUS: ATA Status Error 2nd time. I earlier used another Hard disk and got this error and changed to this hard disk. After around 3 months, This Hard disk too got the same error.

      I am using pfSense 2.3.1. I am attaching the screenshots. Someone please help.

      Currently, Network is going well but I cant get to webGUI.

      IMG_20160927_125538.jpg
      IMG_20160927_125538.jpg_thumb
      IMG_20160927_125533.jpg
      IMG_20160927_125533.jpg_thumb

      1 Reply Last reply Reply Quote 0
      • H
        Harvy66
        last edited by

        What kind of harddisks? Regular, SSD, USB flash, flash card, etc?

        1 Reply Last reply Reply Quote 0
        • KOMK
          KOM
          last edited by

          CAM status errors are always hardware.  You have another bad disk.

          1 Reply Last reply Reply Quote 0
          • M
            MoonKnight
            last edited by

            Hi,
            I just start receiving these errors on my pfSense.
            It started yesterday. It's my hard drives failing now?
            I bought the 03.03.2021: 2 x Samsung 870 EVO SSD 500GB

            This is the log after a reboot of my pfSense today.

            Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): Retrying command, 1 more tries remain
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): RES: 41 40 c0 1f f2 00 28 00 00 90 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): CAM status: ATA Status Error
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): READ_FPDMA_QUEUED. ACB: 60 90 88 1f f2 40 28 00 00 00 00 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): Retrying command, 2 more tries remain
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): RES: 41 40 c0 1f f2 00 28 00 00 90 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): CAM status: ATA Status Error
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): READ_FPDMA_QUEUED. ACB: 60 90 88 1f f2 40 28 00 00 00 00 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): Retrying command, 3 more tries remain
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): RES: 41 40 c0 1f f2 00 28 00 00 90 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): CAM status: ATA Status Error
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): READ_FPDMA_QUEUED. ACB: 60 90 88 1f f2 40 28 00 00 00 00 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): Error 5, Retries exhausted
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): RES: 41 40 58 22 1f 00 29 00 00 a8 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): CAM status: ATA Status Error
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): READ_FPDMA_QUEUED. ACB: 60 a8 10 22 1f 40 29 00 00 00 00 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): Retrying command, 0 more tries remain
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): RES: 41 40 58 22 1f 00 29 00 00 a8 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): CAM status: ATA Status Error
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): READ_FPDMA_QUEUED. ACB: 60 a8 10 22 1f 40 29 00 00 00 00 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): Retrying command, 1 more tries remain
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): RES: 41 40 58 22 1f 00 29 00 00 a8 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): CAM status: ATA Status Error
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): READ_FPDMA_QUEUED. ACB: 60 a8 10 22 1f 40 29 00 00 00 00 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): Retrying command, 2 more tries remain
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): RES: 41 40 58 22 1f 00 29 00 00 a8 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): CAM status: ATA Status Error
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): READ_FPDMA_QUEUED. ACB: 60 a8 10 22 1f 40 29 00 00 00 00 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): Retrying command, 3 more tries remain
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): RES: 41 40 58 22 1f 00 29 00 00 a8 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): CAM status: ATA Status Error
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): READ_FPDMA_QUEUED. ACB: 60 a8 10 22 1f 40 29 00 00 00 00 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): Error 5, Retries exhausted
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): RES: 41 40 80 21 1f 00 29 00 00 a8 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): CAM status: ATA Status Error
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): READ_FPDMA_QUEUED. ACB: 60 a8 68 21 1f 40 29 00 00 00 00 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): Retrying command, 0 more tries remain
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): RES: 41 40 80 21 1f 00 29 00 00 a8 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): CAM status: ATA Status Error
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): READ_FPDMA_QUEUED. ACB: 60 a8 68 21 1f 40 29 00 00 00 00 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): Retrying command, 1 more tries remain
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): RES: 41 40 80 21 1f 00 29 00 00 a8 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): CAM status: ATA Status Error
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): READ_FPDMA_QUEUED. ACB: 60 a8 68 21 1f 40 29 00 00 00 00 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): Retrying command, 2 more tries remain
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): RES: 41 40 80 21 1f 00 29 00 00 a8 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): CAM status: ATA Status Error
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): READ_FPDMA_QUEUED. ACB: 60 a8 68 21 1f 40 29 00 00 00 00 00
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): Retrying command, 3 more tries remain
Jan 2 13:25:13	kernel		(ada1:ahcich3:0:0:0): RES: 41 40 80 21 1f 00 29 00 00 a8 00
Jan 2 13:25:08	kernel		(ada1:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
Jan 2 13:25:08	kernel		(ada1:ahcich3:0:0:0): CAM status: ATA Status Error
Jan 2 13:25:08	kernel		(ada1:ahcich3:0:0:0): READ_FPDMA_QUEUED. ACB: 60 a8 68 21 1f 40 29 00 00 00 00 00
Jan 2 13:25:08	kernel		done.
Jan 2 13:25:08	check_reload_status	412	Updating all dyndns
Jan 2 13:25:08	kernel		done.
Jan 2 13:25:08	php	434	rc.bootup: NTPD is starting up.
Jan 2 13:25:08	kernel		done.
Jan 2 13:25:07	kernel		done.
Jan 2 13:25:07	kernel		.Starting DNS Resolver...done.
Jan 2 13:25:07	php	434	rc.bootup: sync unbound done.
Jan 2 13:25:06	kernel		done.

            d444d823-2ccb-44a2-9ea0-6fa27e723a02-image.png

            ada0:
            4e124fe4-9b60-43b4-8a02-e24f93599aa4-image.png

            ada1:
            895cd9d5-d51f-4bbf-a49e-52188c5258d0-image.png

            --- 24.11 ---
            Intel(R) Xeon(R) CPU D-1518 @ 2.20GHz
            Kingston DDR4 2666MHz 16GB ECC
            2 x HyperX Fury SSD 120GB (ZFS-mirror)
            2 x Intel i210 (ports)
            4 x Intel i350 (ports)

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              Those are all on ada1 and the SMART data shows a bunch of hardware errors on that drive. It doesn't look good. Surprising from a drive like that though. It could also be trying to reading something the drive doesn't support but it implies only one did, same firmware?

              M 1 Reply Last reply Reply Quote 0
              • M
                MoonKnight @stephenw10
                last edited by

                @stephenw10
                Hi, yeah look like the problem is on disk ada1.
                Glad I use zfs (mirroring). Hard to tell if booth disks have the same firmware, since I bought them on the same day and just install them into my pfSense box.
                So I don't really don't know what to do, go and buy the same harddrive and swap it with the bad one, and hopefully, my pfSense will boot normally without any problems. Or just swap booth disk with two older Samsung disks and do a clean install and restore backup config.

                --- 24.11 ---
                Intel(R) Xeon(R) CPU D-1518 @ 2.20GHz
                Kingston DDR4 2666MHz 16GB ECC
                2 x HyperX Fury SSD 120GB (ZFS-mirror)
                2 x Intel i210 (ports)
                4 x Intel i350 (ports)

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  Well 500G is huge for pfSense so swapping in some older, smaller drives is what I'd do if you have them.

                  M 1 Reply Last reply Reply Quote 0
                  • M
                    MoonKnight @stephenw10
                    last edited by

                    @stephenw10

                    Yeah, I found 2 x Kingston HyperX Fury 120GB. Maybe swapping them. But maybe wait to pfSense 2.6.0 is released 🙂

                    --- 24.11 ---
                    Intel(R) Xeon(R) CPU D-1518 @ 2.20GHz
                    Kingston DDR4 2666MHz 16GB ECC
                    2 x HyperX Fury SSD 120GB (ZFS-mirror)
                    2 x Intel i210 (ports)
                    4 x Intel i350 (ports)

                    1 Reply Last reply Reply Quote 0
                    • stephenw10S
                      stephenw10 Netgate Administrator
                      last edited by

                      Yes, you could wait. Though the update from 2.5.2 to 2.6 should be pretty smooth, I've updated numerous boxes many times during testing.

                      Steve

                      M 1 Reply Last reply Reply Quote 1
                      • M
                        MoonKnight @stephenw10
                        last edited by

                        @stephenw10

                        Thanks, do you think it is safe to move to pfsense 2.6.0 Beta now for my home? 🙂

                        --- 24.11 ---
                        Intel(R) Xeon(R) CPU D-1518 @ 2.20GHz
                        Kingston DDR4 2666MHz 16GB ECC
                        2 x HyperX Fury SSD 120GB (ZFS-mirror)
                        2 x Intel i210 (ports)
                        4 x Intel i350 (ports)

                        1 Reply Last reply Reply Quote 0
                        • stephenw10S
                          stephenw10 Netgate Administrator
                          last edited by

                          Well it depends who's using it. If your users are accessing Facebook and demand 99.999% uptime then maybe hold off/ 😉
                          But I have been using it home as my edge device (22.01 at least) for months now without any real problems. Reinstalling and recovering is relatively trivial for me though.

                          Steve

                          1 Reply Last reply Reply Quote 1
                          • First post
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.