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

    Manual root filesystem specification

    Scheduled Pinned Locked Moved General pfSense Questions
    10 Posts 4 Posters 14.1k 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.
    • J
      Jakobud
      last edited by

      I just got 1.2.3 installed (finally after many hurdles) on a test machine.

      I have a single SATA HDD in the server, which shows up as "ad4".

      After installation, I get the error

      Manual root filesystem specification
      

      And I need to specify the filesystem and device.

      After some trial and error and forum searching I discovered that the following worked for us:

      ufs:ad4s1a
      

      And doing some more forum searching, I discovered some threads that adjusting your /etc/fstab will make it so that you don't have to specify this information everytime you bootup.

      My fstab looks like this atm:

      # Device                Mountpoint      FStype  Options         Dump    Pass#
      /dev/ad4s1a             /                 ufs       rw              1       1
      /dev/ad4s1b             none            swap    sw              0       0
      

      What do I need to change?

      PS - The forum admin needs to change the SMF forum's CSS to use a monospace typeface for code blocks :)

      1 Reply Last reply Reply Quote 0
      • W
        wallabybob
        last edited by

        Given your /etc/fstab it is not obvious why you need to specify the root file system.

        I suggest you reboot and if the same problem recurs post a bit more context (say the preceding six lines and following few lines) to the request to specify the root file system.

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

          Can anyone provide some help for us on this?  We are still having this problem.  When we boot up pfSense, we have to manually input the filesystem to mount.  The fstab has not changed and is still the same as above.

          1 Reply Last reply Reply Quote 0
          • jimpJ
            jimp Rebel Alliance Developer Netgate
            last edited by

            If the fstab device matches exactly with what you type in, it shouldn't be necessary.

            Out of curiosity, how large is / on there?

            On some machines we have seen that / needs to be smaller (~8GB) and then the rest can be in /usr, but that requires going through the custom install and not using quick/auto.

            That's just another guess though, as wallabybob said we'd need a lot more context in the boot log to offer any real help. The whole /var/log/dmesg.boot would help, as would the output of "mount" and "df".

            Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

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

              mount

              
              /dev/ad4s1a on / (ufs, local)
              devfs on /dev (devfs, local)
              /dev/md0 on /var/run (ufs, local)
              devfs on /var/dhcpd/dev (devfs, local)
              
              

              df -h

              
              Filesystem     Size    Used   Avail Capacity  Mounted on
              /dev/ad4s1a    142G    490M    131G     0%    /
              devfs          1.0K    1.0K      0B   100%    /dev
              /dev/md0       3.6M     28K    3.3M     1%    /var/run
              devfs          1.0K    1.0K      0B   100%    /var/dhcpd/dev
              
              

              dmesg

              
              Copyright (c) 1992-2009 The FreeBSD Project.
              Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
                      The Regents of the University of California. All rights reserved.
              FreeBSD is a registered trademark of The FreeBSD Foundation.
              FreeBSD 7.2-RELEASE-p5 #0: Sun Dec  6 22:57:48 EST 2009
                  sullrich@FreeBSD_7.2_pfSense_1.2.3_snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense.7
              Timecounter "i8254" frequency 1193182 Hz quality 0
              CPU: AMD Sempron(tm) Processor 3100+ (1808.81-MHz 686-class CPU)
                Origin = "AuthenticAMD"  Id = 0x10fc0  Stepping = 0
                Features=0x78bfbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,mmx,fxsr,sse,sse2>AMD Features=0xe2500800 <syscall,nx,mmx+,ffxsr,lm,3dnow!+,3dnow!>AMD Features2=0x1 <lahf>real memory  = 1073479680 (1023 MB)
              avail memory = 1036615680 (988 MB)
              ACPI APIC Table: <a m="" i ="" oemapic="">
              ioapic0 <version 1.1="">irqs 0-23 on motherboard
              wlan: mac acl policy registered
              kbd1 at kbdmux0
              cryptosoft0: <software crypto="">on motherboard
              padlock0: No ACE support.
              acpi0:</software></version> </a><a m="" i="" oemrsdt="">on motherboard
              acpi0: [ITHREAD]
              acpi0: Power Button (fixed)
              acpi0: reservation of 0, a0000 (3) failed
              acpi0: reservation of 100000, 3ff00000 (3) failed
              Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
              acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
              pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
              pci0: <acpi pci="" bus="">on pcib0
              agp0: <nvidia nforce3-250="" agp="" controller="">on hostb0
              isab0: <pci-isa bridge="">at device 1.0 on pci0
              isa0: <isa bus="">on isab0
              pci0: <serial bus,="" smbus="">at device 1.1 (no driver attached)
              ohci0: <ohci (generic)="" usb="" controller="">mem 0xfebfd000-0xfebfdfff irq 20 at device 2.0 on pci0
              ohci0: [GIANT-LOCKED]
              ohci0: [ITHREAD]
              usb0: OHCI version 1.0, legacy support
              usb0: <ohci (generic)="" usb="" controller="">on ohci0
              usb0: USB revision 1.0
              uhub0: <nvidia 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usb0
              uhub0: 4 ports with 4 removable, self powered
              ohci1: <ohci (generic)="" usb="" controller="">mem 0xfebfe000-0xfebfefff irq 21 at device 2.1 on pci0
              ohci1: [GIANT-LOCKED]
              ohci1: [ITHREAD]
              usb1: OHCI version 1.0, legacy support
              usb1: <ohci (generic)="" usb="" controller="">on ohci1
              usb1: USB revision 1.0
              uhub1: <nvidia 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usb1
              uhub1: 4 ports with 4 removable, self powered
              ehci0: <nvidia 250="" nforce3="" usb="" 2.0="" controller="">mem 0xfebffc00-0xfebffcff irq 22 at device 2.2 on pci0
              ehci0: [GIANT-LOCKED]
              ehci0: [ITHREAD]
              usb2: EHCI version 1.0
              usb2: companion controllers, 4 ports each: usb0 usb1
              usb2: <nvidia 250="" nforce3="" usb="" 2.0="" controller="">on ehci0
              usb2: USB revision 2.0
              uhub2: <nvidia 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usb2
              uhub2: 8 ports with 8 removable, self powered
              nfe0: <nvidia nforce3="" mcp7="" networking="" adapter="">port 0xec00-0xec07 mem 0xfebfc000-0xfebfcfff irq 20 at device 5.0 on pci0
              miibus0: <mii bus="">on nfe0
              rlphy0: <ic 10="" 100="" plus="" phy="">PHY 1 on miibus0
              rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
              nfe0: Ethernet address: 00:15:f2:9b:86:2c
              nfe0: [FILTER]
              pci0: <multimedia, audio="">at device 6.0 (no driver attached)
              atapci0: <nvidia nforce3="" pro="" udma133="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 8.0 on pci0
              ata0: <ata 0="" channel="">on atapci0
              ata0: [ITHREAD]
              ata1: <ata 1="" channel="">on atapci0
              ata1: [ITHREAD]
              atapci1: <nvidia nforce3="" pro="" sata150="" controller="">port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xc800-0xc80f,0xc400-0xc47f irq 22 at device 10.0 on pci0
              atapci1: [ITHREAD]
              ata2: <ata 0="" channel="">on atapci1
              ata2: [ITHREAD]
              ata3: <ata 1="" channel="">on atapci1
              ata3: [ITHREAD]
              pcib1: <acpi pci-pci="" bridge="">at device 11.0 on pci0
              pci1: <acpi pci="" bus="">on pcib1
              vgapci0: <vga-compatible display="">mem 0xfd000000-0xfdffffff,0xea000000-0xebffffff irq 16 at device 0.0 on pci1
              pcib2: <acpi pci-pci="" bridge="">at device 14.0 on pci0
              pci2: <acpi pci="" bus="">on pcib2
              em0: <intel(r) 1000="" pro="" network="" connection="" 6.9.6="">port 0xbc00-0xbc3f mem 0xfeae0000-0xfeafffff,0xfeac0000-0xfeadffff irq 17 at device 7.0 on pci2
              em0: [FILTER]
              em0: Ethernet address: 00:1b:21:5d:d2:e9
              em1: <intel(r) 1000="" pro="" network="" connection="" 6.9.6="">port 0xb800-0xb83f mem 0xfea80000-0xfea9ffff,0xfea60000-0xfea7ffff irq 18 at device 8.0 on pci2
              em1: [FILTER]
              em1: Ethernet address: 00:1b:21:5d:d6:74
              em2: <intel(r) 1000="" pro="" network="" connection="" 6.9.6="">port 0xb400-0xb43f mem 0xfea20000-0xfea3ffff,0xfea00000-0xfea1ffff irq 19 at device 9.0 on pci2
              em2: [FILTER]
              em2: Ethernet address: 00:1b:21:5d:d6:73
              acpi_button0: <power button="">on acpi0
              speaker0: <pc speaker="">port 0x61 on acpi0
              fdc0: <floppy drive="" controller="" (fde)="">port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
              fdc0: [FILTER]
              atkbdc0: <keyboard controller="" (i8042)="">port 0x60,0x64 irq 1 on acpi0
              atkbd0: <at keyboard="">irq 1 on atkbdc0
              kbd0 at atkbd0
              atkbd0: [GIANT-LOCKED]
              atkbd0: [ITHREAD]
              psm0: <ps 2="" mouse="">irq 12 on atkbdc0
              psm0: [GIANT-LOCKED]
              psm0: [ITHREAD]
              psm0: model IntelliMouse, device ID 3
              sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
              sio0: type 16550A
              sio0: [FILTER]
              cpu0: <acpi cpu="">on acpi0
              powernow0: <cool`n'quiet k8="">on cpu0
              device_attach: powernow0 attach returned 6
              pmtimer0 on isa0
              orm0: <isa option="" roms="">at iomem 0xc0000-0xc8fff,0xc9000-0xc9fff,0xca000-0xcafff,0xcb000-0xcbfff pnpid ORM0000 on isa0
              sc0: <system console="">at flags 0x100 on isa0
              sc0: VGA <16 virtual consoles, flags=0x300>
              sio1: configured irq 3 not in bitmap of probed irqs 0
              sio1: port may not be enabled
              vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
              Timecounter "TSC" frequency 1808812921 Hz quality 800
              Timecounters tick every 1.000 msec
              IPsec: Initialized Security Association Processing.
              acd0: DVDR <nec dvd="" rw="" nd-3500ag="" 2.98="">at ata0-master UDMA33
              ad4: 152627MB <seagate st3160023as="" 3.05="">at ata2-master SATA150
              
              Manual root filesystem specification:
                <fstype>:<device>Mount <device>using filesystem <fstype>eg. ufs:da0s1a
                ?                  List valid disk boot devices
                <empty line="">Abort manual input
              
              mountroot> ufs:ad4s1a
              Trying to mount root from ufs:ad4s1a
              WARNING: / was not properly dismounted
              WARNING: R/W mount of / denied.  Filesystem is not clean - run fsck
              WARNING: R/W mount of / denied.  Filesystem is not clean - run fsck</empty></fstype></device></device></fstype></seagate></nec></generic></system></isa></cool`n'quiet></acpi></ps></at></keyboard></floppy></pc></power></intel(r)></intel(r)></intel(r)></acpi></acpi></vga-compatible></acpi></acpi></ata></ata></nvidia></ata></ata></nvidia></multimedia,></ic></mii></nvidia></nvidia></nvidia></nvidia></nvidia></ohci></ohci></nvidia></ohci></ohci></serial></isa></pci-isa></nvidia></acpi></acpi></a></lahf></syscall,nx,mmx+,ffxsr,lm,3dnow!+,3dnow!></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,mmx,fxsr,sse,sse2> 
              
              1 Reply Last reply Reply Quote 0
              • J
                Jakobud
                last edited by

                Does this help?  Anything else I should post for you?

                1 Reply Last reply Reply Quote 0
                • jimpJ
                  jimp Rebel Alliance Developer Netgate
                  last edited by

                  Nothing really unusual there. It may be a quirk of your system that it doesn't like having such a large /

                  As I said in a post earlier in the thread, try to reinstall, using the custom install, and make a smaller / (maybe 8-10GB) and then /usr that takes up the rest of the drive.

                  Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                  Need help fast? Netgate Global Support!

                  Do not Chat/PM for help!

                  1 Reply Last reply Reply Quote 0
                  • Z
                    zuikway
                    last edited by

                    Was there any resolution to this problem? I'm new to PFSense and BSD, but I also have to manually mount. System is 3ghz P4, 2gb ram, 250gb sata drive.

                    Also I'm not sure why it is attempting to mount from USB devices. Is there something that needs to be configured in /boot? dmesg shows:

                    ...
                    Root mount waiting for: usbus4 usbus3 usbus2 usbus1 usbus0
                    uhub0: 2 ports with 2 removable, self powered
                    uhub1: 2 ports with 2 removable, self powered
                    uhub2: 2 ports with 2 removable, self powered
                    uhub3: 2 ports with 2 removable, self powered
                    Root mount waiting for: usbus4
                    Root mount waiting for: usbus4
                    Root mount waiting for: usbus4
                    uhub4: 8 ports with 8 removable, self powered
                    Loader variables:
                    vfs.root.mountfrom=
                    vfs.root.mountfrom.options=
                    
                    Manual root filesystem specification:
                      <fstype>:<device>Mount <device>using filesystem <fstype>eg. ufs:/dev/da0s1a
                                           eg. cd9660:/dev/acd0
                                           This is equivalent to: mount -t cd9660 /dev/acd0 /
                    
                      ?                  List valid disk boot devices
                      <empty line="">Abort manual input
                    
                    mountroot> ufs:/dev/ad14s1a
                    Trying to mount root from ufs:/dev/ad14s1a</empty></fstype></device></device></fstype> 
                    
                    > cat /etc/fstab
                    # Device                Mountpoint      FStype  Options         Dump    Pass#
                    /dev/ad14s1a            /               ufs     rw              1       1
                    /dev/ad14s1b            none            swap    sw              0       0
                    >
                    
                    
                    > df -h
                    Filesystem      Size    Used   Avail Capacity  Mounted on
                    /dev/ad14s1a    222G    166M    204G     0%    /
                    devfs           1.0K    1.0K      0B   100%    /dev
                    /dev/md0        3.6M     44K    3.3M     1%    /var/run
                    devfs           1.0K    1.0K      0B   100%    /var/dhcpd/dev
                    
                    
                    1 Reply Last reply Reply Quote 0
                    • jimpJ
                      jimp Rebel Alliance Developer Netgate
                      last edited by

                      Not sure if it was resolved because there was never any feedback from my suggestion to try a smaller root (/) slice and use the rest for /usr.

                      Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                      Need help fast? Netgate Global Support!

                      Do not Chat/PM for help!

                      1 Reply Last reply Reply Quote 0
                      • Z
                        zuikway
                        last edited by

                        I did a fresh install on another disk and identical system. Seems to work just fine, so I'm not sure what the issue is/was? Perhaps the disk has a problem.

                        Update: For those who come across this thread … The cause of one PC not booting properly is still unknown but most likely a hardware issue with the MB.

                        I determined that the issue was not the disk drive, cables, or network cards. I installed on two systems with identical MB (Asus p4c800e) and bios settings. On one board, the standard ich sata port would not boot properly. Same drives on alternate PC never showed a problem. Switchiing to the Promise controller sata port on the bad board does work. Other OS's have no problem booting (linux, windoze). I can only assume that the older MB may be failing in some way.

                        I'm new to BSD and not familiar with how BSD determines device names, but on one it would find the disk as ad4s1a and on the other (non-working) ad8s1a with promise controller disabled.

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