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

Compact Flash doesn't boot

Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
16 Posts 3 Posters 5.9k 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.
  • S
    schnauber
    last edited by May 31, 2011, 7:33 PM

    Hi Guys,

    I've deleted the image with Gparted and download the pfHacom 1G image because VGA support. The image was written with physdiskwrite without any errors. After select LBA for the 4GB Scandisk everything works fine. The nanoBSD booted correctly also the Web Interface seems to work without any problem but on the "shell" on the monitor screen I see some reading errors something with ad0: reading error 51. This issue appears everytime when I do some changes on the web interface and save them. Any ideas?

    1 Reply Last reply Reply Quote 0
    • S
      stephenw10 Netgate Administrator
      last edited by May 31, 2011, 7:52 PM

      That's not good. However I guess I might be caused by inconsistent dma settings. Are you seeing?:

      ad0: FAILURE - READ_DMA status=51 <ready,dsc,error>error=40<uncorrectable></uncorrectable></ready,dsc,error>
      

      Did you actually disable udma in the bios? If you look in /boot/loader.conf do you have these lines?

      
      hw.ata.atapi_dma="0"
      hw.ata.ata_dma="0"
      hw.ata.wc="0"
      

      Steve

      1 Reply Last reply Reply Quote 0
      • S
        schnauber
        last edited by Jun 1, 2011, 5:53 AM

        @stephenw10:

        That's not good. However I guess I might be caused by inconsistent dma settings. Are you seeing?:

        ad0: FAILURE - READ_DMA status=51 <ready,dsc,error>error=40<uncorrectable></uncorrectable></ready,dsc,error>
        

        Did you actually disable udma in the bios? If you look in /boot/loader.conf do you have these lines?

        
        hw.ata.atapi_dma="0"
        hw.ata.ata_dma="0"
        hw.ata.wc="0"
        

        Steve

        In the BIOS I didn't find any flag with udma setting but I'll google for that tonight. Are that reading errors such a big problem? Everything on the web interface seems to work correct and also saved correct when I do any changes.

        1 Reply Last reply Reply Quote 0
        • S
          stephenw10 Netgate Administrator
          last edited by Jun 1, 2011, 9:54 AM

          If this was a normal HD it would probably imply a UD failure. But it isn't.

          @Hacom:

          We remount the root filesystem as read-only, sync, noatime. The default pfSense nanobsd mounts the filesystems as write-able, sync, noatime.
          This changes the "normal" behavior pf pfSense. Any write (update) operations require the root filesystem to be remounted as write-able by the shell command: "mount -u -ow /". After the changes, just reboot the system or execute the command: "sh /usr/local/etc/rc.d/hacom.sh" to mount the root filesystem back as read-only.
          This is a precaution since during early testing of pfSense 2.0: both BETA5 and RC1, we have experienced major flash corruptions.

          Do the changes you have made survive a reboot?

          Steve

          1 Reply Last reply Reply Quote 0
          • S
            schnauber
            last edited by Jun 1, 2011, 12:42 PM

            @stephenw10:

            If this was a normal HD it would probably imply a UD failure. But it isn't.

            @Hacom:

            We remount the root filesystem as read-only, sync, noatime. The default pfSense nanobsd mounts the filesystems as write-able, sync, noatime.
            This changes the "normal" behavior pf pfSense. Any write (update) operations require the root filesystem to be remounted as write-able by the shell command: "mount -u -ow /". After the changes, just reboot the system or execute the command: "sh /usr/local/etc/rc.d/hacom.sh" to mount the root filesystem back as read-only.
            This is a precaution since during early testing of pfSense 2.0: both BETA5 and RC1, we have experienced major flash corruptions.

            Do the changes you have made survive a reboot?

            Steve

            Yes, the changes survive a reboot.

            1 Reply Last reply Reply Quote 0
            • S
              schnauber
              last edited by Jun 2, 2011, 2:20 PM

              I've deactivated the UDMA settings on my BIOS but the error message is still there if I do any changes on the webinterface:
              ad0: failure - read status=51 error=10(nid_not_found)

              1 Reply Last reply Reply Quote 0
              • S
                stephenw10 Netgate Administrator
                last edited by Jun 2, 2011, 3:24 PM

                What do you have in your /boot/loader.conf ?

                Can you try a standard pfSense image?

                1 Reply Last reply Reply Quote 0
                • S
                  schnauber
                  last edited by Jun 3, 2011, 8:07 PM

                  can you tell me, how I get access to the loader.conf please? Is this file in the root directory of pfhacom? Sorry, I am a unix dummy. I have choosen the pfhacom Image because I want VGA support.

                  1 Reply Last reply Reply Quote 0
                  • S
                    stephenw10 Netgate Administrator
                    last edited by Jun 3, 2011, 10:19 PM

                    Everyone starts some where.  :)
                    From the command line:

                    
                    [2.0-RC2][root@pfsense.fire.box]/root(1): cat /boot/loader.conf
                    hw.ata.atapi_dma="0"
                    hw.ata.ata_dma="0"
                    loader_color="NO"
                    autoboot_delay="5"
                    hw.ata.wc="0"
                    kern.ipc.nmbclusters="0"
                    beastie_disable="YES"
                    vm.kmem_size="435544320"
                    vm.kmem_size_max="535544320"
                    
                    

                    Alternatively you can open it from the file editor in the GUI: Diagnostics -> Edit File
                    Just don't go making random changes!

                    Steve

                    1 Reply Last reply Reply Quote 0
                    • S
                      schnauber
                      last edited by Jun 4, 2011, 10:15 AM

                      I have exactly the same settings below!

                      1 Reply Last reply Reply Quote 0
                      • S
                        stephenw10 Netgate Administrator
                        last edited by Jun 4, 2011, 10:30 AM

                        Hmmm,
                        I'm out of ideas at this point.  :(
                        You could try reflashing the card. You could try a different CF card. You could try a different image.

                        Steve

                        1 Reply Last reply Reply Quote 0
                        15 out of 16
                        • First post
                          15/16
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                          This community forum collects and processes your personal information.
                          consent.not_received