11.4 troubled boots

I had no issue with 11.3 and I had used suse since 9.x seemingly this time is most difficult.:frowning:

Actually my personal take is there are some init (rcX.d) issues, unstable and unpredictable. I did more than one fresh installations in the same system on different partitions, and still find them all unstable and unpredictable.

Hardware is 6core AMD 16GB ram, with raid0 and other SATA and a SSD.

Several issues when boot.

Some times drop me to a simple shell (repair mode) asking root password.
Some times will boot to a run level 3 type shell, can login any users.
Occasionally, will boot into run level 5 GUI, but no LAN, and no vmware services.
Most of the time, no raid, I had to manually mount.

I edited run levels making mdadm run at all levels 1235, seems worst.>:(

If I got drop to repair mode shell, after giving root passwd, I need to do

mdadm --assemble --scan 

then mount my volumes manually

mount /boot /home /home/user/raid

then

init 5

I also will need to do

NetworkManager up

and

service vmware restart

some times init 5 also did not work, it took this

kdm restart

or

service xdm restart

That i can finally run in GUI (KDE4)

Things got so tiring I am using shell script to do these tedious routines already.

Then by mistake I uninstall pulseaudio in zypper, and reinstalled after I realize, but sound won’t come back, kmix won’t even start. This happened only to one of the 11.4 installations, in the other installation it was not broken like this.

In the other instant of installation, same machine, it always lost my host name that my Konsole prompt became user@(none):~ and only

syscntl -p

will fix my hostname.

So according to the above scenario, does it suggest that some of the initiation or rc5.d is bad? I shouldn’t have to do all this manually.

My test in vmware vm are almost perfect.

Before I installed ati-driver-installer-11-3-x86.x86_64.run my screen was blank, after initial installation from the NET install CD! I couldn’t control the pc, so I mounted the HDD into a vmware vm, and installed ATI driver, then I had my screen display.
:\

There is no consistency in the nature of the boot / init issues, it appears to be random and opportunistic. I can just repeatedly reboot without adjusting / altering anything and depending on lucks, it can give me better or worst results. I struggled with the help of my past SuSE experience to cope with the difficulties to get boot process up manually. BTW, the same machine is installed with Kubuntu 10.10 and FC14, in multi-boot, in separated partitions, no issues at all. Before I used 11.4 the same machine ran 11.3 perfectly also.

Any idea any one? What is bugging me?

Thanks! :sarcastic:

BTW there is another clue that RECOVERY MODE will Always never boot up (I use GRUB2 due to Kubuntu, but should not be the issue because SuSE 11.3 worked), the result is always a kernel panic during boot. I suspect initrd lacks certain modules??
:open_mouth:

menuentry "SuSE 11.4, with 2.6.37.1-1.2-desktop (recovery mode)  (on /dev/sdd7)" {
        set gfxmode=1680x1050
        set gfxpayload=keep  
        insmod raid
        insmod mdraid
        insmod gfxterm
        insmod vbe
        insmod part_msdos
        insmod ext2
        set root='(/dev/sdd,msdos5)'
        search --no-floppy --fs-uuid --set 61a9e3b8-09c0-42bd-adf1-ce4b152f8411
        linux /vmlinuz-2.6.37.1-1.2-desktop root=/dev/sdd7 showopts  apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe
        initrd /initrd-2.6.3.7.1-1.2-desktop

How are you installing? LiveCD, network, DVD?
Did you verify your download?

On 2011-04-13 21:06, uy wrote:
> Actually my personal take is there are some init (rcX.d) issues,

There is indeed.

/etc/sysconfig/boot:RUN_PARALLEL=yes

Set it to “NO”.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

It was the NETWORK installation CD that I used firstly, and after encountering these issues, I forced zypper to reinstall all packages - following my previous installation.

I exported my previous installation’s package list by:

zypper se -i |awk -F\| '{print $2}'|sed 's/^ 	]*//' >/media/USB-disk/zyp.lst.txt

It dumps a list into my thumb drive in USB - but imperfectly, I need to use kwrite to edit that file deleting 4 beginning lines containing rubbish from headers.

Then I port that edited file in to zypper in the troubled installation:

cat /media/USB-disk/zyp.lst.txt | xargs -L50 zypper in -yifl --force-resolution

Depending on speed of ISP that will take 1-3 hrs to run because my package list is about 1800 items long!:stuck_out_tongue:

I am sharing this command on this forum, thinking they may be helpful to SuSE users who needs to duplicate installations, there is still a catch, in addition to above commands, you will need to 1st duplicate repository settings, that target system must be 1st set to same repository as the source system, otherwise some packages will be NOT FOUND or different versions.

:wink:

Thanks for that hint! Yr opinion looks very logical and convincing, that /etc/sysconfig/boot is an area that I am not familiar and had no suspicion. I will test that. But as for now it fits my own suspicion that multi-tasking with a fast system like this, may be running boot task ahead of pal processes causing hardware to be in unready state and so on, and thus have a random pattern of failure, and will work properly only when dust settles and user manually & slowing trigger these tasks.:\

I will test this ASAP and post the outcome!

OMG! I tested, and I disable parallel boot process in /etc/sysconfig/boot, it altered the scenario, but did not yield any acceptable solution!

My result summery is that it fixed some of the issues while not helping some more important issues, and then also BROKE something else!

The details:
My lost hostname in Konsole prompt came back.
My network interfaces are both lost.
RAID 0 & vmware services reminded not working.

My further tests, proved that it is indeed issue arising from /etc/init.d/boot.d & /etc/init.d/rc5.d areas.

It will take quite a lot of experiments to tweak links in these folders to alter the sequence of process killing & starting during the various changes of states within the bootup process. Whatever is there left to the users by YAST or installer isn’t good.:’(

The system->runlevel tool in YAST control center can be so useful, however users that failed to reach run level 5 GUI have no chance to enjoy that tool. :X It took quite a bit of experience and struggle for me to get to runlevel 5, which I had shared by experience here, and may not be applicable to every one depending on their own individual situations.

OpenSuSE 11.4 fails to boot properly.

I read and posted in above thread as well, what I need to point out here is that many users’ different issues, like lost of NIC; Graphics; RAID; etc services, are most likely caused by the same source of bug - in the /etc/init.d area or known as runlevel control issues. The parallel boot had made it worse and more unpredictable - appearing random nature.

I also want to point out that SuSE had previously got a reputation of SLOW BOOT UP, and then appointed a team according to some web sources I read to improve boot up time to be within a target of 5 seconds. I think it is highly possible that the problem we are facing now are the consequences of overly high optimization of boot up time, that caused unstable or unreliable boot up process. This is the historic aspect of the issue, some thing from what I can recall from the SuSE 10.x or 11.0 era.

For users unfamiliar with boot process, they are going to get a hard time, for experts, it will take many rounds of tests to tweak one system, for quasi-experienced users like myself, I am half-dead, struggling! >:( I can get to runlevel 5 but through hurdles, I have to find out how to rid these pains in the BOOT still.

:shame:

OK Good news from me at least and at last!

I got through after beating around and asking for help here and reading postings of other users.

I am up and running, straight to runlevel 5 GUI but a bit slower, I think due to disabling parallel boot.

I am only left with an unrelated problem, which is caused by myself misusing the zypper command, I am still with no sound, kmix don’t come up, that was me unintentionally uninstalling pulseaudio and then reinstalling it back couldn’t give me sound still. Any one know how to fix this? :frowning:

Hereby I share my solution, not easy but workable, I tweaked runlevel using YSAT CONTROL CENTER -> SYSTEM-> RUN LEVEL, I share my results of tweaking at the end of this post. But this only apply for my system, yours may differ, you have to tweak runlevel to suit your system.

For those users who are unable to reach runlevel 5 (GUI login) you can not enjoy the GUI runlevel tool. You have only to use command shell to tediously like these /etc/init.d files to various folders below it particularly /etc/init.d/boot.d & /etc/init.d/rc5.d

information within slide #20 of the following file is useful, to know how to link in sequence or modify links in sequences to control the bootup process:
www.blu.org/meetings/2006/06/Linux_Startup.pdf

So my working runlevel result is shared as follows, you may take reference but blindly following may be unsafe:

# ls /etc/init.d/boot.d /etc/init.d/rc?.d
/etc/init.d/boot.d:
K01boot.cleanup   K01boot.sysctl       K04boot.localfs        S02boot.udev           S11boot.localfs     S14boot.quota
K01boot.cycle     K01boot.udev_retry   K06boot.md             S03boot.rootfsck       S13boot.cycle       S14boot.sysctl
K01boot.ipconfig  K02boot.clock        K06boot.rootfsck       S04boot.clock          S13boot.klog        S15boot.cleanup
K01boot.klog      K02boot.loadmodules  K08boot.device-mapper  S05boot.device-mapper  S13boot.proc        S15boot.ipconfig
K01boot.ldconfig  K02boot.proc         K09boot.udev           S05boot.loadmodules    S13boot.swap        S16boot.apparmor
K01boot.localnet  K02boot.swap         K10boot.startpreload   S05boot.localnet       S13boot.udev_retry
K01boot.quota     K03boot.apparmor     S01boot.startpreload   S08boot.md             S14boot.ldconfig

/etc/init.d/rc0.d:
S01halt

/etc/init.d/rc1.d:
S01fbset  S01microcode.ctl  S07kbd  S08irq_balancer  S08splash  S09single  S16stoppreload

/etc/init.d/rc2.d:
K01bluez-coldplug  K01random        K01vmware     K08syslog       S01microcode.ctl  S08bluez-coldplug  S11sbl
K01brld            K01sbl           K02acpid      K09earlysyslog  S01random         S08brld            S12cron
K01cpufreq         K01smartd        K02alsasound  S01acpid        S03syslog         S08irq_balancer    S12smartd
K01cron            K01splash        K02cups       S01cpufreq      S04splash_early   S08mcelog          S16stoppreload
K01irq_balancer    K01splash_early  K02fbset      S01dbus         S04vmware         S08splash
K01mcelog          K01stoppreload   K02kbd        S01earlysyslog  S07kbd            S08vboxadd
K01microcode.ctl   K01vboxadd       K03dbus       S01fbset        S08alsasound      S11cups

/etc/init.d/rc3.d:
K01auditd          K01smartd        K02fbset             S01dbus           S08alsasound         S11cups
K01bluez-coldplug  K01splash        K02kbd               S01earlysyslog    S08avahi-daemon      S11nscd
K01brld            K01splash_early  K02postfix           S01fbset          S08bluez-coldplug    S11postfix
K01cpufreq         K01sshd          K03dbus              S01microcode.ctl  S08brld              S11sbl
K01cron            K01stoppreload   K03ntp               S01random         S08irq_balancer      S12cron
K01irq_balancer    K01vboxadd       K04network-remotefs  S02network        S08mcelog            S12mdadmd
K01mcelog          K01vmtoolsd      K07rpcbind           S03syslog         S08network-remotefs  S12smartd
K01mdadmd          K01vmware        K08syslog            S04auditd         S08splash            S16stoppreload
K01microcode.ctl   K02acpid         K09earlysyslog       S04rpcbind        S08sshd
K01nscd            K02alsasound     K09network           S04splash_early   S08vboxadd
K01random          K02avahi-daemon  S01acpid             S04vmware         S08vmtoolsd
K01sbl             K02cups          S01cpufreq           S07kbd            S09ntp

/etc/init.d/rc4.d:

/etc/init.d/rc5.d:
K01auditd          K01smartd        K02earlyxdm          S01dbus           S08avahi-daemon      S11nscd
K01bluez-coldplug  K01splash        K02fbset             S01earlysyslog    S08bluez-coldplug    S11postfix
K01boot.ipconfig   K01splash_early  K02kbd               S01fbset          S08brld              S11sbl
K01brld            K01sshd          K02postfix           S01microcode.ctl  S08irq_balancer      S12cron
K01cpufreq         K01stoppreload   K03dbus              S01random         S08mcelog            S12mdadmd
K01cron            K01vboxadd       K03ntp               S02network        S08network-remotefs  S12smartd
K01irq_balancer    K01vmtoolsd      K04network-remotefs  S03syslog         S08splash            S12xdm
K01mcelog          K01vmware        K07rpcbind           S04auditd         S08sshd              S15boot.ipconfig
K01mdadmd          K01xdm           K08syslog            S04rpcbind        S08vboxadd           S16stoppreload
K01microcode.ctl   K02acpid         K09earlysyslog       S04splash_early   S08vmtoolsd
K01nscd            K02alsasound     K09network           S04vmware         S09ntp
K01random          K02avahi-daemon  S01acpid             S07kbd            S11cups
K01sbl             K02cups          S01cpufreq           S08alsasound      S11earlyxdm

/etc/init.d/rc6.d:
S01reboot

/etc/init.d/rcS.d:
S04boot.clock  S07kbd  S08splash  S09single

Just to add a further note to this thread since I had done a bit more works in this aspect. The change from parallel boot to non-parallel does contribute to stability, necessary in my case, the process of boot is longer in this case as expected.

Without this stability we would be shooting in the dark trying to tweak runlevels issue.

I had completed the other instant of SuSE 11.4 in my other partition, which was installed for testing and debugging this issue. I will share the runlevel settings here for reference, it is not the same as what I had previously posted which is from other instant of SuSe install, in that 1st 1 my intel HDA sound is broken, in this 1 here intel HDA sound works.

# ls /etc/init.d/boot.d /etc/init.d/rc?.d
/etc/init.d/boot.d:
K01boot.cleanup   K01boot.udev_retry   K06boot.md             S03boot.rootfsck       S13boot.cleanup     S14boot.ldconfig
K01boot.cycle     K02boot.clock        K06boot.rootfsck       S04boot.clock          S13boot.cycle       S14boot.sysctl
K01boot.ipconfig  K02boot.loadmodules  K08boot.device-mapper  S05boot.device-mapper  S13boot.klog        S15boot.ipconfig
K01boot.klog      K02boot.proc         K09boot.udev           S05boot.loadmodules    S13boot.proc
K01boot.ldconfig  K02boot.swap         K10boot.startpreload   S05boot.localnet       S13boot.swap
K01boot.localnet  K03boot.apparmor     S01boot.startpreload   S08boot.md             S13boot.udev_retry
K01boot.sysctl    K04boot.localfs      S02boot.udev           S11boot.localfs        S14boot.apparmor

/etc/init.d/rc0.d:
S01halt

/etc/init.d/rc1.d:
S01fbset  S01microcode.ctl  S07kbd  S08irq_balancer  S08splash  S09single  S13stoppreload

/etc/init.d/rc2.d:
K01bluez-coldplug  K01smartd        K02fbset             S01cpufreq        S03syslog          S08network-remotefs
K01cpufreq         K01splash        K02kbd               S01dbus           S04splash_early    S08splash
K01cron            K01splash_early  K02network-remotefs  S01earlysyslog    S04vmware          S11cups
K01haldaemon       K01stoppreload   K03dbus              S01fbset          S07kbd             S12cron
K01irq_balancer    K01vmware        K07syslog            S01microcode.ctl  S08alsasound       S12smartd
K01mcelog          K02acpid         K08earlysyslog       S01random         S08bluez-coldplug  S13stoppreload
K01microcode.ctl   K02alsasound     K08network           S02haldaemon      S08irq_balancer
K01random          K02cups          S01acpid             S02network        S08mcelog

/etc/init.d/rc3.d:
K01SuSEfirewall2_setup  K01splash_early      K04cifs                S01random          S08irq_balancer
K01auditd               K01stoppreload       K05nfs                 S02haldaemon       S08mcelog
K01bluez-coldplug       K01vmtoolsd          K07syslog              S02network         S08network-remotefs
K01cpufreq              K01vmware            K08earlysyslog         S03syslog          S08splash
K01cron                 K02acpid             K08network             S04auditd          S08vmtoolsd
K01haldaemon            K02alsasound         K09SuSEfirewall2_init  S04splash_early    S11cups
K01irq_balancer         K02avahi-daemon      S01SuSEfirewall2_init  S04vmware          S11nscd
K01mcelog               K02cups              S01acpid               S05nfs             S11postfix
K01microcode.ctl        K02fbset             S01cpufreq             S06cifs            S12cron
K01nscd                 K02kbd               S01dbus                S07kbd             S12smartd
K01random               K02network-remotefs  S01earlysyslog         S08alsasound       S13SuSEfirewall2_setup
K01smartd               K02postfix           S01fbset               S08avahi-daemon    S13stoppreload
K01splash               K03dbus              S01microcode.ctl       S08bluez-coldplug                                        
                                                                                                                             
/etc/init.d/rc4.d:                                                                                                           
                                                                                                                             
/etc/init.d/rc5.d:                                                                                                           
K01auditd          K01splash        K02fbset             S01dbus           S08alsasound         S11nscd                      
K01bluez-coldplug  K01splash_early  K02kbd               S01earlysyslog    S08avahi-daemon      S11postfix                   
K01boot.ipconfig   K01sshd          K02postfix           S01fbset          S08bluez-coldplug    S12cron                      
K01cpufreq         K01stoppreload   K03dbus              S01microcode.ctl  S08irq_balancer      S12mdadmd                    
K01cron            K01vmtoolsd      K03ntp               S01random         S08mcelog            S12smartd                    
K01irq_balancer    K01vmware        K04network-remotefs  S02network        S08network-remotefs  S12xdm                       
K01mcelog          K01xdm           K07rpcbind           S03syslog         S08splash            S15boot.ipconfig             
K01mdadmd          K02acpid         K08syslog            S04auditd         S08sshd              S16stoppreload               
K01microcode.ctl   K02alsasound     K09earlysyslog       S04rpcbind        S08vmtoolsd                                       
K01nscd            K02avahi-daemon  K09network           S04splash_early   S09ntp                                            
K01random          K02cups          S01acpid             S04vmware         S11cups                                           
K01smartd          K02earlyxdm      S01cpufreq           S07kbd            S11earlyxdm                                       
                                                                                                                             
/etc/init.d/rc6.d:                                                                                                           
S01reboot                                                                                                                    
                                                                                                                             
/etc/init.d/rcS.d:                                                                                                           
S04boot.clock  S07kbd  S08splash  S09single

:wink:

I am not showing the details or targets of the links in above, I think the targets should be quite obvious if you looked in /etc/init.d folder’s content they are there. If you see something here that you don’t have, that is something that you can ignore, because you are not using some services that I am using.

:slight_smile:

On 2011-04-14 08:06, uy wrote:
> For those users who are unable to reach runlevel 5 (GUI login) you can
> not enjoy the GUI runlevel tool. You have only to use command shell to
> tediously like these /etc/init.d files to various folders below it
> particularly /etc/init.d/boot.d & /etc/init.d/rc5.d

YaST can be used in text mode. And, there is another tool to change those
things: chkconfig.

Warning: NEVER change the links manually, that will break.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

True! I had just once or twice used it, and forgot already. :shame:

Agree, links would be modified by system commands and programs like YAST, which are unaware of your tweaks these days.

My early days of tweaking RedHat 8 etc there were no such luxury user friendly tools, everything was tweaked manually.

These days GRUB2 will modify it’s own /boot/grub/grub.cfg file and override your own tweaks, which is already unlike GRUB1 that we would engineer the /boot/grub/menu.lst to customize our boxes. :wink:

On 2011-04-14 14:06, uy wrote:
> Agree, links would be modified by system commands and programs like
> YAST, which are unaware of your tweaks these days.

It is because besides the links there are some other files:

/etc/init.d/.depend.boot /etc/init.d/.depend.halt
/etc/init.d/.depend.start /etc/init.d/.depend.stop

This are used, I think, for the parallel booting logic; it is possible that
when it is disabled the links are used instead, I don’t have that clear.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

Most excellent diagnosis, test and documentation of the issue and your solution.
I would ask for a simplified explanation of the actions you did to the /etc/init.d/ folders for those of us who may not have that understanding or followed.

I am sure some will shudder with this suggestion, but it is simple and so far it has worked.

This note addresses the situation where the SuSE 11.4 IPL boot process stalls with

“doing fast boot
Creating device nodes with udev”
(delay)
(repeating CPU timing and register dump messages)

and it is necessary to power the computer off, then on again to retry the boot process.

Computer is a Dell 3000 - Pentium 4 Celeron D 2.4 with an Intel 865 GV chipset. It has limited dual core capabilities. The video “device” is identified as an Intel 845 G and the Vesa driver is specified in a /etc/X11/xorg.conf file which was borrowed from a SuSE 11.2 installation.

Using the option ‘nomodeset’ had no apparent effect. “Run_parallel=No” is not implemented.

Hack:

When starting the system from a cold boot, watch for the normal system bios screen.
The screen is then erased to black.
If you watch carefully (at least on this computer) you will see a screen repaint. The screen will still be black, but will change to a lighter shade. Immediately after the screen changes to the lighter color, and before the Grub splash screen appears, press the keyboard Enter key.

The Grub splash screen is bypassed and the system will boot normally. Using this procedure, the system consistently recognizes the xorg.conf file and establishes proper screen resolution.

Bill
(ducking)

On 2011-04-15 08:36, hbco2 wrote:
> The Grub splash screen is bypassed and the system will boot normally.
> Using this procedure, the system consistently recognizes the xorg.conf
> file and establishes proper screen resolution.

Disable the message file display in grub - that will make it display in
text mode. My wild guess is that the result may be similar.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

I won’t say I am doing any good job of diagnosis, because to do that I would had to stepback every time after I got past a snag, and verify or prove my theory of discovery, but instead of that, I just simply past whatever snag I got past, and roughly guess the best logical reason of it and share without really recreate the issue or prove the solution.

My main snags were these:

GRUB not original SuSE, because I am multi-booting Kubuntu Fedora Core & some other experimental stuffs. My GRUB is GRUB 2.x while SuSE is GRUB 1.x - this is a relatively small issue, but can bug new users badly.

Soft RAID not starting not mounting during boot. This is a big issue to me, my /home & /home/user/raid are are soft RAID0, it is still in some trouble although I can already boot straight into runlevel 5, the pain now is it will still not straight away see my raid volume, and it wait there for 20sec unlike in other Linux, it displays my RAID uuid and says awaiting for it to appear, and show a long bunch of dots… after 20s it would see my raid and continue. I forced** /etc/init.d/boot.md** to early trigger in /etc/init.d/boot.d. I added these to GRUB2** /boot/grub/grub.cfg** which is the file that took the role of** /boot/grub/menu.lst**

xorg driver issue, somehow ATI radeon driver supplied inside SuSE was unable to get me to GUI level. I must install driver from ATI site, ati-driver-installer-11-3-x86.x86_64.run this version works for me. I think my own xorg.conf is abit too complicated for SuSE’s defaults, I have dual screen and rotated., with Kubuntu & FC I had only a little trouble with xorg.

menuentry "SuSE 11.4, with 2.6.37.1-1.2-desktop  (on /dev/sdf6)" {
        set gfxmode=1680x1050
        set gfxpayload=keep
        insmod raid
        insmod mdraid
        insmod gfxterm
        insmod vbe
        insmod part_msdos
        insmod ext2
        set root='(/dev/sdd,msdos5)'
        search --no-floppy --fs-uuid --set 61a9e3b8-09c0-42bd-adf1-ce4b152f8411
        linux /vmlinuz-2.6.37.1-1.2-desktop root=UUID=a9a93efe-4e1f-455a-bf65-0ecfe93838ad splash=silent showopts
        initrd /initrd-2.6.37.1-1.2-desktop
}

If you checked the above codes there are raid related modules and display splash screen addressing statements in GRUB2 added by me. I just added them and got past my snags, however what I did not do is to try remove them one by one, and see if I had actually added unnecessary (over kill) settings or not. That is to say I am still not optimized, I am just out of the woods alive.

I also have xdm snags, when it was in unpredictable state in parallel boot mode, I used combinations of followings to get my GUI, but surely, none of it will help before I installed the above-mentioned ATI Linux driver. The pain in the Azz of this driver is each & every time SuSe kernel is updated, you have to reinstall it again, and before you do so you got no GUI once you reboot. So users are hereby warned!

sudo init 5  (when you are thrown to runlevel 3 - runlevel command will tell you)
sudo kdm restart  (I use KDE)
sudo service xdm restart

Any of the above, may work or a combination of the above, had been able to get me into GUI, that was when parallel boot was making things unstable for me, and I was shooting in the dark. After I rid parallel boot, it became stable, and init 5 was good enough, only in one occasion, I needed sudo service xdm restart but I think that instant does not count because I was then tweaking runlevel, and it might had been my own tweaks that got myself into troubles.

LAN NIC lost, no networks, if your /etc/fstab for example have cifs samba or nfs mounts, your boot issue will be even harder due to this, remark away these stuffs in /etc/fstab until after you are out of the dark with the boot issues. Otherwise, you can not isolate issues.

The other snag is vmware.com virtual machine services did not start, and alsa sound server did not start, after 1st removing parallel boot and tweaking runlevel services they worked, in the process of experiment I broke sound in one installation, still don’t know how to fix it, but I am using the other installation now. :X If you had more harddisk ready for partitioning, and you know how to properly setup multi-boot, you can trouble-shoot and tweak in safer conditions, by playing with more than 1 instant of SuSe installation. I also used virtual machine to mount my installation to help myself get access to the unbootable deadlock situations, live CD can surely help you as well.

There are many more minor snags like my konsole hostname got lost, and some un-useful daemons reporting errors during boot, postfix, mysql, brill codes etc, can all come in and complicate your troubles, knock these services & daemons away, and focus on getting GUI display and LAN NIC up, and your /home partitions can mount so that you can use a comfortable GUI environment to deal with the rest of the issues. Otherwise, you are unable to isolate issues, you need to single out these issues one by one.:\

My old RedHat 8 days experience helped, because in those days, we needed to learn how the links inside /etc/init.d/boot.d and /etc/init.d/rc5.d are meant to do.:expressionless: they are alike ON/OFF switches to each of the services of linux. They are like timer sequencers, K01xdm will kill xdm very first K99ssh will kill ssh last and so on the 2 digit numbers are sequence order, and letter K means kill S means start. So in each runlevel, these links there programs all the services that you have, weather they will kill which 1st and which next, and after killing all, which to start 1st, because of interdependency with each other you can not successfully start / stop in illogical sequence, even if you needed the service, you are better of to kill it off 1st and start it a while after, to have a clean restart or reset effect that will ensure things work. All your services are supposed to be listed in /etc/init.d and in each of runlevel e.g. /etc/init.d/rc5.d for level 5 which is your GUI login level, you only link to these services listed in /etc/init.d.

For example if you mount nfs or samba over network, you surely have to have nfs & smb turned off 1st before turning off boot.ipconfig, if you did the reverse it hangs because smb & nfs can not sign off or unmount when you flipped off tcp/ip switch. To turn back on your sequence is opposite, boot.ipconfig have to be 1st on otherwise you don’t expect to be able to turn on nfs or smb.

The main problems or crisis arise here, is that parallel boot, did not run these ON/OFF in a logical enough sequence, thus hang!>:( that is due to fast processors doing multi tasking and brunch prediction, which tends to do things ahead of schedule, e.g. you programed boot.ipconfig to be killed in sequence #60 and killing smb in sequence #50 it will look logical in your rc3.d for example, but CPU multitasking executed sequence #60 ahead of #50 during parallel boot. I have no evidence, I did not try to prove it, but my hardware knowledge as a multimedia hardware designer preempted me to expect these sort of pain in the Azz all the time, in multimedia hardware, because machines needs to be in some sync and sequence, while multitasking was made to do things fast and ahead of any slow events. So I guess my theory is right, I tweaked with more safer delays between inter-dependent services. I got out of the woods.

sweating…

I use to struggle with booting up primitive prototype hardware that we designed and debug them tediously, so I applied some of these techniques to survive.

I would like to point out a suspicious condition, which I can find no clue until now, and I doubt I can reproduce this any more after I had gone so far after that stage. But it was very consistent and persistently repeated at one stage that the troubled boot process would throw me down to repair shell which just asked for root password, what was so strange then was my /boot partition wouldn’t be mounted, and it IS NOT a raid volume, it is a ext3 partition in a Kingston SATA SSD.

While the other mounts are raid and I totally understand why they won’t mount because raid service was not fully brought up yet at that time /etc/fstab was being mounted. However it is illogical then to have /boot also not mounted. The strangest thing is my kernel and initrd are boot inside that /boot partition, and kernel & initrd had obviously been load up and running already, otherwise there could not be any repair shell.

It seems then the entire process dealing with /etc/fstab is aborted or failed, that means including mount my swap partition tmpfs, which I did not take note during then weather did swap come up.

I am point this out in this msg, hoping other users who experienced /etc/fstab troubles to take note and share their experience, weather did whole /etc/fstab failed. I initially thought only RAID failed, it may be more than that however, as I now recall this illogical fault that /boot also did not mount.

I need /boot to be a partition apart from my SuSE because of my multi-boot, which I have Kubuntu & Fedora, and they all use GRUB2, I need to manage contents of /boot centrally instead of just inside SuSE, in particular also my multi-boot actually have more than one instance of SuSE 11.4, I need to manage /boot from each and every type of booted Linux OS, not just in one. So this /boot is shared. The other big reason is I am using EXT4 partitions which could not boot, so /boot needs to be a separated EXT3 partition.

On 2011-04-15 18:06, uy wrote:
> The main problems or crisis arise here, is that parallel boot, did not
> run these ON/OFF in a logical enough sequence, thus hang!>:( that is due
> to fast processors doing multi tasking and brunch prediction, which
> tends to do things ahead of schedule, e.g. you programed boot.ipconfig
> to be killed in sequence #60 and killing smb in sequence #50 it will
> look logical in your rc3.d for example, but CPU multitasking executed
> sequence #60 ahead of #50 during parallel boot.

No, it can not be that, because parallel booting works fine in openSUSE
11.2, earlier, and later, on multicore machines like mine. Only fails in oS
11.4.

The sequence is not governed by the link numbers, but by makefiles. A
script is not started till all the scripts that are required to finish
before it have finished - that is how it worked. I don’t know what they
have done to 11.4 to break it.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

On 2011-04-16 08:36, uy wrote:
> I am point this out in this msg, hoping other users who experienced
> /etc/fstab troubles to take note and share their experience, weather
> did whole /etc/fstab failed. I initially thought only RAID failed, it
> may be more than that however, as I now recall this illogical fault that
> /boot also did not mount.

No, this is an issue for bugzilla and devs to look at it. Unfortunately,
you have modified your system much beyond the typical one, so they won’t
look at yours.

Just note that the script that parses fstab and the mounts does so much
earlier than the parallel part runs.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

My same hardware ran 11.3 stable, and I upgraded 11.4 with several days of initial stabilities, during which I did not noticed any such troubles, when ony after I added fonts and did some automatic online updates 11.4 began to break for me. It was crazy random and unpredictable, but stablized after only I put off parallel boot. At this moment I can not affor time to go back to experiments, by trying again to break it. In Singapore here, we have General Elections coming up very soon, and I am helping some contestants, I need PC stable and fit to fight cyber poltics. :slight_smile: