[5.800] Slow Boot

ok im getting a few things. It takes 20 minutes to boot. the remounting drives readwrite is where it slows down. after its booted its fast again. Ill look into that.

Parents

0 William Warren over 20 years ago

what hardware is this running on?

Owner: Emmanuel Technology Consulting

http://etc-md.com

Former Sophos SG(Astaro) advocate/researcher/Silver Partner

PfSense w/Suricata, ntopng,

Other addons to follow
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Xeno over 20 years ago in reply to William Warren

Is that during file system check? Do you use SATA in legacy mode? Do you use Raid? Which hardware?

Xeno
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Dave Packham over 20 years ago in reply to Xeno

it starts during the disk checking and does not speed up until the system is at the login prompt. they arfe generic ATA drives nothing special. v5 worked fine on this box, so im guessing its a 2.6 kernel issue.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 William Warren over 20 years ago in reply to Dave Packham

[ QUOTE ]
it starts during the disk checking and does not speed up until the system is at the login prompt. they arfe generic ATA drives nothing special. v5 worked fine on this box, so im guessing its a 2.6 kernel issue.

[/ QUOTE ]
cpu type and speed, ram type and amount, nics, hdd model(speed(rpm) capacity), etc etc would be helpful.

Owner: Emmanuel Technology Consulting

http://etc-md.com

Former Sophos SG(Astaro) advocate/researcher/Silver Partner

PfSense w/Suricata, ntopng,

Other addons to follow
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Dave Packham over 20 years ago in reply to William Warren

its a Shuttle XPS SS51G with a 1.7 ghz P4 512 ram 80 gig ATA 100 Drive. I have disabled the Serial/USB/Printer/Sound to open up IRQ's is there a way to print out a debug config right from the firewall?

Dave P
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 William Warren over 20 years ago in reply to Dave Packham

Sounds like the sis 651 chipset may not be properly suported for DMA and that could be killing your disk performace. Is the SIS651 on the HCL?

Also after it starts its i'm done beeping...go into ssh and run top and see what the load averages are.

You could try hdparm(if it is included in ASL^) to see if you are getting proper disk performance.

Owner: Emmanuel Technology Consulting

http://etc-md.com

Former Sophos SG(Astaro) advocate/researcher/Silver Partner

PfSense w/Suricata, ntopng,

Other addons to follow
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Dave Packham over 20 years ago in reply to William Warren

OK will do. the funny thing that I notice is that after the beeps its fast again. ill look into the chipset. and the hdparms and top reports

Thanks
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Xeno over 20 years ago in reply to Dave Packham

If slow harddisk is the problem you can check the harddisk by simply write onto it. The following command writes data to a file as fast as possible:
cat /dev/zero > testfile
Let it run for 2 or 3 seconds then kill it with Control+C. Look at the size of the file. It should be at least 50 MB in size. Then your harddisk should be fast enough. Also you can try to disable DMA by executing 'hdparm -d 0 /dev/'

Xeno
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 William Warren over 20 years ago in reply to Xeno

[ QUOTE ]
If slow harddisk is the problem you can check the harddisk by simply write onto it. The following command writes data to a file as fast as possible:
cat /dev/zero > testfile
Let it run for 2 or 3 seconds then kill it with Control+C. Look at the size of the file. It should be at least 50 MB in size. Then your harddisk should be fast enough. Also you can try to disable DMA by executing 'hdparm -d 0 /dev/'

Xeno

[/ QUOTE ]
heck no..i would advise against disabling dma.

Owner: Emmanuel Technology Consulting

http://etc-md.com

Former Sophos SG(Astaro) advocate/researcher/Silver Partner

PfSense w/Suricata, ntopng,

Other addons to follow
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 William Warren over 20 years ago in reply to Xeno

[ QUOTE ]
If slow harddisk is the problem you can check the harddisk by simply write onto it. The following command writes data to a file as fast as possible:
cat /dev/zero > testfile
Let it run for 2 or 3 seconds then kill it with Control+C. Look at the size of the file. It should be at least 50 MB in size. Then your harddisk should be fast enough. Also you can try to disable DMA by executing 'hdparm -d 0 /dev/'

Xeno

[/ QUOTE ]
heck no..i would advise against disabling dma.

Owner: Emmanuel Technology Consulting

http://etc-md.com

Former Sophos SG(Astaro) advocate/researcher/Silver Partner

PfSense w/Suricata, ntopng,

Other addons to follow
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 Dave Packham over 20 years ago in reply to William Warren

remember that its only during boot that its slow. after i can login it zippy again like 5.202 used to be. its something during boot that gets undone near the end of the boot process

Dave
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 BarryG over 20 years ago in reply to Dave Packham

I'd guess it's FSCK

ASL usually has it set to run FSCK on every reboot during the beta period.

You might be able to change it with tune2fs or look at the init scripts.

Barry
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Dave Packham over 20 years ago in reply to BarryG

does it take everyone the same time to boot? the disk light is not on during this time and with a fsck i would expect to see that flicker.... I can hook this box up to my web KVM and let someone watch it if they would like to try to see whats up here

Dave P
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Dave Packham over 20 years ago in reply to Dave Packham

remember that with 5.202 it was booted in a about 2-3 minutes not the 20-30 its taking now... same box exactly
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 BarryG over 20 years ago in reply to Dave Packham

Are you using static addressing or DHCP or PPPoE?

Barry
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Dave Packham over 20 years ago in reply to BarryG

Static. the same exact setup as in the 5.202 days nothing changed at all
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Markus Hennig over 20 years ago in reply to Dave Packham

Hi Dave,

thx so far for the report and details!
Can you please post the output of "hdparm /dev/hda" and "hwinfo --disk --bridge"?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 doug_p over 20 years ago in reply to Dave Packham

I'm seeing similar boot times between 5.202 and 6 beta on the same hardware and setup.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 William Warren over 20 years ago in reply to doug_p

What takes forever on v5 is v4watcher and confd. Confd is a cpu hog anyways and apparently takes a long time to intialize at startup.

Owner: Emmanuel Technology Consulting

http://etc-md.com

Former Sophos SG(Astaro) advocate/researcher/Silver Partner

PfSense w/Suricata, ntopng,

Other addons to follow
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Dave Packham over 20 years ago in reply to William Warren

ok I have an identical box here at work that I was using on 5.202 ^ does that same slowdown. Im booting it now and go to lunch. when I get back ill get you the hdparm info. also. FYI the Numlock key keeps flashing during this slow boot period starting at the :: Filesystemcheck and continues to flash until just before the login prompt. something changes at this point and stuff runs fast again. is hdparm getting run in some RC script?

Dave P
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel