LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 03-18-2014, 07:27 AM   #1
photocdn
LQ Newbie
 
Registered: Jul 2011
Posts: 6

Rep: Reputation: Disabled
Lilo error after updating 13.37 installation


Hi Everyone,

I just recently updated my version 13.37 installation using slackpkg upgrade-all.
It notified me to run lilo, and I blindly did and rebooted just for fun, but now the system no longer boots up.

My installation is entirely on LVM, including boot. I got up and running on the install disk, mounted up the partitions and tried to run lilo (after a chroot) and this is the error I'm seeing:

Linux experimental device 0x04x needs to be defined

I'm not sure what is going on here or what i need to do to fix it.
Any help would be greatly appreciated.

thanks
steven
 
Old 03-18-2014, 08:32 AM   #2
JackHair
Member
 
Registered: Aug 2009
Location: Netherlands
Distribution: OpenSuse 13.1
Posts: 80

Rep: Reputation: 16
A quick Google on the error you get gives this as 1st hit:
http://comments.gmane.org/gmane.comp...vm.devel/13832
Maybe it solves it for you as well?
 
Old 03-18-2014, 09:02 AM   #3
photocdn
LQ Newbie
 
Registered: Jul 2011
Posts: 6

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by JackHair View Post
A quick Google on the error you get gives this as 1st hit:
http://comments.gmane.org/gmane.comp...vm.devel/13832
Maybe it solves it for you as well?
Thanks for the reply. I found that page as well, but it's hard to tell if it's the same issue.
I tried adding disk=0x80 and max-partitions=15 in lilo.conf but it didn't help.
 
Old 03-18-2014, 01:11 PM   #4
calrogman
LQ Newbie
 
Registered: Mar 2014
Distribution: Slackware!
Posts: 9

Rep: Reputation: 3
Hi.

Run the following before chroot:
Code:
mount --rbind /dev /mnt/dev
Make sure you rebuild your initrd next time!
 
Old 03-18-2014, 01:37 PM   #5
enorbet
Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware 14 is Main OpSys on Main PC, 2ndary are OpenSuSe 13 and SolydK
Posts: 734

Rep: Reputation: 340Reputation: 340Reputation: 340Reputation: 340
Quote:
Originally Posted by calrogman View Post
<snip>
Make sure you rebuild your initrd next time!
or eliminate the need.
 
Old 03-18-2014, 08:46 PM   #6
photocdn
LQ Newbie
 
Registered: Jul 2011
Posts: 6

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by calrogman View Post
Hi.

Run the following before chroot:
Code:
mount --rbind /dev /mnt/dev
Make sure you rebuild your initrd next time!
Unfortunately, that isn't working either. I rebuilt the initrd pretty much using the instruction in the README,
but I added the -L, and lilo still gives the same error. Even removing initrd entry from lilo.conf, still gives the same error.

Not sure where to go next...
 
Old 03-18-2014, 10:12 PM   #7
photocdn
LQ Newbie
 
Registered: Jul 2011
Posts: 6

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by photocdn View Post
Unfortunately, that isn't working either. I rebuilt the initrd pretty much using the instruction in the README,
but I added the -L, and lilo still gives the same error. Even removing initrd entry from lilo.conf, still gives the same error.

Not sure where to go next...
Well, I got lilo to run successfully, but the system still doesn't boot.
After booting into the install disk (usb stick), I started setup and mounted the LVM partitions for /, /home and 2 others I have in /opt.
I then did
Code:
mount --rbind /dev /mnt/dev
but did not chroot. I ran lilo in /mnt/etc like this:
Code:
lilo -C ./lilo.conf
and it ran fine, no error (Added Linux). Unfortunately, the systems still doesn't boot. It will startup up, I have the splash screen and the OS chooser (there's only linux), and when it launches into linux, I get the first line of dots print out and it halts. I usually would get a few lines and then things would start loading.
 
Old 03-19-2014, 07:58 PM   #8
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,578

Rep: Reputation: 468Reputation: 468Reputation: 468Reputation: 468Reputation: 468
So, this is in a VM of some type? Is this still a 13.37 system or did you upgrade to a newer version?
 
Old 03-19-2014, 09:02 PM   #9
photocdn
LQ Newbie
 
Registered: Jul 2011
Posts: 6

Original Poster
Rep: Reputation: Disabled
Post

Quote:
Originally Posted by photocdn View Post
Well, I got lilo to run successfully, but the system still doesn't boot.
After booting into the install disk (usb stick), I started setup and mounted the LVM partitions for /, /home and 2 others I have in /opt.
I then did
Code:
mount --rbind /dev /mnt/dev
but did not chroot. I ran lilo in /mnt/etc like this:
Code:
lilo -C ./lilo.conf
and it ran fine, no error (Added Linux). Unfortunately, the systems still doesn't boot. It will startup up, I have the splash screen and the OS chooser (there's only linux), and when it launches into linux, I get the first line of dots print out and it halts. I usually would get a few lines and then things would start loading.
I got it figured out and I'm back in business

My system has 3 disks, a 40G, 1TB and 2TB. The 40G is my system disk, the other 2 are data disks plugged on a different controller.
The 40G is plugged into sata0 on the motherboard, so thats the disk that gets booted, but it was showing up as /dev/sdc, not sda (which is what I would have expected). My lilo.conf had /dev/sda as the boot entry, so it wasn't getting written to the proper MBR !

There's two things I'm not sure of. Is it normal, we can't count on the ordering of the disk names to follow (what I think is) the physical ordering of the controllers ? And, because it's been a long time since I originally setup this system, did my lilo.conf change during the upgrade, meaning I originally had the "out of order" disk specified on the boot entry or did the ordering of the disks change in linux ?

Hope I'm explaining myself well enough, in case someone else ever hits this problem.

And one final thing, I also did this
Code:
mount --rbind /proc /mnt/proc
prior to the chroot, did the chroot /mnt and then ran lilo. I'm not sure it was actually needed to run properly, but thats what I had.

Cheers everyone !
Steven
 
Old 03-20-2014, 07:08 AM   #10
photocdn
LQ Newbie
 
Registered: Jul 2011
Posts: 6

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Richard Cranium View Post
So, this is in a VM of some type? Is this still a 13.37 system or did you upgrade to a newer version?
Hi, sorry I didn't see this question - it isn't a VM and yes, it's still 13.37 (I just wanted to patch the system).

Steven
 
Old 03-20-2014, 09:19 AM   #11
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,578

Rep: Reputation: 468Reputation: 468Reputation: 468Reputation: 468Reputation: 468
Not a problem, you solved it yourself.

My machine has an Adaptec AIC-7892A U160/m SCSI controller. The huge kernel would initialize that controller first, then the on-board SATA controller. The generic kernel wouldn't have the adaptec kernel module integrated, so it would initialize the on-board SATA controller first then the initrd would load the adaptec module.

End result was the drives being renamed depending depending which kernel I used to boot. Perhaps this (or something similar) is what happened to you.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
lilo gives an error on installation oathkeeper Slackware - Installation 6 10-21-2007 03:24 PM
Error output with LILO while updating my lilo.config adilturbo Linux - General 4 10-17-2006 05:10 PM
Lilo installation error Nikon01 Slackware 5 08-31-2004 11:28 AM
Updating Lilo Error Message Cozz23 Linux - General 1 02-19-2004 02:52 PM
Problem with Lilo not updating (yes I ran lilo after changing the conf) webguy Linux - General 2 06-24-2001 08:12 PM


All times are GMT -5. The time now is 07:24 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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration