upgrading 9.0 to 9.1 comes up with /dev/hda instead of /dev/hde error...
hi there, have a suse 9.0 test system running on an asus k8v-deluxe board. some old ide drive attached to the primary onboard (non-raid) via chipset. in 9.0 the drive is /dev/hda, about 4 gigs in size. now then i insert the 9.1 dvd, and select update installed system, yast2 gives me some mount errors, and complains that /etc/fstab displays /dev/hda although the drive is actually /dev/hde it says. so whats wrong here? did some device numbering mechanisms changed with the new kernel 2.6? i cant make yast2 mount the drive no matter what i do. thought 9.0->9.1 would be less hassle ;) thanks, andy
----- Original Message ----- now then i insert the 9.1 dvd, and select update installed system, yast2 gives me some mount errors, and complains that /etc/fstab displays /dev/hda although the drive is actually /dev/hde it says.
yast2 points me to a support database article concerning SATA stuff, but that doesnt apply to this case i think, since i dont use sata drives/stuff, or am i mistaken? the ide controller on this board is made by via, and comes with the via chipset: http://www.asus.com/prog/spec.asp?m=K8V%20Deluxe&langs=01 yast2 points me to http://portal.suse.com/sdb/en/2004/01/sata.html so how can i mount my old 9.0 installation and make 9.1 upgrading it? would editing the installed 9.0 fstab before booting the 9.1 dvd help in any way? any workarounds? thanks, andy
"Andreas Bittner"
----- Original Message ----- now then i insert the 9.1 dvd, and select update installed system, yast2 gives me some mount errors, and complains that /etc/fstab displays /dev/hda although the drive is actually /dev/hde it says.
yast2 points me to a support database article concerning SATA stuff, but that doesnt apply to this case i think, since i dont use sata drives/stuff, or am i mistaken? the ide controller on this board is made by via, and comes with the via chipset:
But you have Sata controllers in your systems I assume...
http://www.asus.com/prog/spec.asp?m=K8V%20Deluxe&langs=01
yast2 points me to http://portal.suse.com/sdb/en/2004/01/sata.html
so how can i mount my old 9.0 installation and make 9.1 upgrading it? would editing the installed 9.0 fstab before booting the 9.1 dvd help in any way? any workarounds?
Two ways: via rescue system - boot rescue system - mount root partition - change fstab - umount - reboot or: - boot 9.0 - change fstab - reboot and then start again Just change everywhere /dev/hda to /dev/hdg or whatever... Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
"Andreas Bittner"
hi there,
have a suse 9.0 test system running on an asus k8v-deluxe board. some old ide drive attached to the primary onboard (non-raid) via chipset.
in 9.0 the drive is /dev/hda, about 4 gigs in size.
now then i insert the 9.1 dvd, and select update installed system, yast2 gives me some mount errors, and complains that /etc/fstab displays /dev/hda although the drive is actually /dev/hde it says.
so whats wrong here? did some device numbering mechanisms changed with the new kernel 2.6? i cant make yast2 mount the drive no matter what i do.
Just change the fstab manually and then reboot... The message should have contained a reference to an sdb article on our portal.
thought 9.0->9.1 would be less hassle ;)
This is a fallout of our proper support for SATA (or better: The way libata works in kernel 2.6) :-( Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Wednesday 28 April 2004 12:16, Andreas Bittner wrote:
hi there,
have a suse 9.0 test system running on an asus k8v-deluxe board. some old ide drive attached to the primary onboard (non-raid) via chipset.
in 9.0 the drive is /dev/hda, about 4 gigs in size.
now then i insert the 9.1 dvd, and select update installed system, yast2 gives me some mount errors, and complains that /etc/fstab displays /dev/hda although the drive is actually /dev/hde it says.
so whats wrong here? did some device numbering mechanisms changed with the new kernel 2.6? i cant make yast2 mount the drive no matter what i do.
thought 9.0->9.1 would be less hassle ;)
I had a similar problem when I went from a 2.4 kernel to a 2.6 kernel. My SATA and ATA drives were "swapped". On the grub boot command line I added: ide=reverse And the drives where in the same order as they were under the 2.4 kernel. Maybe this solves your problem as well ?
thanks, andy
Christian
I had a similar problem when I went from a 2.4 kernel to a 2.6 kernel. My SATA and ATA drives were "swapped".
ok so i simply edited two lines /etc/fstab from /dev/hda1 and /dev/hda2 to /dev/hde1 and /dev/hde2 so now suse 9.1 performs the updates, and right now at the very end, it comes up with grub (0.94) error: --- root (hd0,1) error 21: selected disk does not exist install --stage2=/boot/grub/stage2 /boot/grub/stage1 d (hd0) /boot/grub/stage2 0x8000 (hd0,1) /boot/grub/menu.lst error 12: invalid device requested quit ---- so now what :(
so now suse 9.1 performs the updates, and right now at the very end, it comes up with grub (0.94) error:
--- root (hd0,1)
error 21: selected disk does not exist install --stage2=/boot/grub/stage2 /boot/grub/stage1 d (hd0) /boot/grub/stage2 0x8000 (hd0,1) /boot/grub/menu.lst
error 12: invalid device requested quit
ok after the error message, turns out that the bootloader install part of yast2 still had /dev/hda and so forth in his configuration. i exchanged /dev/hda to /dev/hde there. then the installer was able to install grub to the harddisk. but now when the new updated system tries to boot, grub immediately gives me errors that it cannot find some bitmap (the graphical background of suse during bootup or something), then only displays the text-mode menue with linux, memtest rescue and so forth and when trying to boot linux it gives me more errors: booting 'linux' kernel (null)/boot/vmlinuz root=/dev/hde2 vga=0x314 splash=silent console=tty0 desktop resume=/dev/hde1 showopts error 23: error while parsing number press any key to continue .... ---- then the grub textmode menue starts over again. the entries linux failsafe and memtest all give me this very error, the entry floppy tries to access the floppy drive. ---- any hints? thanks, andy
any hints?
i tried to make yast2 repair the already installed system (bootloader, and so forth) and after it did the automatic checks and repairs, the 9.0->9.1 upgraded system now boots all right. it seems that the bootlogo has also reappeared and been installed correctly. during the first bootup some cpufreqd or some similar service failed, and after login to kde some little window also complained about that. after a second bootup of that box, this error doesnt show up any more but there is a different error now: ----- <notice>startproc: execve (/usr/sbin/cpufreqd) [ /usr/sbin/cpufreqd -d ], [ CONSOLE=/dev/console TERM=linux SHELL=/bin/sh progress=35 INIT_VERSION=sysvinit-2.85 RED IRECT=/dev/tty1 COLUMNS=92 PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin vga=0x314 RUNLEVEL=5 PWD=/ PREVLEVEL=N LINES=32 SHLVL=2 splash=silent sscripts=46 _=/s bin/startproc DAEMON=/usr/sbin/cpufreqd ] Starting cpufreqd done Error: Could not open file for writing: /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor Error: No such file or directory ---- i have to admit, that i am somewhat frustrated with suse lately, i very rarely had unproblematic installations, not even clean ones for testing very basic standard/older stuff that actually shouldnt do any harm. most of the times its installation woes and yast crashes and/or problems. how should a basic clueless user (maybe i also belong amongst these :) handle suse/linux when facing such problems. maybe new releases of suse would need to get better/more/public testing before releasing stuff to the mass market. thanks, andy
participants (3)
-
Andreas Bittner -
Andreas Jaeger -
Christian Røsnes