SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
hi there,
i decided to do couple of updates recently and after reboot ended up with following msg:
Code:
loading ext3
resume device /dev/mapper/nvidia_bdbeadct_part2 not found (ignoring)
waiting for device /dev/mapper/nvidia_bdbeadct_part2 to appear....
not found ... exiting to /bin/sh
_
prompt sign is blinking but U cant enter any command
i've been looking for some answer and it seems like its problem with partitions nameing.
how can i fix it if i cant login into any part?
system is 64bit but cant get U much info about update i've done except i was updating only couple of programs (after last experience with kernel update, nvidia drivers, and compiz i was avoiding updating any of these that could give me troubles again)
also i give couple of kernel options at boot that i've found in othere posts like:
irqpoll
pci=nomsi
but none of it made any changes...
also one of the first error msg i've noticed a msg (cant remember excacly where i've seen it):
e2fsck -b 8193 /dev/mapper/nvidia_ggccecaa_part7
sata1: sata linkup 1.5gbps (sstatus 113 scontrol 300)
gc timeout (cmd 0xec)
failed to identify
what you probably have done during your update was installing a driver for your nvidia card which registered itself but did not install correctly. this makes the x server fail to init correctly. try downloading a new driver from www.nvidia.com. it will be a file with the extension .run to install it you must be in cli mode and have the x server stopped. type the following as root: "sh NvidiaDriverName.rum". the installation wizard will show up, just follow the instructions and try again
i dont really think thats the case,
i have touched neither kernel nor x.org nor nvidia driver itself.
it doesnt prompt about nvidia card, its about nvidia sata hdd controlers so doesnt seems like graphic card problem.
The e2fsck -b 8193 /dev/mapper/nvidia_ggccecaa_part7 line means format partition 7. The next lines may indicate a hardware or a kernel problem. Can you boot windows on your system?
My system blew up with something similar after attempting the last kernel update. Running the "repair" tool DID find my partitions :-) but it "fixed" them by turning them all into swap :-(
hi there,
thx for reply,
i can boot to windows no problem, even can browse ext3 via totalcommander plugins so im sure partition table is fine.
as said in first post can really remember which packets were updated but for sure no kernel updates were made, only thing that bothers me was some initrd(??) thing ive seen somewhere over the web. (propably that package was updated, if its possible to update it without kernel update...)
hi guys,
its been a week now since my pc is dead...
still cant find any clue to fix it...
there must be some kind of way of dealing with it.
i really dont fancy reinstalling it all...
No problem in the extract you gave. How many hard disks does your system have? Can you also post /boot/grub/menu.lst? Try to boot with noresume appended to the kernel command line in the grub menu when the system boots (when the boot menu appears, press ESC, ENTER, select opensuse 10.2, press E and edit the kernel line, press ESC, then B).
hi,
ive just noticed that my /boot/ catalouge is empty.. dont know why is that but seems like its not very good ...
anyway, i've found menu.lst file in /grub/menu.lst , here it is:
Code:
# Modified by YaST2. Last modification on Mon Mar 19 17:41:12 GMT 2007
default 6
timeout 8
gfxmenu (hd0,2)/message
###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 10.2
root (hd0,2)
kernel /vmlinuz root=/dev/mapper/nvidia_ggccecaa_part8 vga=0x317 resume=/dev/mapper/nvidia_bdbeadcf_part2 splash=silent showopts
initrd /initrd
title windows XP
rootnoverify (hd0,0)
chainloader (hd0,0)+1
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Bezpieczne uruchamianie -- openSUSE 10.2
root (hd0,2)
kernel /vmlinuz root=/dev/mapper/nvidia_ggccecaa_part8 vga=normal showopts ide=nodma apm=off acpi=off noresume edd=off 3
initrd /initrd
title SUSE Linux 10.1 (/dev/mapper/nvidia_bdbeadcf_part1)
kernel (hd1,0)/vmlinuz root=/dev/sda8 vga=0x317 resume=/dev/mapper/nvidia_bdbeadcf_part2 splash=silent showopts
initrd (hd1,0)/initrd
title windows 2
rootnoverify (hd0,0)
chainloader (hd0,0)+1
###Don't change this comment - YaST2 identifier: Original name: xen###
title XEN
root (hd0,2)
kernel /xen.gz
module /vmlinuz-xen root=/dev/mapper/nvidia_ggccecaa_part8 vga=0x317 resume=/dev/mapper/nvidia_bdbeadcf_part2 splash=silent showopts
module /initrd-xen
title Kernel-2.6.18.8-ccj45-default
root (hd0,2)
kernel /vmlinuz-2.6.18.8-ccj45-default root=/dev/mapper/nvidia_ggccecaa_part8 vga=0x317 resume=/dev/mapper/nvidia_bdbeadcf_part2 splash=silent showopts
initrd /initrd-2.6.18.8-ccj45-default
When the boot menu appears, edit the opensuse 10.2 entry, as I described above, and change root=/dev/mapper/nvidia_ggccecaa_part8 to root=/dev/sda8 and delete the resume= line. Did this help?
it worked (more or less),
ive done excacly what U've said and ended with "give root password to log in" after some errors when fsck had to check file systems.
if that will help i can re write them but first i'd like to know if thers anything to do next (after loggin in).
i was looking for /grub/menu.lst file coz thought that have to edit all the entries and put sda instead of mapper but theres no such a catologue, might be that grub entries are on some other unmounted partition, my whole /home place is also on other partition.
You will probably need to do the same to the fstab entries, i.e. change all /dev/mapper lines to /dev/sda or /dev/sdb as appropriate. The reason for all this trouble might be a bug in the latest suse kernel upgrade, if you didn't modify /boot/grub/menu.lst yourself.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
)
