Page 1 of 3 123 LastLast
Results 1 to 10 of 27

Thread: 11.4 troubled boots

  1. #1
    Join Date
    Apr 2011
    Posts
    25

    Question 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.

    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
    Code:
    mdadm --assemble --scan
    then mount my volumes manually
    Code:
    mount /boot /home /home/user/raid
    then
    Code:
    init 5
    I also will need to do
    Code:
    NetworkManager up
    and
    Code:
    service vmware restart
    some times init 5 also did not work, it took this
    Code:
    kdm restart
    or
    Code:
    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
    Code:
    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!

  2. #2
    Join Date
    Apr 2011
    Posts
    25

    Arrow Re: 11.4 troubled boots

    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??

    Code:
    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

  3. #3

    Default Re: 11.4 troubled boots

    How are you installing? LiveCD, network, DVD?
    Did you verify your download?
    Vaio F11: i7-720QM 8GB RAM Nvidia GT 330m
    Win 7 Pro 64 bit | openSuse 11.4 64 bit | Arch Linux 64 bit

  4. #4
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: 11.4 troubled boots

    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)

  5. #5
    Join Date
    Apr 2011
    Posts
    25

    Default Re: 11.4 troubled boots

    Quote Originally Posted by bsilvereagle View Post
    How are you installing? LiveCD, network, DVD?
    Did you verify your download?
    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:

    Code:
    zypper se -i |awk -F\| '{print $2}'|sed 's/^[ \t]*//' >/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:

    Code:
    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!

    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.


  6. #6
    Join Date
    Apr 2011
    Posts
    25

    Thumbs up Re: 11.4 troubled boots

    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!

  7. #7
    Join Date
    Apr 2011
    Posts
    25

    Exclamation Re: 11.4 troubled boots

    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. 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.


  8. #8
    Join Date
    Apr 2011
    Posts
    25

    Lightbulb Re: 11.4 troubled boots

    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?

    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:


    Code:
    # 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

  9. #9
    Join Date
    Apr 2011
    Posts
    25

    Lightbulb Re: 11.4 troubled boots

    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.

    Code:
    # 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


    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.


  10. #10
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: 11.4 troubled boots

    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)

Page 1 of 3 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •