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

Thread: Boot problem after kernel update on 10/15/2018 - additional from another thread

  1. #1
    Join Date
    Apr 2018
    Location
    U.S Midwest just West of the Mississippi River
    Posts
    387

    Default Boot problem after kernel update on 10/15/2018 - additional from another thread

    From a thread started by pier_andreit, that I sort of hijacked yesterday.

    Quote Originally Posted by deano_ferrari View Post
    Try editing the linux boot options via the grub config. Press 'e' at the grub screen, and arrow down until you find the entry beginning with 'linux' or 'linuxefi'. Add 'fastboot' to the end of the options, then CTRL +X to boot

    https://doc.opensuse.org/documentati...b2.menu_change

    That should bypass any enabled fsck AFAIU.
    Quote Originally Posted by Bill_L View Post
    I will give it a try.
    OK adding the 'fastboot' parameter got me back into a working Leap 15. But that is a panacea in my new user mind.
    I won't belabor how long the boot process has grown, and seems to get longer.

    My question(s) now are why it did what it did after the kernel update? And what/where to begin to start analyzing that WHY.
    There are only one disk listed in YaST 'Edit Disk Boot Order', so it wasn't AFAIK looking at another of the disks in the machine.

    Or possibly something in this Kernel Parameter line needs to be tweaked?
    Code:
    isofrom=/dev/disk/by-label/UUI:/openSUSE-Leap-42.3-NET-x86_64.iso isofrom_device=/dev/disk/by-label/UUI isofrom_system=/openSUSE-Leap-42.3-NET-x86_64.iso loader=syslinux resume=/dev/sdb1 showopts fastboot
    BTW, That same information is in the 'linux' line after clicking 'e' in the Grub menu.
    I will make mistakes, I will learn from them, They will make me stronger
    Leap 15.0 user, KDE Plasma 5 HP AiO and HP Compaq desktop, Xfce Laptop only

  2. #2
    Join Date
    Apr 2018
    Location
    U.S Midwest just West of the Mississippi River
    Posts
    387

    Default Re: Boot problem after kernel update on 10/15/2018 - additional from another thread

    Kernel is:
    Code:
    localhost:~> uname -r
    4.12.14-lp150.12.22-default
    
    I will make mistakes, I will learn from them, They will make me stronger
    Leap 15.0 user, KDE Plasma 5 HP AiO and HP Compaq desktop, Xfce Laptop only

  3. #3
    Join Date
    Apr 2018
    Location
    U.S Midwest just West of the Mississippi River
    Posts
    387

    Default Re: Boot problem after kernel update on 10/15/2018 - additional from another thread

    This line from dougdeep's 'Slow Booting&found problem' is what my HP desktop was ding just prior to it stopping the boot process completely.
    A Start Job is running for DEV-DISK-BY\X2UUIDTD733AD84\X2D5F44\~LordyThisIsALongString~.DEVICE 1min 30sec
    I can remove fastboot from the 'linux' line in grub and try to capture the actual disk name(UUID?) if needed.

    My system is starting very much slower the past few weeks so I am interested if dougdeep's problem relate to mine.
    I will make mistakes, I will learn from them, They will make me stronger
    Leap 15.0 user, KDE Plasma 5 HP AiO and HP Compaq desktop, Xfce Laptop only

  4. #4
    Join Date
    Apr 2018
    Location
    U.S Midwest just West of the Mississippi River
    Posts
    387

    Default Re: Boot problem after kernel update on 10/15/2018 W/images - additional from another thread

    With 'fastboot' remove from the grub 'linux' line.

    http://susepaste.org/17547598

    Grub-boot-options


    http://susepaste.org/18268708
    Start-Job-screen showing the job sequence and disk UUID


    http://susepaste.org/80640724
    Boot-stop-screen - where it just stops doing anything.

    I should add, that when I get tired of waiting and press the power button, It runs my Optic Drive as if I am first starting the machine.
    I will make mistakes, I will learn from them, They will make me stronger
    Leap 15.0 user, KDE Plasma 5 HP AiO and HP Compaq desktop, Xfce Laptop only

  5. #5
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    750

    Default Re: Boot problem after kernel update on 10/15/2018 - additional from another thread

    Quote Originally Posted by Bill_L View Post
    Code:
    isofrom=/dev/disk/by-label/UUI:/openSUSE-Leap-42.3-NET-x86_64.iso isofrom_device=/dev/disk/by-label/UUI isofrom_system=/openSUSE-Leap-42.3-NET-x86_64.iso loader=syslinux resume=/dev/sdb1 showopts fastboot
    In a single HD system, the resume device should not be sdb. Your /etc/fstab, /etc/default/grub and /boot/grub2/grub.cfg all need to be in sync WRT your swap space. I find it easiest to use labels, which are humanly memorable, rather than the lengthy random UUIDs the installer creates. So, start by reformatting your swap (this assumes that your swap partition is the first partition on your only HD):
    Code:
    mkswap -L d1p1swap /dev/sda1
    Next, edit /etc/default/grub to include resume=LABEL=d1p1swap in place of resume=/dev/sdb1. Do the same with /etc/fstab. Finally, use YaST2 to update your bootloader by changing the timeout value up or down by 1, confirming that the resume=value remains as you just edited. Next boot should not have the timeout delay from non-existent resume device.

    You can test that the resume= parameter is your problem by using the e key at the grub menu to remove the entirety of resume=blahblahwhatever before proceeding to boot.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2) & 42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,others on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,GT218 &&&&

  6. #6
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    19,151
    Blog Entries
    1

    Default Re: Boot problem after kernel update on 10/15/2018 - additional from another thread

    Quote Originally Posted by Bill_L View Post
    My question(s) now are why it did what it did after the kernel update? And what/where to begin to start analyzing that WHY.
    There are only one disk listed in YaST 'Edit Disk Boot Order', so it wasn't AFAIK looking at another of the disks in the machine.

    Or possibly something in this Kernel Parameter line needs to be tweaked?
    Code:
    isofrom=/dev/disk/by-label/UUI:/openSUSE-Leap-42.3-NET-x86_64.iso isofrom_device=/dev/disk/by-label/UUI isofrom_system=/openSUSE-Leap-42.3-NET-x86_64.iso loader=syslinux resume=/dev/sdb1 showopts fastboot
    BTW, That same information is in the 'linux' line after clicking 'e' in the Grub menu.
    Bill, I don't understand your disk layout or boot loader setup. Why is the openSUSE 42.3 net ISO in your (openSUSE 15) grub entry?

    Can you show more details about your disks?
    Code:
    sudo /sbin/fdisk -l
    Code:
    /usr/sbin/blkid
    Last edited by deano_ferrari; 17-Oct-2018 at 01:10.
    openSUSE Leap 15.0; KDE Plasma 5

  7. #7
    Join Date
    Apr 2018
    Location
    U.S Midwest just West of the Mississippi River
    Posts
    387

    Default Re: Boot problem after kernel update on 10/15/2018 - additional from another thread

    Quote Originally Posted by deano_ferrari View Post
    Bill, I don't understand your disk layout or boot loader setup. Why is the openSUSE 42.3 net ISO in your (openSUSE 15) grub entry?

    Can you show more details about your disks?
    That mess in the 'linux' line has been in the grub 'e'dit mode since I installed 42.3, and it was carried over to Leap 15 during the update from 42.3 to leap.
    It also is in YaST kernel settings.
    I asked once before about it, and never got a response as to why it is what it is.
    And /dev/sdb/ is not the in the fdisk. it was the USB stick at the time of 42.3 install. Again, I will get fhe full fdisk -l later.

    I will get the other things you asked for when I get back to the desktop later this day.

    Also. the fsck disk check in the one of the images I posted appears to be the '/' root partition.
    I will make mistakes, I will learn from them, They will make me stronger
    Leap 15.0 user, KDE Plasma 5 HP AiO and HP Compaq desktop, Xfce Laptop only

  8. #8
    Join Date
    Apr 2018
    Location
    U.S Midwest just West of the Mississippi River
    Posts
    387

    Default Re: Boot problem after kernel update on 10/15/2018 - additional from another thread

    Quote Originally Posted by mrmazda View Post
    snip snip
    I will look closer to your recommendations when I climb those mountainous stairs again this day to get to the desktop.
    I will make mistakes, I will learn from them, They will make me stronger
    Leap 15.0 user, KDE Plasma 5 HP AiO and HP Compaq desktop, Xfce Laptop only

  9. #9
    Join Date
    Apr 2018
    Location
    U.S Midwest just West of the Mississippi River
    Posts
    387

    Default Re: Boot problem after kernel update on 10/15/2018 - additional from another thread

    In response to deano-ferrari's request for more details about disk information:

    Code:
    sudo /sbin/fdisk -l
    Disk /dev/sda: 149.1 GiB, 160041885696 bytes, 312581808 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0xfb30b87c
    
    DeviceBoot    Start      End SectorsSizeIdType
    /dev/sda1       245457135 312577711 67120577  32G  7 HPFS/NTFS/exFAT
    
    
    Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x00000001
    
    DeviceBoot    Start      End  Sectors  SizeIdType
    /dev/sdb1  *           64    204863    204800   100M  7 HPFS/NTFS/exFAT
    /dev/sdb2          208845 660242866 660034022 314.7G  7 HPFS/NTFS/exFAT
    /dev/sdb3       660244480 661202943    958464   468M 27 Hidden NTFS WinRE
    /dev/sdb4       661203270 976769071 315565802 150.5G  7 HPFS/NTFS/exFAT
    
    
    Disk /dev/sdc: 149 GiB, 160000000000 bytes, 312500000 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0xd0f4738c
    
    DeviceBoot    Start      End  SectorsSizeIdType
    /dev/sdc1            2048  16771071  16769024   8G 82 Linux swap / Solaris
    /dev/sdc2  *     16771072 100663295  83892224  40G 83 Linux
    /dev/sdc3       100663296 205518847 104855552  50G 83 Linux
    /dev/sdc4       205518848 312498175 106979328  51G 83 Linux
    
    AND
    Code:
    /usr/sbin/blkid                                                                                                                                      
    /dev/sda1: LABEL="WesternDigital IDE 160" UUID="D2E8C97CE8C95F7B" TYPE="ntfs" PARTUUID="fb30b87c-01"                                                               
    /dev/sdb1: LABEL="System Reserved" UUID="1A0CB3280CB2FE37" TYPE="ntfs" PARTUUID="00000001-01"                                                                      
    /dev/sdb2: LABEL="Windows 10 Home Release" UUID="0FCB1B290FCB1B29" TYPE="ntfs" PARTUUID="00000001-02"                                                              
    /dev/sdb3: UUID="40888E43888E3804" TYPE="ntfs" PARTUUID="00000001-03"                                                                                              
    /dev/sdb4: LABEL="Windows 7 64 Home" UUID="ACB2B4EEB2B4BDE0" TYPE="ntfs" PARTUUID="00000001-04"                                                                    
    /dev/sdc1: UUID="0f558cfc-c8f3-4c78-93a8-cc4a7acba25d" TYPE="swap" PARTUUID="d0f4738c-01"                                                                          
    /dev/sdc2: UUID="4e8d4f1f-f98f-4e94-adfc-bdf649be2f0f" TYPE="ext3" PTTYPE="dos" PARTUUID="d0f4738c-02"                                                             
    /dev/sdc3: UUID="4a8eefe9-5576-4315-b7a2-9837e9957b42" TYPE="ext3" PARTUUID="d0f4738c-03"                                                                          
    /dev/sdc4: LABEL="data" UUID="6e1e2ac3-d36d-40f9-913d-b4e7fd194c12" TYPE="ext3" PARTUUID="d0f4738c-04"   
    
    I will make mistakes, I will learn from them, They will make me stronger
    Leap 15.0 user, KDE Plasma 5 HP AiO and HP Compaq desktop, Xfce Laptop only

  10. #10
    Join Date
    Apr 2018
    Location
    U.S Midwest just West of the Mississippi River
    Posts
    387

    Default Re: Boot problem after kernel update on 10/15/2018 - additional from another thread

    Quote Originally Posted by mrmazda View Post
    In a single HD system, the resume device should not be sdb. Your /etc/fstab, /etc/default/grub and /boot/grub2/grub.cfg all need to be in sync WRT your swap space. I find it easiest to use labels, which are humanly memorable, rather than the lengthy random UUIDs the installer creates. So, start by reformatting your swap (this assumes that your swap partition is the first partition on your only HD):
    Code:
    mkswap -L d1p1swap /dev/sda1
    Next, edit /etc/default/grub to include resume=LABEL=d1p1swap in place of resume=/dev/sdb1. Do the same with /etc/fstab. Finally, use YaST2 to update your bootloader by changing the timeout value up or down by 1, confirming that the resume=value remains as you just edited. Next boot should not have the timeout delay from non-existent resume device.

    You can test that the resume= parameter is your problem by using the e key at the grub menu to remove the entirety of resume=blahblahwhatever before proceeding to boot.
    What happens if I remove all the garbage before the 'showopts fastboot'?
    There IS a /dev/sdb1 , which happens to be on my Windows drive.
    Leap 15 is on it's own HDD.
    See the fdisk -l posted above.
    I will make mistakes, I will learn from them, They will make me stronger
    Leap 15.0 user, KDE Plasma 5 HP AiO and HP Compaq desktop, Xfce Laptop only

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
  •