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 - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-02-2011, 04:34 AM   #1
Locklear
LQ Newbie
 
Registered: Oct 2010
Distribution: msdos
Posts: 14

Rep: Reputation: 0
Question Grub2 and slackware64 13.37


Hello, I installed slackware64 13.37 in an additional partition installing boot in the root and leaving grub2 of my first distro to manage distros.

After an update-grub I try to run slack (generic and huge kernels) but I have kernel panic of this type:

Kernel panic - not syncing:VFS:Unable to mount root fs on unknown-block(0,0)

How can I change my grub.cfg to run slackware??

These my actual entries for slackware:

Quote:
menuentry "Slackware 13.37 (2.6.37.6) (Generic)" {
insmod part_msdos
insmod ext2
set root='(hd2,msdos9)'
search --no-floppy --fs-uuid --set eee93b3a-25ae-446b-8eeb-f9b676a336ad
linux /boot/vmlinuz-generic-2.6.37.6 root=UUID=eee93b3a-25ae-446b-8eeb-f9b676a336ad
}
menuentry "Slackware 13.37 (2.6.37.6) (Huge)" {
insmod part_msdos
insmod ext2
set root='(hd2,msdos9)'
search --no-floppy --fs-uuid --set eee93b3a-25ae-446b-8eeb-f9b676a336ad
linux /boot/vmlinuz-huge-2.6.37.6 root=UUID=eee93b3a-25ae-446b-8eeb-f9b676a336ad
}

Thanks for helping me

Last edited by Locklear; 05-02-2011 at 04:38 AM.
 
Old 05-02-2011, 05:49 AM   #2
Locklear
LQ Newbie
 
Registered: Oct 2010
Distribution: msdos
Posts: 14

Original Poster
Rep: Reputation: 0
I add:

I created an initrd with this command:

mkinitrd -c "$(/usr/share/mkinitrd/mkinitrd_command_generator.sh -r)"

from this thread:
http://www.linuxquestions.org/questi...928/page2.html

And adding the:
initrd /boot/initrd.gz
line to the grub.cfg for the generic kernel entry

Huge kernel still can't running with the same kernel panic.

Generic kernel stop with this error:
Quote:
/boot/initrd.gz:Loading kernel modules from initrd image:
mount:mounting /dev/sda8 on /mnt failed:No such device
ERROR:No /sbin/init found on rootdev (or not mounted).Trouble ahead.
You can try to fix it.Type 'exit' when things are done.
(same as the thread linked)

I only can run with the USB stick created from slack installation

Last edited by Locklear; 05-02-2011 at 05:51 AM.
 
Old 05-02-2011, 06:08 AM   #3
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,148
Blog Entries: 2

Rep: Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886
Please post the output of
Code:
fdisk -l
blkid
Both programs must be run as root.
 
Old 05-02-2011, 06:40 AM   #4
Locklear
LQ Newbie
 
Registered: Oct 2010
Distribution: msdos
Posts: 14

Original Poster
Rep: Reputation: 0
Here you have the contents:

Quote:
bash-4.1# fdisk -l

Disk /dev/sda: 500.1 GB, 500106780160 bytes
255 heads, 63 sectors/track, 60801 cylinders, 976771055 sectores en total
Units = sectores of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Identificador del disco: 0xf414dd3e

Disposit. Inicio Comienzo Fin Bloques Id Sistema
/dev/sda1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
/dev/sda2 206848 405805679 202799416 7 HPFS/NTFS/exFAT
/dev/sda3 405805680 976767119 285480720 7 HPFS/NTFS/exFAT

Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, 976773168 sectores en total
Units = sectores of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Identificador del disco: 0xa9dda9dc

Disposit. Inicio Comienzo Fin Bloques Id Sistema
/dev/sdc1 63 321299 160618+ 83 Linux
/dev/sdc2 321300 418236209 208957455 83 Linux
/dev/sdc3 418236210 426525749 4144770 82 Linux swap
/dev/sdc4 * 426525811 976771071 275122630+ 5 Extendida
/dev/sdc5 426525813 447008624 10241406 83 Linux
/dev/sdc6 447008688 467491499 10241406 83 Linux
/dev/sdc7 467492864 508457249 20482193 83 Linux
/dev/sdc8 508457313 549422999 20482843+ 83 Linux
/dev/sdc9 549423063 590388749 20482843+ 83 Linux

Disk /dev/sdd: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders, 78165360 sectores en total
Units = sectores of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Identificador del disco: 0x44da44d9

Disposit. Inicio Comienzo Fin Bloques Id Sistema

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, 976773168 sectores en total
Units = sectores of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Identificador del disco: 0x0c1b0c1a

Disposit. Inicio Comienzo Fin Bloques Id Sistema
/dev/sdb1 2048 976769023 488383488 7 HPFS/NTFS/exFAT

Disco /dev/sde: 8010 MB, 8010072064 bytes
247 heads, 62 sectors/track, 1021 cylinders, 15644672 sectores en total
Units = sectores of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Identificador del disco: 0xb0bcd68e

Esto no parece una tabla de particiones
Probablemente ha seleccionado el dispositivo que no era.
Disposit. Inicio Comienzo Fin Bloques Id Sistema
/dev/sde1 ? 3223366781 3470046704 123339962 78 Desconocido
/dev/sde2 ? 432871117 1208554935 387841909+ 10 OPUS
/dev/sde3 ? 1869562563 3788792630 959615034 8b Desconocido
/dev/sde4 ? 4718592 4784127 32768 a OS/2 Boot Manager

Las entradas de la tabla de particiones no están en el orden del disco
Quote:
bash-4.1# blkid
/dev/sdc9: UUID="6c69d2d5-ba40-4d5c-ba9a-e92e2cbc776b" TYPE="ext4"
/dev/sda1: LABEL="Reservado para el sistema" UUID="9C220334220312C6" TYPE="ntfs"
/dev/sda2: LABEL="Win7" UUID="82E80793E807849F" TYPE="ntfs"
/dev/sda3: LABEL="Datos" UUID="9276BF3676BF1A45" TYPE="ntfs"
/dev/sdc1: UUID="6a427396-65c8-45f4-a9f6-05579b8b78cf" TYPE="ext2"
/dev/sdc2: UUID="c4beb089-c963-4d2f-86a0-2fc455aa0bfd" TYPE="ext4"
/dev/sdc3: UUID="2cd99001-fa88-4f5b-97a7-c4a99996824e" TYPE="swap"
/dev/sdc5: UUID="2eaf3cb2-f098-4af6-82f0-2097779ed785" TYPE="ext4"
/dev/sdc6: UUID="9ece670d-25f7-46d3-a716-639570a5d8fb" TYPE="ext4"
/dev/sdc7: UUID="c54d8926-5256-4b07-9c6c-ba24a9f9c949" TYPE="ext4"
/dev/sdc8: LABEL="suse" UUID="8e94cb21-8fdc-4d6a-bb04-30607df63e06" TYPE="ext4"
/dev/sdb1: LABEL="Datos" UUID="BAF8D42EF8D3E723" TYPE="ntfs"
/dev/sde: SEC_TYPE="msdos" LABEL="USBSLACK" UUID="D543-57C3" TYPE="vfat"
bash-4.1#
PS: the UUID have changed because I reinstalled slack (formatting partition) to generate the USB. I also updated grub.cfg to the new UUID. Same errors

Actual entries in grub are:

Quote:
menuentry "Slackware 13.37 (2.6.37.6) (Generic)" {
insmod part_msdos
insmod ext2
set root='(hd2,msdos9)'
search --no-floppy --fs-uuid --set 6c69d2d5-ba40-4d5c-ba9a-e92e2cbc776b
linux /boot/vmlinuz-generic-2.6.37.6 root=UUID=6c69d2d5-ba40-4d5c-ba9a-e92e2cbc776b
initrd /boot/initrd.gz
}
menuentry "Slackware 13.37 (2.6.37.6) (Huge)" {
insmod part_msdos
insmod ext2
set root='(hd2,msdos9)'
search --no-floppy --fs-uuid --set 6c69d2d5-ba40-4d5c-ba9a-e92e2cbc776b
linux /boot/vmlinuz-huge-2.6.37.6 root=UUID=6c69d2d5-ba40-4d5c-ba9a-e92e2cbc776b
}

Last edited by Locklear; 05-02-2011 at 06:45 AM.
 
Old 05-02-2011, 06:56 AM   #5
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,148
Blog Entries: 2

Rep: Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886
I can't see any reason why your system shouldn't boot. You mentioned that you edited grub.cfg manually. Why aren't you using the update-grub command? Any changes to that file will get lost the next time the system launches update-grub because of an kernel update.
Please try that command (after making a backup of grub.cfg) and compare the newly generated file to your own entries.
 
Old 05-02-2011, 08:22 AM   #6
Locklear
LQ Newbie
 
Registered: Oct 2010
Distribution: msdos
Posts: 14

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by TobiSGD View Post
You mentioned that you edited grub.cfg manually. Why aren't you using the update-grub command?
Because at the first time it don't worked, so I decided to do it manually.

But now I just tried another time, and now it can run with the huge kernel... but it still can't run with the generic kernel giving me the same errors.

Generic kernel without initrd give a kernel panic
Generic kernel with initrd give the sdc9 error.

This is grub.cfg after update-grub and manually adding initrd to the generic kernel entry.:

Quote:
menuentry "Slackware Linux (Slackware 13.37.0) (on /dev/sdc9)" {
insmod part_msdos
insmod ext2
set root='(hd2,msdos9)'
search --no-floppy --fs-uuid --set 6c69d2d5-ba40-4d5c-ba9a-e92e2cbc776b
linux /boot/vmlinuz-generic-2.6.37.6 root=/dev/sdc9
initrd /boot/initrd.gz
}
menuentry "Slackware Linux (Slackware 13.37.0) (on /dev/sdc9)" {
insmod part_msdos
insmod ext2
set root='(hd2,msdos9)'
search --no-floppy --fs-uuid --set 6c69d2d5-ba40-4d5c-ba9a-e92e2cbc776b
linux /boot/vmlinuz-huge-2.6.37.6 root=/dev/sdc9
}
It seems like I have errors with initrd. Now I will search more things about initrd, but if anyone can help here, it would be great.

Thanks
 
  


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
upgrading slackware64 13.1 multilib to slackware64 -current multilib Cultist Slackware 4 03-12-2011 09:04 AM
[SOLVED] GRUB2 after a minor update of GRUB2 /boot prefix no longer needed?? wikapuki Linux - Software 1 10-24-2010 02:39 PM
grub2 psmurthy Linux - Newbie 2 03-16-2010 11:20 AM
Updating from Slackware64-current to Slackware64 13. glore2002 Slackware 4 08-28-2009 06:50 PM
[SOLVED] Slackware64-C client wont detect Slackware64-C Samba server slackass Slackware 5 08-07-2009 11:23 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

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

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