LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices


Reply
  Search this Thread
Old 12-23-2003, 05:01 PM   #1
Razgo
Member
 
Registered: Dec 2003
Location: Australia-Brisbane
Distribution: RHEL WS basic edition-gnome
Posts: 40

Rep: Reputation: 15
how do i boot into linux without it scanning all hd


basically i have never figured out how my red hat 9 can boot without scanning all my hardrives first?

using gnome is there a setting somewhere i can change?
 
Old 12-23-2003, 05:05 PM   #2
Mara
Moderator
 
Registered: Feb 2002
Location: Grenoble
Distribution: Debian
Posts: 9,696

Rep: Reputation: 232Reputation: 232Reputation: 232
What do you mean by 'scan'? Running fsck?
 
Old 12-23-2003, 05:26 PM   #3
Razgo
Member
 
Registered: Dec 2003
Location: Australia-Brisbane
Distribution: RHEL WS basic edition-gnome
Posts: 40

Original Poster
Rep: Reputation: 15
thanks mara, being a noob i will explain as best i can.

i boot and GRUB starts. i select linux, then there is this scanning checking thing going on for every drive/partition.

i have 3 hardrives and 4 patitions. and when it hits the drive linux is on then it fires up the linux loading process.
 
Old 12-23-2003, 09:16 PM   #4
bigrigdriver
LQ Addict
 
Registered: Jul 2002
Location: East Centra Illinois, USA
Distribution: Debian stable
Posts: 5,908

Rep: Reputation: 356Reputation: 356Reputation: 356Reputation: 356
Linux will check the fille systems for errors during the boot process. What partitions and filesystems to check are listed in the file /etc/fstab. The more partitions you check on boot, the longer the boot process. In order to prevent Linux from checking partitions you don't want checked, remove them from /ect/fstab. BEWARE. If any errors creep into those partitions, you'll never know about it until it's a system-fatal problem. The solution I employ: I copied fstab 4 times (fstab1, 2, 3, and 4), retaining /etc/fstab unchanged. I edited each copy to reflect the configuration I want for a particular purpose. I then wrote a simple bash script to be run as root, offering a menu of choices. When I select the one I want. /etc/fstab is rewriten with the copy I chose. Then I reboot. I eliminate what I regard as unnecessary fs checking for things I use irregularly, and fstab is set to the things I use regularly.
My 2 cents. Hope it reaps a profit for you.
 
Old 12-23-2003, 11:57 PM   #5
Razgo
Member
 
Registered: Dec 2003
Location: Australia-Brisbane
Distribution: RHEL WS basic edition-gnome
Posts: 40

Original Poster
Rep: Reputation: 15
this is my fstab:

LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/hdd5 swap swap defaults 0 0
/dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner,kudzu 0 0

it takes ages as it is scanning hda , hda1 hda2, hda5 then reports hda not ready for reading etc etc....

i think linux is in hdd6
 
Old 12-24-2003, 12:56 AM   #6
C Scott
LQ Newbie
 
Registered: Dec 2003
Location: Nashville, TN
Distribution: Mandrake 9.2 Enterprise Download
Posts: 12

Rep: Reputation: 0
Removing them from fstab may not be what you what to do. When you do that, it also removes those drives from your boot choices. Is there another solution?
 
Old 12-24-2003, 06:04 PM   #7
Razgo
Member
 
Registered: Dec 2003
Location: Australia-Brisbane
Distribution: RHEL WS basic edition-gnome
Posts: 40

Original Poster
Rep: Reputation: 15
here is my system log. it is all the hda, hdd checking that takes the longest and seems pointless?


Dec 25 09:54:12 c210-49-92-137 syslogd 1.4.1: restart.
Dec 25 09:54:12 c210-49-92-137 syslog: syslogd startup succeeded
Dec 25 09:54:12 c210-49-92-137 kernel: klogd 1.4.1, log source = /proc/kmsg started.
Dec 25 09:54:12 c210-49-92-137 kernel: Linux version 2.4.20-8 (bhcompile@stripples.devel.redhat.com) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Thu Mar 13 17:18:24 EST 2003
Dec 25 09:54:12 c210-49-92-137 kernel: BIOS-provided physical RAM map:
Dec 25 09:54:12 c210-49-92-137 kernel: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
Dec 25 09:54:12 c210-49-92-137 kernel: BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
Dec 25 09:54:12 c210-49-92-137 kernel: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Dec 25 09:54:12 c210-49-92-137 kernel: BIOS-e820: 0000000000100000 - 000000001ffec000 (usable)
Dec 25 09:54:12 c210-49-92-137 kernel: BIOS-e820: 000000001ffec000 - 000000001ffef000 (ACPI data)
Dec 25 09:54:12 c210-49-92-137 kernel: BIOS-e820: 000000001ffef000 - 000000001ffff000 (reserved)
Dec 25 09:54:12 c210-49-92-137 kernel: BIOS-e820: 000000001ffff000 - 0000000020000000 (ACPI NVS)
Dec 25 09:54:12 c210-49-92-137 kernel: BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
Dec 25 09:54:12 c210-49-92-137 kernel: 0MB HIGHMEM available.
Dec 25 09:54:12 c210-49-92-137 kernel: 511MB LOWMEM available.
Dec 25 09:54:12 c210-49-92-137 kernel: On node 0 totalpages: 131052
Dec 25 09:54:12 c210-49-92-137 kernel: zone(0): 4096 pages.
Dec 25 09:54:12 c210-49-92-137 kernel: zone(1): 126956 pages.
Dec 25 09:54:12 c210-49-92-137 kernel: zone(2): 0 pages.
Dec 25 09:54:12 c210-49-92-137 kernel: Kernel command line: ro root=LABEL=/ hdb=ide-scsi
Dec 25 09:54:12 c210-49-92-137 kernel: ide_setup: hdb=ide-scsi
Dec 25 09:54:12 c210-49-92-137 kernel: Initializing CPU#0
Dec 25 09:54:12 c210-49-92-137 kernel: Detected 1008.998 MHz processor.
Dec 25 09:54:12 c210-49-92-137 kernel: Console: colour VGA+ 80x25
Dec 25 09:54:12 c210-49-92-137 kernel: Calibrating delay loop... 2011.95 BogoMIPS
Dec 25 09:54:12 c210-49-92-137 syslog: klogd startup succeeded
Dec 25 09:54:12 c210-49-92-137 kernel: Memory: 511384k/524208k available (1312k kernel code, 10260k reserved, 996k data, 128k init, 0k highmem)
Dec 25 09:54:12 c210-49-92-137 kernel: Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Dec 25 09:54:12 c210-49-92-137 kernel: Inode cache hash table entries: 32768 (order: 6, 262144 bytes)
Dec 25 09:54:12 c210-49-92-137 kernel: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Dec 25 09:54:12 c210-49-92-137 portmap: portmap startup succeeded
Dec 25 09:54:12 c210-49-92-137 kernel: Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes)
Dec 25 09:54:12 c210-49-92-137 kernel: Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
Dec 25 09:54:12 c210-49-92-137 nfslock: rpc.statd startup succeeded
Dec 25 09:54:12 c210-49-92-137 rpc.statd[3010]: Version 1.0.1 Starting
Dec 25 09:54:12 c210-49-92-137 kernel: CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
Dec 25 09:54:12 c210-49-92-137 keytable:
Dec 25 09:54:13 c210-49-92-137 kernel: CPU: L2 Cache: 256K (64 bytes/line)
Dec 25 09:54:13 c210-49-92-137 keytable: Loading system font:
Dec 25 09:54:13 c210-49-92-137 kernel: Intel machine check architecture supported.
Dec 25 09:54:13 c210-49-92-137 kernel: Intel machine check reporting enabled on CPU#0.
Dec 25 09:54:13 c210-49-92-137 kernel: CPU: AMD Athlon(tm) Processor stepping 04
Dec 25 09:54:13 c210-49-92-137 kernel: Enabling fast FPU save and restore... done.
Dec 25 09:54:13 c210-49-92-137 kernel: Checking 'hlt' instruction... OK.
Dec 25 09:54:13 c210-49-92-137 kernel: POSIX conformance testing by UNIFIX
Dec 25 09:54:13 c210-49-92-137 kernel: mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
Dec 25 09:54:13 c210-49-92-137 kernel: mtrr: detected mtrr type: Intel
Dec 25 09:54:13 c210-49-92-137 kernel: PCI: PCI BIOS revision 2.10 entry at 0xf1150, last bus=1
Dec 25 09:54:13 c210-49-92-137 kernel: PCI: Using configuration type 1
Dec 25 09:54:13 c210-49-92-137 kernel: PCI: Probing PCI hardware
Dec 25 09:54:13 c210-49-92-137 kernel: PCI: Using IRQ router VIA [1106/0686] at 00:04.0
Dec 25 09:54:13 c210-49-92-137 kernel: Applying VIA southbridge workaround.
Dec 25 09:54:13 c210-49-92-137 kernel: isapnp: Scanning for PnP cards...
Dec 25 09:54:13 c210-49-92-137 kernel: isapnp: No Plug & Play device found
Dec 25 09:54:13 c210-49-92-137 kernel: Linux NET4.0 for Linux 2.4
Dec 25 09:54:13 c210-49-92-137 kernel: Based upon Swansea University Computer Society NET3.039
Dec 25 09:54:13 c210-49-92-137 keytable:
Dec 25 09:54:13 c210-49-92-137 kernel: Initializing RT netlink socket
Dec 25 09:54:13 c210-49-92-137 rc: Starting keytable: succeeded
Dec 25 09:54:13 c210-49-92-137 kernel: apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)
Dec 25 09:54:13 c210-49-92-137 kernel: Starting kswapd
Dec 25 09:54:13 c210-49-92-137 kernel: VFS: Disk quotas vdquot_6.5.1
Dec 25 09:54:13 c210-49-92-137 kernel: pty: 2048 Unix98 ptys configured
Dec 25 09:54:13 c210-49-92-137 kernel: Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI ISAPNP enabled
Dec 25 09:54:13 c210-49-92-137 kernel: ttyS0 at 0x03f8 (irq = 4) is a 16550A
Dec 25 09:54:13 c210-49-92-137 kernel: ttyS1 at 0x02f8 (irq = 3) is a 16550A
Dec 25 09:54:13 c210-49-92-137 kernel: Real Time Clock Driver v1.10e
Dec 25 09:54:13 c210-49-92-137 kernel: Floppy drive(s): fd0 is 1.44M
Dec 25 09:54:13 c210-49-92-137 kernel: FDC 0 is a post-1991 82077
Dec 25 09:54:13 c210-49-92-137 kernel: NET4: Frame Diverter 0.46
Dec 25 09:54:13 c210-49-92-137 kernel: RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Dec 25 09:54:13 c210-49-92-137 kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00beta-2.4
Dec 25 09:54:13 c210-49-92-137 kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Dec 25 09:54:13 c210-49-92-137 kernel: VP_IDE: IDE controller at PCI slot 00:04.1
Dec 25 09:54:13 c210-49-92-137 kernel: VP_IDE: chipset revision 6
Dec 25 09:54:13 c210-49-92-137 random: Initializing random number generator: succeeded
Dec 25 09:54:13 c210-49-92-137 kernel: VP_IDE: not 100%% native mode: will probe irqs later
Dec 25 09:54:13 c210-49-92-137 kernel: VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:04.1
Dec 25 09:54:13 c210-49-92-137 kernel: ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA
Dec 25 09:54:13 c210-49-92-137 rc: Starting pcmcia: succeeded
Dec 25 09:54:13 c210-49-92-137 kernel: ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:DMA
Dec 25 09:54:13 c210-49-92-137 kernel: hda: QUANTUM FIREBALL EX6.4A, ATA DISK drive
Dec 25 09:54:13 c210-49-92-137 kernel: hdb: LITE-ON LTR-52246S, ATAPI CD/DVD-ROM drive
Dec 25 09:54:13 c210-49-92-137 kernel: blk: queue c03be900, I/O limit 4095Mb (mask 0xffffffff)
Dec 25 09:54:13 c210-49-92-137 kernel: hdc: QUANTUM FIREBALLP LM20.5, ATA DISK drive
Dec 25 09:54:13 c210-49-92-137 kernel: hdd: ST380023A, ATA DISK drive
Dec 25 09:54:13 c210-49-92-137 kernel: blk: queue c03bed60, I/O limit 4095Mb (mask 0xffffffff)
Dec 25 09:54:13 c210-49-92-137 kernel: blk: queue c03beea4, I/O limit 4095Mb (mask 0xffffffff)
Dec 25 09:54:13 c210-49-92-137 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Dec 25 09:54:13 c210-49-92-137 kernel: ide1 at 0x170-0x177,0x376 on irq 15
Dec 25 09:54:13 c210-49-92-137 kernel: hda: host protected area => 1
Dec 25 09:54:13 c210-49-92-137 kernel: hda: 12594960 sectors (6449 MB) w/418KiB Cache, CHS=784/255/63, UDMA(33)
Dec 25 09:54:13 c210-49-92-137 kernel: hdc: host protected area => 1
Dec 25 09:54:13 c210-49-92-137 kernel: hdc: 40132503 sectors (20548 MB) w/1900KiB Cache, CHS=39813/16/63, UDMA(66)
Dec 25 09:54:13 c210-49-92-137 kernel: hdd: host protected area => 1
Dec 25 09:54:13 c210-49-92-137 kernel: hdd: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=155061/16/63, UDMA(100)
Dec 25 09:54:13 c210-49-92-137 kernel: ide-floppy driver 0.99.newide
Dec 25 09:54:13 c210-49-92-137 kernel: Partition check:
Dec 25 09:54:13 c210-49-92-137 kernel: hda:<4>hda: dma_timer_expiry: dma status == 0x61
Dec 25 09:54:13 c210-49-92-137 kernel: hda: timeout waiting for DMA
Dec 25 09:54:13 c210-49-92-137 kernel: hda: timeout waiting for DMA
Dec 25 09:54:13 c210-49-92-137 kernel: hda: (__ide_dma_test_irq) called while not waiting
Dec 25 09:54:13 c210-49-92-137 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 25 09:54:13 c210-49-92-137 kernel:
Dec 25 09:54:13 c210-49-92-137 kernel: hda: drive not ready for command
Dec 25 09:54:13 c210-49-92-137 kernel: blk: queue c03be900, I/O limit 4095Mb (mask 0xffffffff)
Dec 25 09:54:13 c210-49-92-137 kernel: hda1 hda2 <<4>hda: dma_timer_expiry: dma status == 0x61
Dec 25 09:54:13 c210-49-92-137 kernel: hda: timeout waiting for DMA
Dec 25 09:54:13 c210-49-92-137 kernel: hda: timeout waiting for DMA
Dec 25 09:54:13 c210-49-92-137 kernel: hda: (__ide_dma_test_irq) called while not waiting
Dec 25 09:54:13 c210-49-92-137 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 25 09:54:13 c210-49-92-137 kernel:
Dec 25 09:54:13 c210-49-92-137 kernel: hda: drive not ready for command
Dec 25 09:54:13 c210-49-92-137 kernel: hda5<4>hda: dma_timer_expiry: dma status == 0x61
Dec 25 09:54:13 c210-49-92-137 kernel: hda: timeout waiting for DMA
Dec 25 09:54:13 c210-49-92-137 kernel: hda: timeout waiting for DMA
Dec 25 09:54:13 c210-49-92-137 kernel: hda: (__ide_dma_test_irq) called while not waiting
Dec 25 09:54:13 c210-49-92-137 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 25 09:54:13 c210-49-92-137 kernel:
Dec 25 09:54:13 c210-49-92-137 kernel: hda: drive not ready for command
Dec 25 09:54:13 c210-49-92-137 kernel: hda6<4>hda: dma_timer_expiry: dma status == 0x61
Dec 25 09:54:13 c210-49-92-137 kernel: hda: timeout waiting for DMA
Dec 25 09:54:13 c210-49-92-137 kernel: hda: timeout waiting for DMA
Dec 25 09:54:13 c210-49-92-137 kernel: hda: (__ide_dma_test_irq) called while not waiting
Dec 25 09:54:13 c210-49-92-137 kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 25 09:54:13 c210-49-92-137 kernel:
Dec 25 09:54:13 c210-49-92-137 kernel: hda: drive not ready for command
Dec 25 09:54:13 c210-49-92-137 kernel: hda7 >
Dec 25 09:54:13 c210-49-92-137 kernel: hdc: [PTBL] [2498/255/63] hdc1 hdc2 < >
Dec 25 09:54:13 c210-49-92-137 kernel: hdd: [PTBL] [9729/255/63] hdd1 hdd2 hdd3 hdd4 < hdd5 >


it is this above part that seems to be pointless?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Dec 25 09:54:13 c210-49-92-137 kernel: ide-floppy driver 0.99.newide
Dec 25 09:54:13 c210-49-92-137 kernel: md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
Dec 25 09:54:13 c210-49-92-137 kernel: md: Autodetecting RAID arrays.
Dec 25 09:54:13 c210-49-92-137 kernel: md: autorun ...
Dec 25 09:54:13 c210-49-92-137 kernel: md: ... autorun DONE.
Dec 25 09:54:13 c210-49-92-137 kernel: NET4: Linux TCP/IP 1.0 for NET4.0
Dec 25 09:54:13 c210-49-92-137 kernel: IP Protocols: ICMP, UDP, TCP, IGMP
Dec 25 09:54:13 c210-49-92-137 kernel: IP: routing cache hash table of 4096 buckets, 32Kbytes
Dec 25 09:54:13 c210-49-92-137 kernel: TCP: Hash tables configured (established 32768 bind 65536)
Dec 25 09:54:13 c210-49-92-137 kernel: Linux IP multicast router 0.06 plus PIM-SM
Dec 25 09:54:13 c210-49-92-137 kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Dec 25 09:54:13 c210-49-92-137 kernel: RAMDISK: Compressed image found at block 0
Dec 25 09:54:13 c210-49-92-137 kernel: Freeing initrd memory: 146k freed
Dec 25 09:54:13 c210-49-92-137 kernel: VFS: Mounted root (ext2 filesystem).
Dec 25 09:54:13 c210-49-92-137 kernel: Journalled Block Device driver loaded
Dec 25 09:54:13 c210-49-92-137 kernel: kjournald starting. Commit interval 5 seconds
Dec 25 09:54:13 c210-49-92-137 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Dec 25 09:54:13 c210-49-92-137 kernel: Freeing unused kernel memory: 128k freed
Dec 25 09:54:13 c210-49-92-137 kernel: usb.c: registered new driver usbdevfs
Dec 25 09:54:13 c210-49-92-137 kernel: usb.c: registered new driver hub
Dec 25 09:54:13 c210-49-92-137 kernel: usb-uhci.c: $Revision: 1.275 $ time 17:26:20 Mar 13 2003
Dec 25 09:54:13 c210-49-92-137 kernel: usb-uhci.c: High bandwidth mode enabled
Dec 25 09:54:13 c210-49-92-137 kernel: PCI: Found IRQ 9 for device 00:04.2
Dec 25 09:54:13 c210-49-92-137 kernel: PCI: Sharing IRQ 9 with 00:04.3
Dec 25 09:54:13 c210-49-92-137 kernel: PCI: Sharing IRQ 9 with 00:09.0
Dec 25 09:54:13 c210-49-92-137 kernel: usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 9
Dec 25 09:54:13 c210-49-92-137 kernel: usb-uhci.c: Detected 2 ports
Dec 25 09:54:13 c210-49-92-137 kernel: usb.c: new USB bus registered, assigned bus number 1
Dec 25 09:54:13 c210-49-92-137 kernel: hub.c: USB hub found
Dec 25 09:54:13 c210-49-92-137 kernel: hub.c: 2 ports detected
Dec 25 09:54:13 c210-49-92-137 kernel: PCI: Found IRQ 9 for device 00:04.3
Dec 25 09:54:13 c210-49-92-137 kernel: PCI: Sharing IRQ 9 with 00:04.2
Dec 25 09:54:13 c210-49-92-137 kernel: PCI: Sharing IRQ 9 with 00:09.0
Dec 25 09:54:13 c210-49-92-137 kernel: usb-uhci.c: USB UHCI at I/O 0xd000, IRQ 9
Dec 25 09:54:13 c210-49-92-137 kernel: usb-uhci.c: Detected 2 ports
Dec 25 09:54:13 c210-49-92-137 kernel: usb.c: new USB bus registered, assigned bus number 2
Dec 25 09:54:13 c210-49-92-137 kernel: hub.c: USB hub found
Dec 25 09:54:13 c210-49-92-137 kernel: hub.c: 2 ports detected
Dec 25 09:54:13 c210-49-92-137 kernel: usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
Dec 25 09:54:13 c210-49-92-137 kernel: usb.c: registered new driver hiddev
Dec 25 09:54:13 c210-49-92-137 kernel: usb.c: registered new driver hid
Dec 25 09:54:13 c210-49-92-137 kernel: hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
Dec 25 09:54:13 c210-49-92-137 kernel: hid-core.c: USB HID support drivers
Dec 25 09:54:13 c210-49-92-137 kernel: mice: PS/2 mouse device common for all mice
Dec 25 09:54:13 c210-49-92-137 kernel: hub.c: new USB device 00:04.2-2, assigned address 2
Dec 25 09:54:13 c210-49-92-137 kernel: usb-uhci.c: interrupt, status 3, frame# 634
Dec 25 09:54:13 c210-49-92-137 kernel: input0: USB HID v1.10 Mouse [Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)] on usb1:2.0
Dec 25 09:54:13 c210-49-92-137 kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,67), internal journal
Dec 25 09:54:13 c210-49-92-137 kernel: Adding Swap: 1044184k swap-space (priority -1)
Dec 25 09:54:13 c210-49-92-137 kernel: hub.c: new USB device 00:04.3-2, assigned address 2
Dec 25 09:54:13 c210-49-92-137 kernel: usb.c: USB device 2 (vend/prod 0x46d/0xd001) is not claimed by any active driver.
Dec 25 09:54:13 c210-49-92-137 kernel: kjournald starting. Commit interval 5 seconds
Dec 25 09:54:13 c210-49-92-137 kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,66), internal journal
Dec 25 09:54:13 c210-49-92-137 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Dec 25 09:54:13 c210-49-92-137 kernel: SCSI subsystem driver Revision: 1.00
Dec 25 09:54:13 c210-49-92-137 kernel: scsi0 : SCSI host adapter emulation for IDE ATAPI devices
Dec 25 09:54:13 c210-49-92-137 kernel: Vendor: LITE-ON Model: LTR-52246S Rev: 6S02
Dec 25 09:54:13 c210-49-92-137 kernel: Type: CD-ROM ANSI SCSI revision: 02
Dec 25 09:54:13 c210-49-92-137 kernel: parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
Dec 25 09:54:13 c210-49-92-137 kernel: parport0: Printer, Lexmark Lexmark 5700
Dec 25 09:54:13 c210-49-92-137 kernel: parport_pc: Via 686A parallel port: io=0x378
Dec 25 09:54:13 c210-49-92-137 kernel: Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
Dec 25 09:54:13 c210-49-92-137 kernel: sr0: scsi3-mmc drive: 52x/52x writer cd/rw xa/form2 cdda tray
Dec 25 09:54:13 c210-49-92-137 kernel: Uniform CD-ROM driver Revision: 3.12
Dec 25 09:54:13 c210-49-92-137 kernel: ip_tables: (C) 2000-2002 Netfilter core team
Dec 25 09:54:13 c210-49-92-137 kernel: ne2k-pci.c:v1.02 10/19/2000 D. Becker/P. Gortmaker
Dec 25 09:54:13 c210-49-92-137 kernel: http://www.scyld.com/network/ne2k-pci.html
Dec 25 09:54:13 c210-49-92-137 kernel: PCI: Found IRQ 9 for device 00:09.0
Dec 25 09:54:13 c210-49-92-137 kernel: PCI: Sharing IRQ 9 with 00:04.2
Dec 25 09:54:13 c210-49-92-137 kernel: PCI: Sharing IRQ 9 with 00:04.3
Dec 25 09:54:13 c210-49-92-137 kernel: eth0: RealTek RTL-8029 found at 0xa400, IRQ 9, 00:C0:26:E0:FF:FF.
Dec 25 09:54:13 c210-49-92-137 netfs: Mounting other filesystems: succeeded
Dec 25 09:54:13 c210-49-92-137 apmd[3077]: Version 3.0.2 (APM BIOS 1.2, Linux driver 1.16)
Dec 25 09:54:13 c210-49-92-137 apmd: apmd startup succeeded
Dec 25 09:54:13 c210-49-92-137 autofs: automount startup succeeded
Dec 25 09:54:10 c210-49-92-137 sysctl: net.ipv4.ip_forward = 0
Dec 25 09:54:10 c210-49-92-137 sysctl: net.ipv4.conf.default.rp_filter = 1
Dec 25 09:54:10 c210-49-92-137 sysctl: kernel.sysrq = 0
Dec 25 09:54:10 c210-49-92-137 sysctl: kernel.core_uses_pid = 1
Dec 25 09:54:10 c210-49-92-137 network: Setting network parameters: succeeded
Dec 25 09:54:10 c210-49-92-137 network: Bringing up loopback interface: succeeded
Dec 25 09:54:10 c210-49-92-137 ifup:
Dec 25 09:54:10 c210-49-92-137 ifup: Determining IP information for eth0...
Dec 25 09:54:12 c210-49-92-137 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Dec 25 09:54:12 c210-49-92-137 dhclient: bound to 210.49.92.137 -- renewal in 33393 seconds.
Dec 25 09:54:14 c210-49-92-137 sshd: succeeded
Dec 25 09:54:14 c210-49-92-137 apmd[3077]: Charge: * * * (-1% unknown)
Dec 25 09:54:15 c210-49-92-137 xinetd[3128]: xinetd Version 2.3.10 started with libwrap options compiled in.
Dec 25 09:54:15 c210-49-92-137 xinetd[3128]: Started working: 1 available service
Dec 25 09:54:17 c210-49-92-137 xinetd: xinetd startup succeeded
Dec 25 09:54:18 c210-49-92-137 sendmail: sendmail startup succeeded
Dec 25 09:54:18 c210-49-92-137 sendmail: sm-client startup succeeded
Dec 25 09:54:18 c210-49-92-137 gpm: gpm startup succeeded
Dec 25 09:54:19 c210-49-92-137 crond: crond startup succeeded
Dec 25 09:54:21 c210-49-92-137 kernel: parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
Dec 25 09:54:21 c210-49-92-137 kernel: parport0: Printer, Lexmark Lexmark 5700
Dec 25 09:54:21 c210-49-92-137 kernel: parport_pc: Via 686A parallel port: io=0x378
Dec 25 09:54:21 c210-49-92-137 kernel: lp0: using parport0 (polling).
Dec 25 09:54:21 c210-49-92-137 kernel: lp0: console ready
Dec 25 09:54:21 c210-49-92-137 modprobe: modprobe: Can't locate module char-major-188
Dec 25 09:54:21 c210-49-92-137 last message repeated 15 times
Dec 25 09:54:21 c210-49-92-137 cups: cupsd startup succeeded
Dec 25 09:54:22 c210-49-92-137 xfs: xfs startup succeeded
Dec 25 09:54:22 c210-49-92-137 anacron: anacron startup succeeded
Dec 25 09:54:22 c210-49-92-137 atd: atd startup succeeded
Dec 25 09:54:22 c210-49-92-137 wine: Registering binary handler for Windows applications
Dec 25 09:54:22 c210-49-92-137 rc: Starting wine: succeeded
Dec 25 09:54:22 c210-49-92-137 xfs: ignoring font path element /usr/X11R6/lib/X11/fonts/cyrillic (unreadable)
Dec 25 09:54:25 c210-49-92-137 kernel: 0: nvidia: loading NVIDIA Linux x86 nvidia.o Kernel Module 1.0-5328 Wed Dec 17 13:54:51 PST 2003
Dec 25 09:54:25 c210-49-92-137 insmod: Warning: loading /lib/modules/2.4.20-8/kernel/drivers/video/nvidia.o will taint the kernel: non-GPL license - NVIDIA
Dec 25 09:54:25 c210-49-92-137 insmod: See http://www.tux.org/lkml/#export-tainted for information about tainted modules
Dec 25 09:54:25 c210-49-92-137 insmod: Module nvidia loaded, with warnings
Dec 25 09:54:27 c210-49-92-137 kernel: Linux agpgart interface v0.99 (c) Jeff Hartmann
Dec 25 09:54:27 c210-49-92-137 kernel: agpgart: Maximum main memory to use for agp memory: 439M
Dec 25 09:54:27 c210-49-92-137 kernel: agpgart: Detected Via Apollo Pro KT133 chipset
Dec 25 09:54:27 c210-49-92-137 kernel: agpgart: AGP aperture is 32M @ 0xe6000000
Dec 25 09:54:37 c210-49-92-137 gdm(pam_unix)[3331]: session opened for user razgo by (uid=0)
Dec 25 09:54:39 c210-49-92-137 gconfd (razgo-3391): starting (version 2.2.0), pid 3391 user 'razgo'
Dec 25 09:54:39 c210-49-92-137 gconfd (razgo-3391): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0
Dec 25 09:54:39 c210-49-92-137 gconfd (razgo-3391): Resolved address "xml:readwrite:/home/razgo/.gconf" to a writable config source at position 1
Dec 25 09:54:39 c210-49-92-137 gconfd (razgo-3391): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Dec 25 09:55:48 c210-49-92-137 userhelper: pam_timestamp: timestamp file `/var/run/sudo/razgo/unknown:root' is only 33 seconds old, allowing access to redhat-logviewer for UID 500
 
Old 12-24-2003, 06:30 PM   #8
Technoslave
Member
 
Registered: Dec 2003
Location: Northern VA
Posts: 493

Rep: Reputation: 30
I think some people are confusing when linux is in it's boot up procedures ( all the OK s that go by ) and when the machine FIRST boots up and scans hard drives for boot partitions.

From the descriptions Razgo is mentioning, he is talking about the latter.

The answer to this is that there really isn't any, short of making sure that your linux is the very first thing on the first disk, and even then, that's no guarntee that this "searching" you're speaking of will either lessen in length or go away totally.

By the by, what's the length of time we're talking here?
 
Old 12-24-2003, 06:44 PM   #9
Razgo
Member
 
Registered: Dec 2003
Location: Australia-Brisbane
Distribution: RHEL WS basic edition-gnome
Posts: 40

Original Poster
Rep: Reputation: 15
it takes 2:08 min/s to get to the screen where it says welcome to redhat linux intereactive startup. then it takes another 56 sec's to get to the log in promt, totalling a total of 3:04 min/s.

the boot process with all the ok's is where i thought it would boot straight too, instead of all the other scanning hardrives/partitions process.


Last edited by Razgo; 12-24-2003 at 06:46 PM.
 
Old 12-26-2003, 04:40 PM   #10
Mara
Moderator
 
Registered: Feb 2002
Location: Grenoble
Distribution: Debian
Posts: 9,696

Rep: Reputation: 232Reputation: 232Reputation: 232
There are errors on hda (the end of first part of logs). It results in delay.
Razgo, do you have an idea what may be wrong with the disk (primary master)?
 
Old 12-27-2003, 05:41 AM   #11
C Scott
LQ Newbie
 
Registered: Dec 2003
Location: Nashville, TN
Distribution: Mandrake 9.2 Enterprise Download
Posts: 12

Rep: Reputation: 0
Try turning off dma support in your kernel and see if that helps.

Last edited by C Scott; 12-27-2003 at 05:52 AM.
 
Old 12-27-2003, 06:56 AM   #12
Razgo
Member
 
Registered: Dec 2003
Location: Australia-Brisbane
Distribution: RHEL WS basic edition-gnome
Posts: 40

Original Poster
Rep: Reputation: 15
if i access kernal tuning i don't see an option for turning off dma support. how do i do this?
 
Old 12-28-2003, 06:03 AM   #13
C Scott
LQ Newbie
 
Registered: Dec 2003
Location: Nashville, TN
Distribution: Mandrake 9.2 Enterprise Download
Posts: 12

Rep: Reputation: 0
Quote:
Originally posted by Razgo
if i access kernal tuning i don't see an option for turning off dma support. how do i do this?
Type "ide=nodma" (without the quotes of course) in your boot menu. Then check your boot or system log to see if it helps.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Suse Linux 9.1 Pro: boot hang on "scanning pci..." paulsm4 Linux - Software 1 11-16-2004 02:54 PM
will linux ever see decent scanning support ? qwijibow Linux - Hardware 2 02-29-2004 09:38 PM
linux scanning software Aerlock Linux - Software 1 10-23-2003 03:51 PM
Scanning Linux from windows M$ISBS Linux - Security 1 09-16-2003 09:23 PM
Scanning sistem on boot?!? caphclimber Linux - Software 4 09-03-2003 06:28 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 01:04 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration