after kernel upgrade slackware boots only if I pass root=/dev/sda3 when booting

zux · 12-05-2008, 08:11 AM

I switched from slack-12.1 default huge-smp kernel to a generic-2.6.27.7 from slackware-current. That changed my /dev/hda to /dev/sda.
so after a couple of reboots from slack-install cd that was fixed, but it still tries to mount /dev/hda3
and more interestingly it tries to mount it to /mnt
but passing parameter "root=/dev/sda3 ro" it boots ok (3 is my root partition)
fstab looks like this:

Code:

/dev/sda2        swap             swap        defaults         0   0
/dev/sda3	 /                ext3        defaults         1   1

and lilo.conf like this:

Code:

boot = /dev/sda
compact        # faster, but won't work on all systems.
  bitmap = /boot/slack.bmp
  bmp-colors = 255,0,255,0,255,0
  bmp-table = 60,6,1,16
  bmp-timer = 65,27,0,255

append="pci=noapic evt.default_utf8=0"
prompt
timeout = 50

vga = 773

image = /boot/vmlinuz.new
	initrd = /boot/initrd.gz
	root = /dev/sda3
	label = slack.new.1
	read-only

image = /boot/vmlinuz
  root = /dev/sda3
  label = slack
  read-only

where could it be getting the hda3 from??

keefaz · 12-05-2008, 08:18 AM

Is it the same when you boot from slack or slack.new.1 (in lilo menu)
(maybe there is an issue with the initrd.gz ?)
Did you try add the well known hda=noprobe kernel parameter ?

zux · 12-05-2008, 08:49 AM

slack.new.1 is the new 2.6.27.7 kernel
slack is 2.6.24.5 (the one that had hda3, not sda3)
hda=noprobe had the same results

I rebuilt initrd.gz a couple of times with the same results, it only contains ext3 module + dependecies

Also it shouldn't be initrd, becouse just giving the right root= parameter fixes it.
I just can't understand why it ignores the lilo root=/dev/sda3 option

zux · 12-05-2008, 09:10 AM

fixed it for now by changing this line in lilo:

Code:

append="root=/dev/sda3 pci=noapic evt.default_utf8=0"

it still seems wrong. but works

any ideas?

keefaz · 12-05-2008, 09:37 AM

I don't know, I suspected the initrd because there is init script into it that mounts the root partition I believe (so maybe this is where you see the root partition seen as hda3 mounted in mnt ?)

Maybe you have to add other modules in initrd ? (sata, scsi... I don't know)
Or it's time to build your own kernel ?

(and enable ext3 as built-in, so no more initrd)

zux · 12-05-2008, 09:50 AM

you where right after all, every time I rebuilt initrd the initrd-tree folder had been the same

after deleting it and rebuilding initrd it worked

the first initrd was built while the old kernel was loaded, therefor the hda3
thanks for leading me to the right path

and now to get back to the problem why i needed the upgrade:
http://www.linuxquestions.org/questi...uspend-688355/