LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 09-20-2015, 07:41 PM   #1
fogpipe
Member
 
Registered: Mar 2011
Distribution: Slackware 64 -current,
Posts: 550

Rep: Reputation: 196Reputation: 196
Lilo boot problems sdb seen as sda in debian testing


Im using lilo to boot slackware current on /dev/sda5 and debian testing on /dev/sda1.
Slackware on /dev/sdb5 boots fine.

Lilo is installed to the mbr of /dev/sdc.

The debian kernel, config, system.map and initrd.img files are all in /boot/debian on /dev/sda5, the slackware partition and thats where im running lilo from.

My lilo entry for debian:

Code:
image=/boot/debian/vmlinuz-4.1.0-2-amd64
    root = /dev/sda1
    label=Debian
    initrd=/boot/debian/initrd.img-4.1.0-2-amd64
        read-only
#       restricted
#       alias=1
    append="fb=false"
Which works unless my external usb drive /dev/sdb is plugged in.
If that drive is plugged in lilo or the boot process or something gets /dev/sda confused with /dev/sdb and cant find the root partition or init.

So as things stand now to boot debian i have to unplug /dev/sdb and plug it back in after boot.

I have already tried including
Code:
disk=/dev/sdb
     inaccessible
In lilo.conf so im guessing it isnt lilo.

Is there any way to make lilo or the boot process see /dev/sda1 correctly when /dev/sdb is plugged in?
 
Old 09-20-2015, 07:51 PM   #2
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,346

Rep: Reputation: 1589Reputation: 1589Reputation: 1589Reputation: 1589Reputation: 1589Reputation: 1589Reputation: 1589Reputation: 1589Reputation: 1589Reputation: 1589Reputation: 1589
find the id of the disk with
Code:
blkid
then use
Code:
root = UUID=<disk uuid>
instead of
Code:
root = /dev/sda1
 
1 members found this post helpful.
Old 09-20-2015, 09:10 PM   #3
fogpipe
Member
 
Registered: Mar 2011
Distribution: Slackware 64 -current,
Posts: 550

Original Poster
Rep: Reputation: 196Reputation: 196
Quote:
Originally Posted by colorpurple21859 View Post
find the id of the disk with
Code:
blkid
then use
Code:
root = UUID=<disk uuid>
instead of
Code:
root = /dev/sda1
That gave a syntax error with i tried to put it in root line of the lilo stanza for that kernel. What worked was including that in the append portion of the stanza. Thanks

Last edited by fogpipe; 09-20-2015 at 09:22 PM. Reason: duh too much caffine too little sleep
 
Old 09-22-2015, 04:15 PM   #4
fogpipe
Member
 
Registered: Mar 2011
Distribution: Slackware 64 -current,
Posts: 550

Original Poster
Rep: Reputation: 196Reputation: 196
Actually i think the problem was with the init system and im not the only one seeing it.

https://lists.debian.org/debian-user.../msg01366.html

Quote:
On 10/15/2014 11:53 AM, Don Armstrong wrote:
On Wed, 15 Oct 2014, Jape Person wrote:
From dmesg ...[ 4.853751] systemd-gpt-auto-generator[154]: Failed to determine partition table type of /dev/sda: Input/output error [ 4.854298] systemd[151]: /lib/systemd/system-generators/systemd-gpt-auto-generator failed with error code 1. ... and later on ... [12650.204616] systemd-gpt-auto-generator[7555]: Failed to determine partition table type of /dev/sda: Input/output error ... I looked in the BTS and couldn't even find a package named systemd-gpt-auto-generator, much less a bug that had been filed for it. I guess it's a routine or function name?
It's part of systemd; it generates rules to mount partitions from GPT partition tables without needing to express them in /etc/fstab. [See man systemd-gpt-auto-generator for details.]
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] sda drive to sdb, so new hdd can become sda? irgunII Slackware 5 03-07-2014 08:38 AM
cant boot sdb2 (win7); sdb is usb 3.0 externel drive; grub is on sda; ununun Linux - General 11 01-02-2012 01:27 PM
[SOLVED] Grub: If exists sdb, then boot sdb, else sda defaultyeti Linux - Desktop 6 06-28-2011 02:38 AM
sda / sdb after boot anika.ella Linux - Newbie 1 04-29-2011 10:59 AM
Just installed F9 on sdb but lost the ability to boot F7 on sda Iltbreg Fedora 2 06-09-2008 12:26 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 08:12 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration