Jump to content

Mandriva blocks while booting [solved]


Kieth
 Share

Recommended Posts

  • Replies 44
  • Created
  • Last Reply

Top Posters In This Topic

OK, I did it. From WXP I eliminated all the partitions, then re-installed everything. I got my ati video card working, and now I'm ready again to try and resolve this on going problem of it stopping (about 2 out of 3 bootups) at "Checking root filesystem". First I changed /etc/sysconfig/init to read

 

'# Set to anything other than 'no' to allow hotkey interactive startup...

PROMPT=no'.

 

/etc/sysconfig/init is now:

 

# color => new RH6.0 bootup

# verbose => old-style bootup

# anything else => new style bootup without ANSI colors or positioning

BOOTUP=color

# Turn on graphical boot

GRAPHICAL=yes

# column to start "[ OK ]" label in

RES_COL=65

# terminal sequence to move to that column. You could change this

# to something like "tput hpa ${RES_COL}" if your terminal supports it

MOVE_TO_COL="echo -en \\033[${RES_COL}G"

# terminal sequence to set color to a 'success' color (currently: green)

SETCOLOR_SUCCESS="echo -en \\033[1;32m"

# terminal sequence to set color to a 'failure' color (currently: red)

SETCOLOR_FAILURE="echo -en \\033[1;31m"

# terminal sequence to set color to a 'warning' color (currently: yellow)

SETCOLOR_WARNING="echo -en \\033[1;33m"

# terminal sequence to reset to the default color.

SETCOLOR_NORMAL="echo -en \\033[0;39m"

# default kernel loglevel on boot (syslog will reset this)

LOGLEVEL=3

# Set to anything other than 'no' to allow hotkey interactive startup...

PROMPT=no

# Set to 'yes' to allow probing for devices with swap signatures

AUTOSWAP=no

 

After changing /etc/sysconfig/init, it was still stopping. Therefore I changed the first line of /etc/fstab like scarecrow mentioned. Now it's:

 

/dev/hdb1 / ext3 defaults 0 0

/dev/hdb8 /home ext3 defaults 1 2

/dev/hdc /mnt/cdrom auto umask=0,users,iocharset=utf8,noauto,ro,exec 0 0

none /mnt/floppy supermount dev=/dev/fd0,fs=ext2:vfat,--,umask=0,iocharset=utf8,sync 0 0

/dev/hda1 /mnt/win_c ntfs umask=0,nls=utf8,ro 0 0

/dev/hda5 /mnt/win_d vfat umask=0,iocharset=utf8 0 0

none /proc proc defaults 0 0

/dev/hdb6 /usr ext3 defaults 1 2

/dev/hdb7 /var ext3 defaults 1 2

/dev/hdb5 swap swap defaults 0 0

 

It still stops, though. When it does, I usually have to press the computer's reset button another 2 times for it to boot up. Any ideas that might resolve the problem? Thanks.

Link to comment
Share on other sites

I personally stand by what I said before, you've got a system that has QiLinux underneath it. You need to either delete the partitions and clean install Mandriva, or leave the partitions and *format* then when you reinstall.

 

It seems Mandriva is attempting to do stuff that has been left behind from QiLinux, and hence the error message you're getting about it. And I expect half of this is why you're having the problems now.

 

Never attempt to upgrade or install over the top of a previous distro unless you are going to format the partitions first. This is where I think your problems exist, and suggest you clean install.

Link to comment
Share on other sites

Well, "back to the drawing board". There must be something I didn't understand that I should have done, or something I could have done better. I thought I did everything you mentioned. When I originally installed, I formated everything but /home. Then this weekend, from WXP, I deleted all the partitions. While I was at it, I also deleted one of my ntfs partitions. Anyway, after that, I re-installed Mandriva, making new partitions and formatting them all. I have 2 disks, 80 GB each. One has only linux and the other has WXP. On the WXP disk, I have a ntfs partition and a fat32 partition (for swapping files to and from linux). I don't remember, but I don't think I deleted or formated the fat32 partition. I mention it because I do not know if the problem could be coming from there. Did I miss something? From WXP, should I delete all the partitions again, re-formatting them (all from WXP) and re-install again? If need be, I'll do it again, afterall, it's a real "pain in the neck" having my system stop all the time while booting. Thanks.

Link to comment
Share on other sites

It's always at the root partition, although it also stops at: 'Waiting for network to be up [failed]'. It waits for a few seconds (10?), then goes on. Then it also looks for something else (I forget what), and then 'fails', and goes on. The next time I boot up, I'll write it down. It only hesitates a moment or 2, though.

Link to comment
Share on other sites

OK, I was able to write it down. I had to start my computer several times to get it, since it goes by so fast. As I mentioned, it stops at:

 

Waiting for network to be up [failed]

 

Here it waits for about 10 seconds. Then it stops at:

 

Looking for host 0.it.pool.ntp.org and service ntp [failed]

Looking for host 1.it.pool.ntp.org and service ntp [failed]

Looking for host 2.it.pool.ntp.org and service ntp [failed]

 

Here it does wait at all, but comes and goes fast.

 

You mentioned a dhcp connection. I have a an adsl modem, and I connect by way of pppoe, from the command line: adsl-start. I also just checked MCC, and of course there is also an eth0 connection. The portocol is DHCP. There is not netmask or IP address. The dhcp client is dhclient. Two boxes are checked: Assign host name from DHCP address, and Get DNS servers from DHCP. The option is to start at boot. Network hotplugging is not marked.

Edited by Kieth
Link to comment
Share on other sites

While booting up this time, I noticed that I did not get everything written down where it "fails". It goes by so fast it's hard to get it. Is there a record of the boot sequence somewhere that I can just go to and copy? Otherwise I don't know if I'll be able to get it all.

Link to comment
Share on other sites

Reading a post where ian was helping someone else, he said to use the command less /var/log/messages to get some information. I did and here's the result. Does it mean anything to someone (it doesn't to me :woops: )?

 

 

Nov 21 15:50:34 localhost kernel: via-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald Becker

Nov 21 15:50:34 localhost kernel: ACPI: PCI Interrupt 0000:00:12.0[A] -> GSI 23 (level, low) -> IRQ 20

Nov 21 15:50:34 localhost kernel: eth0: VIA Rhine II at 0x1a000, 00:13:d4:8c:3a:57, IRQ 20.

Nov 21 15:50:34 localhost kernel: eth0: MII PHY found at address 1, status 0x786d advertising 01e1 Link 0021.

Nov 21 15:50:35 localhost ifplugd(eth0)[2513]: ifplugd 0.28 initializing.

Nov 21 15:50:35 localhost kernel: eth0: link up, 10Mbps, half-duplex, lpa 0x0021

Nov 21 15:50:35 localhost ifplugd(eth0)[2513]: Using interface eth0/00:13:D4:8C:3A:57 with driver <via-rhine> (

version: 1.2.0-2.6)

Nov 21 15:50:35 localhost ifplugd(eth0)[2513]: Using detection mode: SIOCETHTOOL

Nov 21 15:50:35 localhost ifplugd(eth0)[2513]: Initialization complete, link beat detected.

Nov 21 15:50:35 localhost ifplugd(eth0)[2513]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.

Nov 21 15:50:36 localhost kernel: Floppy drive(s): fd0 is 1.44M

Nov 21 15:50:36 localhost kernel: FDC 0 is a post-1991 82077

Nov 21 15:50:36 localhost kernel: end_request: I/O error, dev fd0, sector 0

Nov 21 15:50:38 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7

Nov 21 15:50:45 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13

Nov 21 15:50:58 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8

Nov 21 15:50:58 localhost ntpdate[3789]: can't find host 0.it.pool.ntp.org

Nov 21 15:50:58 localhost ntpdate[3789]: can't find host 1.it.pool.ntp.org

Nov 21 15:50:58 localhost ntpdate[3789]: can't find host 2.it.pool.ntp.org

Nov 21 15:50:58 localhost ntpdate[3789]: no servers can be used, exiting

Nov 21 15:50:58 localhost ntpd[3807]: ntpd 4.2.0@1.1161-r Sat Sep 30 08:42:47 MDT 2006 (1)

Nov 21 15:50:58 localhost avahi-daemon[3842]: Found user 'avahi' (UID 72) and group 'avahi' (GID 72).

Nov 21 15:50:58 localhost avahi-daemon[3842]: Successfully dropped root privileges.

Nov 21 15:50:58 localhost avahi-daemon[3842]: avahi-daemon 0.6.13 starting up.

Link to comment
Share on other sites

Does your adsl modem connect to your ethernet card? Or is it USB? If so, we can disable the eth0 unless the modem is connected to it.

 

Also, post a list of your services, so I can tell you what we can disable. Do:

 

chkconfig --list

 

as root (after an su), and then post here, and I can tell you which services we can disable safely.

Link to comment
Share on other sites

My modem is connected to a card - it's not USB.

 

# chkconfig --list

acpi 0:off 1:off 2:on 3:on 4:on 5:on 6:off

acpid 0:off 1:off 2:off 3:on 4:on 5:on 6:off

alsa 0:off 1:off 2:on 3:on 4:on 5:on 6:off

atd 0:off 1:off 2:off 3:on 4:on 5:on 6:off

atieventsd 0:off 1:off 2:on 3:on 4:on 5:on 6:off

avahi-daemon 0:off 1:off 2:off 3:on 4:off 5:on 6:off

clamd 0:off 1:off 2:on 3:on 4:on 5:on 6:off

crond 0:off 1:off 2:on 3:on 4:on 5:on 6:off

cups 0:off 1:off 2:on 3:on 4:on 5:on 6:off

dkms 0:off 1:off 2:off 3:on 4:on 5:on 6:off

dm 0:off 1:off 2:off 3:off 4:off 5:on 6:off

freshclam 0:off 1:off 2:on 3:on 4:on 5:on 6:off

haldaemon 0:off 1:off 2:off 3:on 4:on 5:on 6:off

harddrake 0:off 1:off 2:off 3:off 4:off 5:off 6:off

hplip 0:off 1:off 2:on 3:on 4:on 5:on 6:off

keytable 0:off 1:off 2:on 3:on 4:on 5:on 6:off

kheader 0:off 1:off 2:on 3:on 4:off 5:on 6:off

lisa 0:off 1:off 2:off 3:on 4:on 5:on 6:off

messagebus 0:off 1:off 2:off 3:on 4:on 5:on 6:off

mtink 0:off 1:off 2:off 3:off 4:off 5:off 6:off

netfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off

network 0:off 1:off 2:on 3:on 4:on 5:on 6:off

network-up 0:off 1:off 2:on 3:on 4:on 5:on 6:off

ntpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off

numlock 0:off 1:off 2:off 3:on 4:on 5:on 6:off

oki4daemon 0:off 1:off 2:off 3:off 4:off 5:off 6:off

partmon 0:off 1:off 2:off 3:on 4:on 5:on 6:off

pppoe 0:off 1:off 2:off 3:off 4:off 5:off 6:off

sound 0:off 1:off 2:on 3:on 4:on 5:on 6:off

syslog 0:off 1:off 2:on 3:on 4:on 5:on 6:off

wltool 0:off 1:off 2:on 3:on 4:on 5:on 6:off

xfs 0:off 1:off 2:on 3:on 4:on 5:on 6:off

xinetd 0:off 1:off 2:off 3:on 4:on 5:on 6:off

 

xinetd based services:

cups-lpd: off

cvs: off

rsync: off

Link to comment
Share on other sites

atd 0:off 1:off 2:off 3:on 4:on 5:on 6:off

atieventsd 0:off 1:off 2:on 3:on 4:on 5:on 6:off

avahi-daemon 0:off 1:off 2:off 3:on 4:off 5:on 6:off

clamd 0:off 1:off 2:on 3:on 4:on 5:on 6:off

crond 0:off 1:off 2:on 3:on 4:on 5:on 6:off

freshclam 0:off 1:off 2:on 3:on 4:on 5:on 6:off

harddrake 0:off 1:off 2:off 3:off 4:off 5:off 6:off

hplip 0:off 1:off 2:on 3:on 4:on 5:on 6:off

lisa 0:off 1:off 2:off 3:on 4:on 5:on 6:off

netfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off

wltool 0:off 1:off 2:on 3:on 4:on 5:on 6:off

xinetd 0:off 1:off 2:off 3:on 4:on 5:on 6:off

 

xinetd based services:

cups-lpd: off

cvs: off

rsync: off

 

These are the services I think you could disable potentially. First off, lisa, just remove it, it's not really usable, so:

 

urpme lisa

 

will free up some resource. Now the rest. atd and crond are scheduling for jobs. If you only use your system as a desktop and nothing else, and don't leave it running all the time, then you can safely disable both of these. To disable:

 

chkconfig servicename off

 

where servicename is the name from the list above, example:

 

chkconfig atd off

 

atieventsd I'm not sure of, so maybe don't disable this unless you know what it is, or post back with the results from this command:

 

rpm -qf /etc/init.d/atieventsd

 

avahi-daemon is supposed to report info on your system across the network, usually used for zeroconf, so can be disabled no problem.

 

clamd/freshclam are your anti-virus, but you can probably disable this if you want to.

 

harddrake is the hardware detection. If you don't plug many additional devices into your system, then disable this. If you plug in USB sticks or hard disks, then leave this, as I had problems with them being detected otherwise.

 

hplip I think is something with your printer, do the rpm -qf command like I did above for the atievents and post back so I can see what it is.

 

netfs, you can disable this, you're not using samba or nfs, or anything like this.

 

wltool can be disabled as it's user-space tools for power management, I have this disabled no problem.

 

xinetd can be disabled, since you don't have any xinet services running.

Link to comment
Share on other sites

OK, here are the results. Thanks for your help, I really appreciate it.

 

# urpme lisa

removing lisa-3.5.4-3mdv2007.0.i586

[root@localhost kieth]# chkconfig atd off

[root@localhost kieth]# chkconfig avahi-daemon off

[root@localhost kieth]# chkconfig clamd off

[root@localhost kieth]# chkconfig freshclam off

clamd is needed by freshclam in runlevel 2

[root@localhost kieth]# rpm -qf /etc/init.d/atieventsd

ati-8.28.8-3plf2007.0

[root@localhost kieth]# rpm -qf /etc/init.d/hplip

hplip-1.6.9-1mdv2007.0

[root@localhost kieth]# chkconfig netfs off

[root@localhost kieth]# chkconfig wltool off

[root@localhost kieth]# chkconfig xinetd off

Link to comment
Share on other sites

OK, you can leave atieventsd and hplip. Don't wanna disable these in case something stops functioning :P

 

The rest should free up memory, and thus make you system a bit better. Check on rebooting now how it feels and whether the boot process is any better.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share


×
×
  • Create New...