Re: Booting takes too long. Why? (/ was not properly dismounted)
shutdown -h -o appears to behave the same as simply using halt I'm glad I dont have to wait for the disc errors anymore thanks for your help Rohit On Tuesday 17 June 2003 15:16, Shantanu Mahajan wrote: > +-- Rohit [freebsd] [16-06-03 08:42 +]: > | Thanks for your help Jud, you are absolutely right. With issuing the halt > | command, there are no excessive delays in booting. Inface booting is > | really fast. > | > | Thanks > | > | Rohit > > Rohit: > You mean to say that when you use 'halt' instead of > 'shutdown -h', your machince boots faster? > > Roger: > I don't think that 'shutdown -h' = 'halt' > Rohit is not invoking halt. > 'shutdown -h -o' = 'halt' > > Rohit: > Can you try 'shutdown -h -o' and let us know what's the > result? > > Regards, > Shantanu > > | On Saturday 14 June 2003 20:04, Jud wrote: > | > On Sat, 14 Jun 2003 12:28:23 +0530, Shantanu Mahajan > | > > | > <[EMAIL PROTECTED]> wrote: > | > > | I shutdown using the shutdown -h now command > | > > | or reboot using reboot now > | > > > | > > did you try 'halt'? > | > > what msg. do you see after the shutdown is complete? > | > > | > From the halt(8) man page: > | > > | > "Normally, the shutdown(8) utility is used when the system needs to be > | > halted or restarted, giving users advance warning of their impending > | > doom and cleanly terminating specific programs." > | > > | > From the shutdown(8) man page: > | > > | > "The following options are available: > | > -h The system is halted at the specified time." > | > > | > So Rohit is in fact using 'halt' in the way it is normally invoked, as > | > an option to 'shutdown.' Is there a reason that 'halt' without > | > 'shutdown' would be preferable in this case? > | > > | > Jud ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting takes too long. Why? (/ was not properly dismounted)
+-- Rohit [freebsd] [16-06-03 08:42 +]: | Thanks for your help Jud, you are absolutely right. With issuing the halt | command, there are no excessive delays in booting. Inface booting is really | fast. | | Thanks | | Rohit Rohit: You mean to say that when you use 'halt' instead of 'shutdown -h', your machince boots faster? Roger: I don't think that 'shutdown -h' = 'halt' Rohit is not invoking halt. 'shutdown -h -o' = 'halt' Rohit: Can you try 'shutdown -h -o' and let us know what's the result? Regards, Shantanu | | | On Saturday 14 June 2003 20:04, Jud wrote: | > On Sat, 14 Jun 2003 12:28:23 +0530, Shantanu Mahajan | > | > <[EMAIL PROTECTED]> wrote: | > > | I shutdown using the shutdown -h now command | > > | or reboot using reboot now | > > | > > did you try 'halt'? | > > what msg. do you see after the shutdown is complete? | > | > From the halt(8) man page: | > | > "Normally, the shutdown(8) utility is used when the system needs to be | > halted or restarted, giving users advance warning of their impending doom | > and cleanly terminating specific programs." | > | > From the shutdown(8) man page: | > | > "The following options are available: | > -h The system is halted at the specified time." | > | > So Rohit is in fact using 'halt' in the way it is normally invoked, as an | > option to 'shutdown.' Is there a reason that 'halt' without 'shutdown' | > would be preferable in this case? | > | > Jud -- Nice tcsh prompt: set prompt = '[EMAIL PROTECTED]:%~%# ' ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting takes too long. Why? (/ was not properly dismounted)
Thanks for your help Jud, you are absolutely right. With issuing the halt command, there are no excessive delays in booting. Inface booting is really fast. Thanks Rohit On Saturday 14 June 2003 20:04, Jud wrote: > On Sat, 14 Jun 2003 12:28:23 +0530, Shantanu Mahajan > > <[EMAIL PROTECTED]> wrote: > > | I shutdown using the shutdown -h now command > > | or reboot using reboot now > > > > did you try 'halt'? > > what msg. do you see after the shutdown is complete? > > From the halt(8) man page: > > "Normally, the shutdown(8) utility is used when the system needs to be > halted or restarted, giving users advance warning of their impending doom > and cleanly terminating specific programs." > > From the shutdown(8) man page: > > "The following options are available: > -h The system is halted at the specified time." > > So Rohit is in fact using 'halt' in the way it is normally invoked, as an > option to 'shutdown.' Is there a reason that 'halt' without 'shutdown' > would be preferable in this case? > > Jud > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting takes too long. Why? (/ was not properly dismounted)
On Sat, 14 Jun 2003 12:28:23 +0530, Shantanu Mahajan <[EMAIL PROTECTED]> wrote: | I shutdown using the shutdown -h now command | or reboot using reboot now did you try 'halt'? what msg. do you see after the shutdown is complete? From the halt(8) man page: "Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending doom and cleanly terminating specific programs." From the shutdown(8) man page: "The following options are available: -h The system is halted at the specified time." So Rohit is in fact using 'halt' in the way it is normally invoked, as an option to 'shutdown.' Is there a reason that 'halt' without 'shutdown' would be preferable in this case? Jud ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting takes too long. Why? (/ was not properly dismounted)
+-- Rohit [freebsd] [13-06-03 10:35 +]: | 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 did you try 'halt'? what msg. do you see after the shutdown is complete? Regards, Shantanu | | | Rohit | | | 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 | [EMAIL PROTECTED]:/usr/src/sys/compile/ROHIT_MAY11_2003 | Timecounter "i8254" frequency 1193182 Hz | CPU: Mobile AMD Athlon(tm) XP 1500+ (1325.14-MHz 686-class CPU) | Origin = "AuthenticAMD" Id = 0x680 Stepping = 0 | | Features=0x383f9ff | AMD Features=0xc048 | 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: on motherboard | apm0: found APM BIOS v1.2, connected at v1.2 | npx0: on motherboard | npx0: INT 16 interface | pcib0: on motherboard | pci0: on pcib0 | pcib1: at device 1.0 on pci0 | pci1: on pcib1 | pci1: at 5.0 irq 10 | ohci0: 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: 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: at device 7.0 on pci0 | isa0: on isab0 | pcm0: port 0x8400-0x84ff mem 0xf4015000-0xf4015fff irq 5 at | device 8.0 on pci0 | pcm0: (id=0x41445363) | pci_cfgintr_virgin: using routable interrupt 10 | pci_cfgintr: ROUTE_INTERRUPT failed. | pcic0: 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: on pcic0 | rl0: port 0x8800-0x88ff mem 0xf4017800-0xf40178ff | irq 11 at device 11.0 on pci0 | ROHIT**rl0: Ethernet address: | 00:08:02:f3:d2:03 | ROHIT**miibus0: on rl0 | rlphy0: on miibus0 | rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto | pci0: (vendor=0x14f1, dev=0x2f00) at 12.0 irq 10 | ohci1: mem 0xf4016000-0xf4016fff | irq 11 at device 15.0 on pci0 | usb1: OHCI version 1.0, legacy support | usb1: 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: 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: at device 17.0 on pci0 | alpm0: driver is using old-style compatibility shims | fwohci0: mem | 0xf401-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: 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: on alsmb0 | smb0: on smbus0 | orm0: at iomem 0xc-0xcefff,0xdf000-0xd,0xe-0xe3fff | on isa0 | fdc0: 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: at port 0x60,0x64 on isa0 | atkbd0: flags 0x1 irq 1 on atkbdc0 | kbd0 at atkbd0 | psm0: irq 12 on atkbdc0 | psm0: model IntelliMouse, device ID 3 | vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 | sc0: at flags 0x100 on isa0 | sc0: VGA <16 virtual consoles, flags=0x300> | ppc0: 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: on ppbus0 | lpt0: Interrupt-driven port | unknown: can't assign resources | unknown: can't assign resources | unknown: can't assign resources | unkn
Re: Booting takes too long. Why? (/ was not properly dismounted)
could the shutdown binary be broken on your installations ? are you running the same release on all machines installed from the same media ? LukeK - Original Message - From: "Bill Moran" <[EMAIL PROTECTED]> To: "Rohit" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, June 14, 2003 12:43 AM Subject: Re: Booting takes too long. Why? (/ was not properly dismounted) > Rohit wrote: > > 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) > > My mistake ... I misread your original post. > > > I shutdown using the shutdown -h now command > > or reboot using reboot now > > How big is your / partition? During the halt/reboot sequence, does it give any > errors? Are all the buffers flushed? > > I'm grasping at straws here ... Is there some daemon running that takes too long > to shutdown or doesn't shutdown cleanly, thus preventing the system from flushing > all its buffers and marking the fs clean? > > One thing to try: manually stop all processes that you can, then issue "sync" a > few times, then (when disk activity has stopped) issue reboot. See if / is still > dirty on reboot. > > Does fsck succeed during boot? Possibly boot into single-usr mode and issue > "fsck -y" until the filesystems are all marked clean, then try your standard > method of rebooting and see if the / partition is now clean. > > Many guesses here. Hopefully one of them will be helpful. > > -- > Bill Moran > Potential Technologies > http://www.potentialtech.com > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting takes too long. Why? (/ was not properly dismounted)
Rohit wrote: 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) My mistake ... I misread your original post. I shutdown using the shutdown -h now command or reboot using reboot now How big is your / partition? During the halt/reboot sequence, does it give any errors? Are all the buffers flushed? I'm grasping at straws here ... Is there some daemon running that takes too long to shutdown or doesn't shutdown cleanly, thus preventing the system from flushing all its buffers and marking the fs clean? One thing to try: manually stop all processes that you can, then issue "sync" a few times, then (when disk activity has stopped) issue reboot. See if / is still dirty on reboot. Does fsck succeed during boot? Possibly boot into single-usr mode and issue "fsck -y" until the filesystems are all marked clean, then try your standard method of rebooting and see if the / partition is now clean. Many guesses here. Hopefully one of them will be helpful. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting takes too long. Why? (/ was not properly dismounted)
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 Rohit 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 [EMAIL PROTECTED]:/usr/src/sys/compile/ROHIT_MAY11_2003 Timecounter "i8254" frequency 1193182 Hz CPU: Mobile AMD Athlon(tm) XP 1500+ (1325.14-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x680 Stepping = 0 Features=0x383f9ff AMD Features=0xc048 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: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 5.0 irq 10 ohci0: 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: 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: at device 7.0 on pci0 isa0: on isab0 pcm0: port 0x8400-0x84ff mem 0xf4015000-0xf4015fff irq 5 at device 8.0 on pci0 pcm0: (id=0x41445363) pci_cfgintr_virgin: using routable interrupt 10 pci_cfgintr: ROUTE_INTERRUPT failed. pcic0: 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: on pcic0 rl0: port 0x8800-0x88ff mem 0xf4017800-0xf40178ff irq 11 at device 11.0 on pci0 ROHIT**rl0: Ethernet address: 00:08:02:f3:d2:03 ROHIT**miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: (vendor=0x14f1, dev=0x2f00) at 12.0 irq 10 ohci1: mem 0xf4016000-0xf4016fff irq 11 at device 15.0 on pci0 usb1: OHCI version 1.0, legacy support usb1: 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: 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: at device 17.0 on pci0 alpm0: driver is using old-style compatibility shims fwohci0: mem 0xf401-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: 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: on alsmb0 smb0: on smbus0 orm0: at iomem 0xc-0xcefff,0xdf000-0xd,0xe-0xe3fff on isa0 fdc0: 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: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> ppc0: 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: on ppbus0 lpt0: Interrupt-driven port unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: 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 [58140/16/63] at ata0-master UDMA100 acd0: CD-RW at ata1-master PIO4 Mounting root from ufs:/dev/ad0s2a WARNING: / was not properly dis
