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

    Kernel TIMEOUT

    Scheduled Pinned Locked Moved 1.2.3-PRERELEASE-TESTING snapshots - RETIRED
    7 Posts 6 Posters 3.5k Views
    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.
    • T
      ToxIcon
      last edited by

      pfsense at another location was update to 1.2.3-RC2
      built on Sat Jul 18 19:19:52 EDT 2009 FreeBSD 7.2-RELEASE-p2 i386 and now they are seeing this error
      in the system logs

      Jul 21 17:40:05 dnsmasq[719]: reading /var/dhcpd/var/db/dhcpd.leases
      Jul 21 17:25:06 kernel: g_vfs_done():ad0s1a[WRITE(offset=36804395008, length=16384)]error = 5
      Jul 21 17:25:06 kernel: g_vfs_done():ad0s1a[WRITE(offset=35070132224, length=16384)]error = 5
      Jul 21 17:25:06 kernel: ad0: error issuing WRITE_DMA command
      Jul 21 17:25:06 kernel: ad0: timeout waiting to issue command
      Jul 21 17:25:05 kernel: ad0: error issuing WRITE_DMA command
      Jul 21 17:25:05 kernel: ad0: timeout waiting to issue command

      Jul 21 18:11:55 dnsmasq[719]: reading /var/dhcpd/var/db/dhcpd.leases
      Jul 21 18:01:09 kernel: ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=68508367
      Jul 21 17:42:25 dnsmasq[719]: reading /var/dhcpd/var/db/dhcpd.leases
      Jul 21 17:40:05 dnsmasq[719]: reading /var/dhcpd/var/db/dhcpd.leases
      Jul 21 17:25:06 kernel: g_vfs_done():ad0s1a[WRITE(offset=36804395008, length=16384)]error = 5
      Jul 21 17:25:06 kernel: g_vfs_done():ad0s1a[WRITE(offset=35070132224, length=16384)]error = 5
      Jul 21 17:25:06 kernel: ad0: error issuing WRITE_DMA command
      Jul 21 17:25:06 kernel: ad0: timeout waiting to issue command
      Jul 21 17:25:05 kernel: ad0: error issuing WRITE_DMA command
      Jul 21 17:25:05 kernel: ad0: timeout waiting to issue command

      Jul 21 18:01:09 kernel: ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=68508367
      Jul 21 17:42:25 dnsmasq[719]: reading /var/dhcpd/var/db/dhcpd.leases
      Jul 21 17:40:05 dnsmasq[719]: reading /var/dhcpd/var/db/dhcpd.leases
      Jul 21 17:25:06 kernel: g_vfs_done():ad0s1a[WRITE(offset=36804395008, length=16384)]error = 5
      Jul 21 17:25:06 kernel: g_vfs_done():ad0s1a[WRITE(offset=35070132224, length=16384)]error = 5
      Jul 21 17:25:06 kernel: ad0: error issuing WRITE_DMA command
      Jul 21 17:25:06 kernel: ad0: timeout waiting to issue command
      Jul 21 17:25:05 kernel: ad0: error issuing WRITE_DMA command
      Jul 21 17:25:05 kernel: ad0: timeout waiting to issue command

      1 Reply Last reply Reply Quote 0
      • dotdashD
        dotdash
        last edited by

        I'd be very surprised if an update really made your hard drive fail. What's the hardware?

        1 Reply Last reply Reply Quote 0
        • T
          ToxIcon
          last edited by

          sorry its a 250 ide by WD

          and a 80 gig wd

          1 Reply Last reply Reply Quote 0
          • ?
            Guest
            last edited by

            This is your hard drive starting to get flaky.  As was pointed out, this is coincidental to your upgrade.

            1 Reply Last reply Reply Quote 0
            • B
              Briantist
              last edited by

              @submicron:

              This is your hard drive starting to get flaky.  As was pointed out, this is coincidental to your upgrade.

              It may be you're only noticing it because of the upgrade. I upgraded my setup at home to 1.2.3-RC1 and when it didn't come back up that's what led me to find out that my hard drive had failed. If I had rebooted for another reason, I probably would have found out just the same.

              1 Reply Last reply Reply Quote 0
              • T
                tommyboy180
                last edited by

                There is a tool in the Hiren's BootCD that will attempt to fix your dying HDDs.

                -Tom Schaefer
                SuperMicro 1U 2X Intel pro/1000 Dual Core Intel 2.2 Ghz - 2 Gig RAM

                Please support pfBlocker | File Browser | Strikeback

                1 Reply Last reply Reply Quote 0
                • J
                  jits
                  last edited by

                  Speaking from experience, you might want to use seagate or samsung drives instead of WD.

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