LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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-27-2013, 03:39 PM   #1
Rip van Vinkle
LQ Newbie
 
Registered: Dec 2010
Location: Barcelona - Spain
Distribution: aptosid, Salix
Posts: 4

Rep: Reputation: 0
Problem with salix. Grub2 culprit


After a lot of fight against Grub2 and questions not answered in other forums, I come here to ask for help at wise people of LQ. I hope this is the correct sub-forum.

My computer has two Linux OS inside: aptosid, a Debian derivative, and Salix, a Slackware based, as you know. As a consequence of an aptosid's dist-upgrade, I cannot boot salix.

It is, obviously, a Grub2 issue, which is the bootmanager of aptosid, having salix as second OS. In my battles with Grub2 I've learned (in some forum; don't ask me what forum, I don't remember) that the script /etc/grub.d/30_os-prober is not always reliable. Because that, I've annulled the mode "x" of this script and configured 40_custom instead. Here is as it looks now:

Code:
lluis1@aptosidbox1:~$ cat /etc/grub.d/40_cus*
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
    menuentry "Salix-Slackware 13.37 (on /dev/sda3)" --class gnu-linux --class gnu --class os {
       insmod part_msdos
       insmod ext2
       set root='(hd0,msdos3)'
       search --no-floppy --fs-uuid --set=root 17405d87-e0a8-4b36-94cd-27682c750d50
       linux /boot/vmlinuz root=UUID=17405d87-e0a8-4b36-94cd-27682c750d50
    }

lluis1@aptosidbox1:~$
As far as I'm able to see, this configuration must go, but if I try to boot Salix-Slackware 13.37, I get:
Code:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (0,0)
For more information I've run bootinfoscript, which results are here

Any advice will be very appreciated.

Rip van Vinkle
 
Old 03-27-2013, 04:12 PM   #2
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,192

Rep: Reputation: Disabled
This is a Slackware forum. Slackware is not Salix. Slackware also does not contain grub2. Perhaps you are better off finding help in the Salix forum : http://www.salixos.org/forum/

Eric
 
4 members found this post helpful.
Old 03-27-2013, 04:27 PM   #3
Rip van Vinkle
LQ Newbie
 
Registered: Dec 2010
Location: Barcelona - Spain
Distribution: aptosid, Salix
Posts: 4

Original Poster
Rep: Reputation: 0
Apologies if I've bothered you. I think you don't need to be impolite.

Of course, I've asked at salix forum, but nobody could find a solution. If salix is a derivative of Slackware, then the knowledge of Slackware is applicable to salix.

And in the first paragraph I've said "I hope this is the correct sub-forum". If not, please said me what other subforum is.
 
Old 03-27-2013, 04:39 PM   #4
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 858

Rep: Reputation: 1668Reputation: 1668Reputation: 1668Reputation: 1668Reputation: 1668Reputation: 1668Reputation: 1668Reputation: 1668Reputation: 1668Reputation: 1668Reputation: 1668
Quote:
Originally Posted by Rip van Vinkle View Post
Apologies if I've bothered you. I think you don't need to be impolite.
The response you got looked pretty factual to me.

Quote:
Of course, I've asked at salix forum, but nobody could find a solution. If salix is a derivative of Slackware, then the knowledge of Slackware is applicable to salix.
Not when you're asking about a component that Slackware has never included. Obviously that wouldn't be derived from Slackware in any way.

Quote:
And in the first paragraph I've said "I hope this is the correct sub-forum". If not, please said me what other subforum is.
I have no idea. Good luck with your search for an answer, though.
 
1 members found this post helpful.
Old 03-27-2013, 04:50 PM   #5
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,806

Rep: Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810
I would ask in Linux General (this reads like a Grub2 issue). The Slackware forum is the least appropriate IMHO given that Slackware is one of the few that does not include/use Grub2.
 
Old 03-27-2013, 05:41 PM   #6
w1k0
Senior Member
 
Registered: May 2008
Location: Poland
Distribution: Slackware, Mint
Posts: 1,240

Rep: Reputation: 196Reputation: 196
Rip van Vinkle,

I published here my experience concerning GRUB2 in Linux Mint and LILO in Slackware Linux.

Since Salix is a derivative of Slackware I assume it uses LILO. LILO is much more reliable in my opinion than GRUB. So you could try to install LILO on MBR and GRUB Legacy on the partition with aptosid using the method that I described in the mentioned post. Then use LILO to run both your systems. That should work.
 
Old 03-27-2013, 05:53 PM   #7
JWJones
Member
 
Registered: Jun 2009
Location: Cascadia
Distribution: Slackware, LinuxBBQ, OpenBSD, Mac OSX
Posts: 723

Rep: Reputation: 185Reputation: 185
Yup, I'd say grub2 or aptosid issue, as, like Slackware, Salix uses lilo, rather than grub.
 
Old 03-27-2013, 06:03 PM   #8
w1k0
Senior Member
 
Registered: May 2008
Location: Poland
Distribution: Slackware, Mint
Posts: 1,240

Rep: Reputation: 196Reputation: 196
eyeofliberty,

The issue which I described in the mentioned post concerns GRUB2 in Linux Mint. I think that the similar method will solve the problem with GRUB2 in aptosid.
 
Old 03-27-2013, 06:41 PM   #9
Beelzebud
Member
 
Registered: Oct 2010
Distribution: Arch & Slackware
Posts: 95

Rep: Reputation: 22
Have you actually tried using os-prober, or did you just assume it wouldn't work because someone said it wouldn't?
 
Old 03-28-2013, 09:04 AM   #10
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,441

Rep: Reputation: 409Reputation: 409Reputation: 409Reputation: 409Reputation: 409
One of the nice things about grub and grub2 is that you can interactively run boot loader commands during the boot so that you can figure out exactly what's wrong with your configuration file and boot the system so you can make the changes. Win win!

Judging from the error message, I'd advise you to put the boot process in interactive mode and list out your disk partitions. I'm pretty sure that (hd0,msdos3) isn't correct (or isn't an ext2 partition).
 
Old 03-28-2013, 04:12 PM   #11
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 12,125

Rep: Reputation: 985Reputation: 985Reputation: 985Reputation: 985Reputation: 985Reputation: 985Reputation: 985Reputation: 985
An altogether unsatisfactory and unhelpful thread until that last post.
By the time the message the OP sees is issued the boot-loader (whatever it is) has done it's job. That is a kernel message from a Slackware derived distro. You'd think the Slack community would try to help, but apparently not.

Unless things are different in Salix, you will need to include an initrd to get all the support pre-loaded for the kernel. Add it immediately after the kernel line.
That grub setup does look a mess - open another thread for that if you want; general as suggested will probably be a better choice.
 
Old 03-28-2013, 05:07 PM   #12
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 858

Rep: Reputation: 1668Reputation: 1668Reputation: 1668Reputation: 1668Reputation: 1668Reputation: 1668Reputation: 1668Reputation: 1668Reputation: 1668Reputation: 1668Reputation: 1668
Quote:
Originally Posted by syg00 View Post
An altogether unsatisfactory and unhelpful thread until that last post.
By the time the message the OP sees is issued the boot-loader (whatever it is) has done it's job. That is a kernel message from a Slackware derived distro. You'd think the Slack community would try to help, but apparently not.
We don't ship grub2. The kernel message (almost certainly not our kernel, either) is simply saying that it couldn't mount root, very likely because the initrd or the boot loader were not set up properly. I don't know, but suspect that the initrd construction is different from what we do as well.

Salix may have forked from Slackware, but it differs in a lot of ways. This is one of them.

Sorry you weren't satified, but asking for support in the wrong place (from a project that has nothing to do with the software in question) isn't likely to produce helpful answers.
 
Old 03-28-2013, 05:21 PM   #13
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,806

Rep: Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810
They (SalixOS) use a huge kernel by default and do not encourage (in any of their documentation) the use of a generic kernel with initrd (so I suspect most users do not bother). That all said, I fully agree that this isn't the right forum and should either be in general or in Salix's own forum.
 
Old 03-29-2013, 01:12 AM   #14
jd3v
LQ Newbie
 
Registered: Dec 2012
Location: Indiana
Distribution: Slackware, Debian
Posts: 1

Rep: Reputation: Disabled
Quote:
Originally Posted by Richard Cranium View Post
I'm pretty sure that (hd0,msdos3) isn't correct...
I would agree. According to your Boot Info script, that's a swap partition. Your salix root partition is on the second hard drive (hd1,3), not the first (hd0,3).

I would recommend you revisit/reevaluate the documentation used to create your custom entry. Or run os-prober and let that take care of it for you.
 
1 members found this post helpful.
Old 03-29-2013, 03:05 PM   #15
Rip van Vinkle
LQ Newbie
 
Registered: Dec 2010
Location: Barcelona - Spain
Distribution: aptosid, Salix
Posts: 4

Original Poster
Rep: Reputation: 0
Finally, a salix mate has advised me in the right way.

Thanks to everybody who has tried to help me.

Van Vinkle
 
  


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
kcm-grub2 - No valid GRUB2/BURG installation could be detected cristi92b Linux - Newbie 2 06-14-2012 08:01 AM
Problem running salix linuxlover2 Linux - Distributions 1 05-23-2011 07:25 PM
[SOLVED] Problem with excessive RAM usage and no obvious culprit Dralnu Linux - General 12 05-13-2011 07:27 PM
[SOLVED] GRUB2 after a minor update of GRUB2 /boot prefix no longer needed?? wikapuki Linux - Software 1 10-24-2010 02:39 PM
who is the culprit? (traceroute problem) domeili Linux - Networking 1 11-12-2003 09:44 AM


All times are GMT -5. The time now is 04:01 AM.

Main Menu
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