Booting takes too long. Why? (/ was not properly dismounted)

Rohit rohitvis at
Fri Jun 13 07:36:54 PDT 2003

Here is the dmesg. However, I should tell you that this has been the case with 
all my FreeBSD boxes. I have two PC's running FreeBSD and a Compaq laptop 
running FreeBSd all have different types of harddrives. 

The main problem is that everytime I boot I get the message saying / was not 
dismounted properly and then it goes through and fixes all the drive block 
errors. (This is the case on all my computers) 

I shutdown using the shutdown -h now command
or reboot using reboot now


opyright (c) 1992-2003 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 4.8-RELEASE #8: Wed May 21 13:22:57 GMT 2003
    ro at
Timecounter "i8254"  frequency 1193182 Hz
CPU: Mobile AMD Athlon(tm) XP 1500+ (1325.14-MHz 686-class CPU)
  Origin = "AuthenticAMD"  Id = 0x680  Stepping = 0
  AMD Features=0xc0480000<MP,AMIE,DSP,3DNow!>
real memory  = 251658240 (245760K bytes)
avail memory = 240287744 (234656K bytes)
Preloaded elf kernel "kernel" at 0xc0465000.
module_register_init: MOD_LOAD (vesa, c0310844, 0) error 6
netsmb_dev: loaded
Pentium Pro MTRR support enabled
md0: Malloc disk
Using $PIR table, 11 entries at 0xc00fdf10
apm0: <APM BIOS> on motherboard
apm0: found APM BIOS v1.2, connected at v1.2
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pcib1: <PCI to PCI bridge (vendor=1002 device=700f)> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pci1: <ATI model 4336 graphics accelerator> at 5.0 irq 10
ohci0: <AcerLabs M5237 (Aladdin-V) USB controller> mem 0xf4014000-0xf4014fff 
irq 11 at device 2.0 on pci0
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0: <AcerLabs M5237 (Aladdin-V) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
isab0: <AcerLabs M1533 portable PCI-ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
pcm0: <Acer Labs M5451> port 0x8400-0x84ff mem 0xf4015000-0xf4015fff irq 5 at 
device 8.0 on pci0
pcm0: <unknown ac97 codec> (id=0x41445363)
pci_cfgintr_virgin: using routable interrupt 10
pci_cfgintr: ROUTE_INTERRUPT failed.
pcic0: <TI PCI-1410 PCI-CardBus Bridge> mem 0xffbfe000-0xffbfefff at device 
10.0 on pci0
pci_cfgintr_virgin: using routable interrupt 10
pci_cfgintr: ROUTE_INTERRUPT failed.
pcic0: No PCI interrupt routed, trying ISA.
pcic0: Polling mode
pcic0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][CSC 
serial isa irq]
pccard0: <PC Card 16-bit bus (classic)> on pcic0
rl0: <RealTek 8139 10/100BaseTX> port 0x8800-0x88ff mem 0xf4017800-0xf40178ff 
irq 11 at device 11.0 on pci0
********************ROHIT**********************rl0: Ethernet address: 
********************ROHIT**********************miibus0: <MII bus> on rl0
rlphy0: <RealTek internal media interface> on miibus0
rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pci0: <unknown card> (vendor=0x14f1, dev=0x2f00) at 12.0 irq 10
ohci1: <AcerLabs M5237 (Aladdin-V) USB controller> mem 0xf4016000-0xf4016fff 
irq 11 at device 15.0 on pci0
usb1: OHCI version 1.0, legacy support
usb1: <AcerLabs M5237 (Aladdin-V) USB controller> on ohci1
usb1: USB revision 1.0
uhub1: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 4 ports with 4 removable, self powered
atapci0: <AcerLabs Aladdin ATA100 controller> port 0x8080-0x808f irq 0 at 
device 16.0 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
alpm0: <AcerLabs M15x3 Power Management Unit> at device 17.0 on pci0
alpm0: driver is using old-style compatibility shims
fwohci0: <Texas Instruments TSB43AB22/A> mem 
0xf4010000-0xf4013fff,0xf4017000-0xf40177ff irq 10 at device 19.0 on pci0
fwohci0: PCI bus latency is 64.
fwohci0: OHCI version 1.10 (ROM=1)
fwohci0: No. of Isochronous channel is 4.
fwohci0: EUI64 00:08:02:71:9b:f3:cb:d2
fwohci0: Phy 1394a available S400, 2 ports.
fwohci0: Link S400, max_rec 2048 bytes.
firewire0: <IEEE1394(FireWire) bus> on fwohci0
fwohci0: Initiate bus reset
fwohci0: BUS reset
fwohci0: node_id = 0xc000ffc0, CYCLEMASTER mode
firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
smbus0: <System Management Bus> on alsmb0
smb0: <SMBus general purpose I/O> on smbus0
orm0: <Option ROMs> at iomem 0xc0000-0xcefff,0xdf000-0xdffff,0xe0000-0xe3fff 
on isa0
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/1 bytes threshold
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
unknown: <PNP0000> can't assign resources
unknown: <PNP0303> can't assign resources
unknown: <PNP0c02> can't assign resources
unknown: <PNP0c02> can't assign resources
unknown: <PNP0401> can't assign resources
unknown: <PNP0700> can't assign resources
IP packet filtering initialized, divert enabled, rule-based forwarding 
enabled, default to accept, logging limited to 10 packets/entry by default
pccard: card inserted, slot 0
ad0: 28615MB <FUJITSU MHR2030AT> [58140/16/63] at ata0-master UDMA100
acd0: CD-RW <DW-224E> at ata1-master PIO4
Mounting root from ufs:/dev/ad0s2a
WARNING: / was not properly dismounted

On Friday 13 June 2003 14:16, Bill Moran wrote:
> Rohit wrote:
> > Hi,
> > I'm curious why booting my FreeBSD box takes so long. Is there a way to
> > bypass this. For some reason ever since 4.6 it has taken quite a bit of
> > time fixing harddrive errors (or something) while booting which takes too
> > long.
> You'll probably get better response if you post dmesg output and indicate
> the part of the boot process that is taking a long time.

More information about the freebsd-questions mailing list