Recover Update of 10.1 from power failure hard crash.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I started a SUSE Linux 10.1 upgrade from 10.0 on saturday. We had a bad weather and a car hit a power pole. My power was out for over 6 hours. I had just started and upgrade when the system died. The upgrade had installed linux-2.6.16.13-4. I have a linux-2.6.16.13-4-obj but no linux-2.6.16.13-4. When I boot the system I get ... waiting for /dev/had5 to appear: .... resume device /dev/hda5 not found (Ignoring). waiting for /dev/had6 to appear: .... not found exiting to (/bin/sh). I have searched google for "linux waiting for to appear" and tried what I could find most of them were about USB Devices and re-installing. When I boot from CD 1 or the DVD I am able to mount/use both the swap and root as /dev/hda5 and /dev/hda6. When I try to do a network install again the system hangs hard before the select /dev/hda6. When I run install and repair system I get a failure on mkinitrd that is run from the auto repair in the grub menu part of the auto repair. Auto Repair does not complain about any thing else. It does only have two packages for the base instead of the complete list. Kernel and some YaST. I tried going back to 2.6.13-15.8 with no luck. I remove all the /boot/*2.6.13-15.8 files since they were not there when I booted to the rescue system the first time. I have tried Rescue System mount /dev/hda6 /mnt swapon /dev/had5 cd /mnt chroot /mnt mkinitrd and had it fail. I then copied the /sbin from Rescue System to /lib/klibc/sbin as that what was giving me errors on mkinitrd. Then it build and installs to /boot the linux-2.6.16.13-4 files again. They are the exact same sizes each time. Sadly I did not make a backup of the system. I am able to see all my files on the disk from the rescue cd. So I have not lost any thing that I need. The disk is a 120 GB disk with 6 GB available. I tried to do a rpm --rebuilddb after the above mount and chroot. It did not help. I am not sure what else to try. Does any one have any ideas on getting this system to a state where I am able to restart the network install. I have the entire 10.1/inst-source and 10.1/non-oss-inst-source download to another system that is 10.0. I was using it for the network install. HELP? I do not know what else to try. Thanks for any ideas. - -- Boyd Gerber <gerberb@zenez.com> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQFEclXnVtBjDid73eYRAk3aAJ9MB49KrlzR4JMBdQlgXnb9TiPUmwCfc0PL eUnURAw6peKbxj8eljips90= =dB4B -----END PGP SIGNATURE-----
On Monday 22 May 2006 20:22, Boyd Lynn Gerber wrote:
Thanks for any ideas.
Hi Boyd, First, what are you losing if you just wipe the partitions and install 10.1 'from scratch'? From your description, the upgrade was begun and soon interrupted. It is no longer 10.0 *or* 10.1 but something in between... with the added complexity of manual rescue attempts and manipulated content. I'm not sure the 10.1 installer would be sophisticated enough to identify and sort all these changes out. However, if you're absolutely determined to pursue the upgrade route, given the noted anomalies, above, I'd say your best bet would be to run the 10.0 'system repair', first... let it revert the installation back to 10.0 and attempt the upgrade again. my 2 cents, Carl
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 22 May 2006, Carl Hartung wrote:
On Monday 22 May 2006 20:22, Boyd Lynn Gerber wrote:
Thanks for any ideas.
First, what are you losing if you just wipe the partitions and install 10.1 'from scratch'?
112 GB of unbacked up data, source code for projects, all company records... Stuff I can not live without. I should have made a backup but I was in a hurry and now I am in trouble for not following my own rules about backup. If I had the funds I would go an buy a large HD and problem would be solved. All I have available is a 15 GB laptop HD for testing on my laptop. The system I need to repair is my Desktop PC. At this point I am unable to install Backup Edge to backup to DVD. THis machine has both IDE and SCSI disks. On very large IDE Drive with SUSE, One drive with UnixWare and Windows 2000, cdrom burner and dvd burner. 2 2 GB SCSI HD's with UnixWare 7.1.4, SCSI CD rom, SCSI CD rom burner. The machine is a P III 667 MHz with 128 MB Memory. So I have to have the 1 GB swap to do anything with it and 10.1.
From your description, the upgrade was begun and soon interrupted. It is no longer 10.0 *or* 10.1 but something in between... with the added complexity of manual rescue attempts and manipulated content. I'm not sure the 10.1 installer would be sophisticated enough to identify and sort all these changes out.
I have no idea how long it ran. I had left it to complete un-attended. I have been able to do a test on a smaller hd with 10.0 to a 10.1 upgrade that I halted. It did not have the problem with the boot finding the partitions and swap, but was in between. I powered off at a know point. I was able to boot the mini iso and force a reinstall using update all programs if newer. It did take 3 hours to resolve all the conflicts, because of the stupid updater in 10.1 only doing one at a time. But I was able to get it to 10.1. So I am sure if I can get the system to boot without the waiting for ... to come up I can complete the install. I wish I had another drive to copy all the information off to it, then I would do a new install. If I knew how to create this situation with the boot not finding the /dev/hda5 swap and /dev/hda6 root, I think I could fix it. Not knowing how to get to this state I do not know how to undo it.
However, if you're absolutely determined to pursue the upgrade route, given the noted anomalies, above, I'd say your best bet would be to run the 10.0 'system repair', first... let it revert the installation back to 10.0 and attempt the upgrade again.
Sadly I had already tried it. With either the DL DVD from 10.0 or CD 1 I am unable to boot from them. The system goes imediately to the HD boot menu. The 10.1 CD and DVD both boot to their menues, Every option I have tried does not seem to work with the 10.0 CD/DVD. I also thought maybe able to use y2pmsh to do the upgrade as mentioned on the opensuse-factory list. The /boot/grub/menu.lst has been changed to 10.1 instead of 10.0. So the system had to get to some point that it was changed or it may have been changed from the 10.1 install/repair installed system. Any other ideas? Anyone? Thanks, - -- Boyd Gerber <gerberb@zenez.com> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQFEcpkyVtBjDid73eYRAsDPAJ4r1A56MciM3xUk8bAOf2WcApCP8gCeJMFq gchx3T0By1BSKY8ez58Q/JY= =8BT4 -----END PGP SIGNATURE-----
Boyd Lynn Gerber wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, 22 May 2006, Carl Hartung wrote:
On Monday 22 May 2006 20:22, Boyd Lynn Gerber wrote:
Thanks for any ideas. First, what are you losing if you just wipe the partitions and install 10.1 'from scratch'?
112 GB of unbacked up data, source code for projects, all company records... Stuff I can not live without. I should have made a backup but I was in a hurry and now I am in trouble for not following my own rules about backup. If I had the funds I would go an buy a large HD and problem would be solved. All I have available is a 15 GB laptop HD for testing on my laptop. The system I need to repair is my Desktop PC. At this point I am unable to install Backup Edge to backup to DVD. THis machine has both IDE and SCSI disks. On very large IDE Drive with SUSE, One drive with UnixWare and Windows 2000, cdrom burner and dvd burner. 2 2 GB SCSI HD's with UnixWare 7.1.4, SCSI CD rom, SCSI CD rom burner. The machine is a P III 667 MHz with 128 MB Memory. So I have to have the 1 GB swap to do anything with it and 10.1.
From your description, the upgrade was begun and soon interrupted. It is no longer 10.0 *or* 10.1 but something in between... with the added complexity of manual rescue attempts and manipulated content. I'm not sure the 10.1 installer would be sophisticated enough to identify and sort all these changes out.
I have no idea how long it ran. I had left it to complete un-attended. I have been able to do a test on a smaller hd with 10.0 to a 10.1 upgrade that I halted. It did not have the problem with the boot finding the partitions and swap, but was in between. I powered off at a know point. I was able to boot the mini iso and force a reinstall using update all programs if newer. It did take 3 hours to resolve all the conflicts, because of the stupid updater in 10.1 only doing one at a time. But I was able to get it to 10.1. So I am sure if I can get the system to boot without the waiting for ... to come up I can complete the install. I wish I had another drive to copy all the information off to it, then I would do a new install.
If I knew how to create this situation with the boot not finding the /dev/hda5 swap and /dev/hda6 root, I think I could fix it. Not knowing how to get to this state I do not know how to undo it.
However, if you're absolutely determined to pursue the upgrade route, given the noted anomalies, above, I'd say your best bet would be to run the 10.0 'system repair', first... let it revert the installation back to 10.0 and attempt the upgrade again.
Sadly I had already tried it. With either the DL DVD from 10.0 or CD 1 I am unable to boot from them. The system goes imediately to the HD boot menu. The 10.1 CD and DVD both boot to their menues, Every option I have tried does not seem to work with the 10.0 CD/DVD. I also thought maybe able to use y2pmsh to do the upgrade as mentioned on the opensuse-factory list. The /boot/grub/menu.lst has been changed to 10.1 instead of 10.0. So the system had to get to some point that it was changed or it may have been changed from the 10.1 install/repair installed system.
Any other ideas? Anyone?
Thanks,
A suggestion- try using ACRONIS Disk Director which will find and restore zapped partitions (provided that they are recoverable). It runs in Windows of course but it will also find Linux partitions. I am pretty sure that you can download it on a trial basis. Cheers. -- All answers questioned here.
On Tuesday 23 May 2006 01:40 am, Basil Chupin wrote:
A suggestion- try using ACRONIS Disk Director which will find and restore zapped partitions (provided that they are recoverable). It runs in Windows of course but it will also find Linux partitions. I am pretty sure that you can download it on a trial basis.
You can also make a CD to boot Acronis from.... not sure whether the trial version would allow that.
Bruce Marshall wrote:
On Tuesday 23 May 2006 01:40 am, Basil Chupin wrote:
A suggestion- try using ACRONIS Disk Director which will find and restore zapped partitions (provided that they are recoverable). It runs in Windows of course but it will also find Linux partitions. I am pretty sure that you can download it on a trial basis.
You can also make a CD to boot Acronis from.... not sure whether the trial version would allow that.
One never knows until one tries it. But installing it on a Win system and then doing a work-around to access the HD with SuSE on it would work. Cheers. -- All answers questioned here.
On Tuesday 23 May 2006 01:10, Boyd Lynn Gerber wrote:
On Mon, 22 May 2006, Carl Hartung wrote:
On Monday 22 May 2006 20:22, Boyd Lynn Gerber wrote:
Thanks for any ideas.
First, what are you losing if you just wipe the partitions and install 10.1 'from scratch'?
112 GB of unbacked up data, source code for projects, all company records... Stuff I can not live without.
I meant "wipe" SUSE '/' (hda6) Questions: How many partitions on hda? What sizes are they? Did you maintain a separate /home partition? Which one? What drive/partition has the 'free' 6GB? What partitions on hda contain *data*? (not the Linux system) Carl
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday 23 May 2006 01:10, Boyd Lynn Gerber wrote:
On Mon, 22 May 2006, Carl Hartung wrote:
On Monday 22 May 2006 20:22, Boyd Lynn Gerber wrote:
Thanks for any ideas.
First, what are you losing if you just wipe the partitions and install 10.1 'from scratch'?
112 GB of unbacked up data, source code for projects, all company records... Stuff I can not live without.
I meant "wipe" SUSE '/' (hda6)
Questions: How many partitions on hda?
3 Primary hda1, hda5 1.2 GB swap, hda6 118 GB. The small win 2000 for booting to second HD with win 2000 and UnixWare.
What sizes are they?
win 2000 5 GB, 1.2 GB swap, 118 GB Main Linux, everything all in the one large partition.
Did you maintain a separate /home partition? Which one? What drive/partition has the 'free' 6GB?
thw 118 GB main partition.
What partitions on hda contain *data*? (not the Linux system)
Yes, the Linux System, everything on it. No seperate data partition. - -- Boyd Gerber <gerberb@zenez.com> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQFEcwt/VtBjDid73eYRAnlOAJ4pD4Zns3LCPcoPlPzrX7A1eOI0mgCfca/S gHJvhq8knZXiP38dQDZZM+c= =xKl6 -----END PGP SIGNATURE-----
On Tuesday 23 May 2006 09:17, Boyd Lynn Gerber wrote:
win 2000 5 GB 1.2 GB swap 118 GB Main Linux, everything all in the one large partition.
Hi Boyd, If I were you, since you can't backup your data, I'd pull hda out of the system and temporarily replace it with a cheaply purchased or borrowed 'spare.' All you need is a known working drive that is sitting around because it's now too small, say 8GB or 10GB or something along those lines. **Partition the spare to match your original hda, only obviously the slices must be much smaller. Remember, the first small slice is a primary and the remaining space is an extended carrying two logical partitions: hdn5 (swap) and hdn6 ("/") Be sure to keep hdn6 large enough to hold the installed 10.1. This step is important because you want the subsequent installation to match your original paths.** Install 10.1 on the spare drive. Treat this installation like it is going to be permanent, too, with respect to your desktop and software selections and configuration of hardware, mount points, etc. This system is hopefully going to be transferred to your original drive. Add the original drive back into the system, jumpered and cabled accordingly so you are booting from the spare and you are able to mount your original "/" partition manually. Boot 10.1 and test the original "/" filesystem for corruption. If, say, that partition is mapping to '/dev/hdd6' you'd run 'reiserfsck /dev/hdd6' as root. *DO NOT* attempt any repairs of any kind if corruption is found. If that happens, you MUST find a way to make a backup while the drive can still be read and, hopefully, all or most of your data can be copied wholesale to a safe place. If the filesystem passes the initial check, then mount it *read only* so you can visually sanity-check it for obvious problems. If you don't find any show-stoppers, you then: Boot to rescue (10.0 media is fine) via CD/DVD and manually copy the newly installed 10.1 *into* your original directory structure, the contents of one directory/subdirectory at a time. This distinction is important: don't overwrite directories unless you are absolutely certain the target directory has nothing unique in it. In other words, you want to overwrite (hence replace) the mangled/midmatched system files but leave everything else (any software you've added plus all your data) intact. Note: When you're done with this process, you'll still have to reinstall any 'extra' or 'third party' software to keep your rpm database consistent with the physical contents of the filesystem, but custom settings and original configuration files for that software should not have been impacted. Exceptions: * move your original /home/boyd to /home/.boyd and copy over the new /home/boyd * backup, don't overwrite, the original /etc/fstab. This is to preserve your non-Linux mount points and options. * don't copy the contents of /proc, /sys or /tmp... just confirm these directories still exist in the original filesystem and that they're empty. When this lengthy process is done, your original drive should now contain a system that will boot and run identically to the system you installed on the spare. Shut down, pull the spare drive out, return your drive cabling and jumpers *precisely* back to their original positions and boot from the original drive. *If* the drive does not boot, you should be able to boot into the system using an installation CD/DVD. Once booted, use YaST's bootloader configuration utility to reinstall Grub. Note: Pay particular attention to the device and slice assignments... I and others have had problems with it becoming 'confused' by 'too many' partitions and not using the correct partition numbers. Everything else, i.e. the paths, are still good but the actual partition numbers are wrong in some cases. If you have a problem accomplishing this recovery, drop back into SLE to discuss it before attempting 'ad hoc' deviations, OK? Good luck & regards, Carl
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday 23 May 2006 09:17, Boyd Lynn Gerber wrote:
win 2000 5 GB 1.2 GB swap 118 GB Main Linux, everything all in the one large partition.
If I were you, since you can't backup your data, I'd pull hda out of the system and temporarily replace it with a cheaply purchased or borrowed 'spare.' All you need is a known working drive that is sitting around because it's now too small, say 8GB or 10GB or something along those lines.
I have been fighting this since 4:30 AM. I used backup edge to backup my UnixWare and win 2000 HD. I then blow it away and have since been trying to install 10.1 on it. No Luck. It seems that 10.1 has to have more memory than 128 MB. I just got back on the internet to see if there were any work arounds for the lack of memory. I created a 2 GB swap on the disk as I had to have a 1 GB swap on 10.0. It failed trying ever option I could. I even put the orginal disk in as a slave and tried to use it's swap. I seems I am going to have to install 10.0 on the drive and then see if I can then do a fresh install. I doubt it. As booting from the 10.1 CD's going into rescue system and creating partitions did not seem to help 10.1. I know on 10.0 I was able to do this to install it. Thanks for the below. As that is what I have been trying. I just need to find my purchased copy of 10.0 now to try and install it. I may have to go the update route again to get 10.1 to install. I know that it did not help in rescue mode to format the partitions with the 10.1 CD disks and create a swap. Thanks for the below. That is what I have been trying.
**Partition the spare to match your original hda, only obviously the slices must be much smaller. Remember, the first small slice is a primary and the remaining space is an extended carrying two logical partitions: hdn5 (swap) and hdn6 ("/") Be sure to keep hdn6 large enough to hold the installed 10.1. This step is important because you want the subsequent installation to match your original paths.**
Install 10.1 on the spare drive. Treat this installation like it is going to be permanent, too, with respect to your desktop and software selections and configuration of hardware, mount points, etc. This system is hopefully going to be transferred to your original drive.
Boot 10.1 and test the original "/" filesystem for corruption. If, say, that partition is mapping to '/dev/hdd6' you'd run 'reiserfsck /dev/hdd6' as root. *DO NOT* attempt any repairs of any kind if corruption is found. If that happens, you MUST find a way to make a backup while the drive can still be read and, hopefully, all or most of your data can be copied wholesale to a safe place. If the filesystem passes the initial check, then mount it *read only* so you can visually sanity-check it for obvious problems. ...
The 10.1 CD's tell me that the orignal disk is OK and does not have any errors. Thanks for the other suggestions. That is what I was going to do. You would like an old dog like me who has been using linux since the first Linus' releases would not do such dumb things. I have been in business since 1979 and my first Unix experience was in the late 1960/early 1970's with the PDP 11 and some earlier machines. I just do not remember what they were right now. I have/had every version of SUSE Linux, and most of the other orignal distro's. I guess it is time I followed my own council and backed things up. Just because one have been doing this for many years does not stop things from happening. Thanks everyone for the assistance. I will have to restore my win 2000 and UnixWare but at least I should have my data once I finish this merathon of installation and recovery of the data. - -- Boyd Gerber <gerberb@zenez.com> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQFEc5M7VtBjDid73eYRAsTpAJoCP49nw0fkNcsjartccMcyhV6snQCeLLJ6 5nweF0hBqcF+SHqyUyfOkGU= =0TYA -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2006-05-23 at 07:17 -0600, Boyd Lynn Gerber wrote:
Yes, the Linux System, everything on it. No seperate data partition.
Too bad... you now see why. With a separate data partition (/home etcetera), you could happily format the system / partition. Follow Carl advice, I concur with him fully. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEc1kLtTMYHG2NR9URAgUuAJsFwfImjapkgqYejb4MGMG2bJiTwgCfWokA UTLf+ksGUZcNhFnOm7ENz0s= =9PtF -----END PGP SIGNATURE-----
On Tuesday 23 May 2006 02:22, Boyd Lynn Gerber wrote:
I started a SUSE Linux 10.1 upgrade from 10.0 on saturday. We had a bad weather and a car hit a power pole. My power was out for over 6 hours. I had just started and upgrade when the system died. The upgrade had installed linux-2.6.16.13-4. I have a linux-2.6.16.13-4-obj but no linux-2.6.16.13-4.
When I boot the system I get ...
waiting for /dev/had5 to appear: .... resume device /dev/hda5 not found (Ignoring).
waiting for /dev/had6 to appear: .... not found exiting to (/bin/sh).
I have searched google for "linux waiting for to appear" and tried what I could find most of them were about USB Devices and re-installing. When I boot from CD 1 or the DVD I am able to mount/use both the swap and root as /dev/hda5 and /dev/hda6. When I try to do a network install again the system hangs hard before the select /dev/hda6. When I run install and repair system I get a failure on mkinitrd that is run from the auto repair in the grub menu part of the auto repair.
Auto Repair does not complain about any thing else. It does only have two packages for the base instead of the complete list. Kernel and some YaST. I tried going back to 2.6.13-15.8 with no luck. I remove all the /boot/*2.6.13-15.8 files since they were not there when I booted to the rescue system the first time.
I have tried Rescue System
mount /dev/hda6 /mnt swapon /dev/had5 cd /mnt chroot /mnt
mkinitrd and had it fail.
I then copied the /sbin from Rescue System to /lib/klibc/sbin as that what was giving me errors on mkinitrd. Then it build and installs to /boot the linux-2.6.16.13-4 files again. They are the exact same sizes each time.
Sadly I did not make a backup of the system. I am able to see all my files on the disk from the rescue cd. So I have not lost any thing that I need. The disk is a 120 GB disk with 6 GB available.
I tried to do a rpm --rebuilddb after the above mount and chroot. It did not help. I am not sure what else to try. Does any one have any ideas on getting this system to a state where I am able to restart the network install. I have the entire 10.1/inst-source and 10.1/non-oss-inst-source download to another system that is 10.0. I was using it for the network install.
HELP? I do not know what else to try.
Thanks for any ideas.
-- Boyd Gerber <gerberb@zenez.com> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
What does mkinitrd complain about?? I had the same "waiting for..." error when i updated my system a whole back, and didnt get the XFS driver loaded. It wants to load the partition as per grub statement, but the driver for the file system isnt there. My resolution was to run the rescue system, mount "/ "under "/mnt", and "/boot" undet "/mnt/boot" to make sure i had the important stuff online. And then did mkinitrd. If the /boot isnt mounted properly (under /mnt/boot in my case) mknintrd will most probably barf... -- /Rikard ----------------------------------------------------------------------------- email : rikard.j@rikjoh.com web : http://www.rikjoh.com mob: : +46 (0)763 19 76 25 ------------------------ Public PGP fingerprint ---------------------------- < 15 28 DF 78 67 98 B2 16 1F D3 FD C5 59 D4 B6 78 46 1C EE 56 >
On Mon, 2006-05-22 at 18:22 -0600, Boyd Lynn Gerber wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I started a SUSE Linux 10.1 upgrade from 10.0 on saturday. We had a bad weather and a car hit a power pole. My power was out for over 6 hours. I had just started and upgrade when the system died. The upgrade had
IMHO your hosed so saving /home do a clean install. I usually dont do back to back versions; so I always do a clean install. No problems so far. -- ___ _ _ _ ____ _ _ _ | | | | [__ | | | |___ |_|_| ___] | \/
here's something that may be worth a try... 1. boot disk 1 of your install set, and select installation (yes installation, don't chicken out yet) This will boot using the KERNEL ON THE DISK 2. when it prompts for the setup language, hit Abort It will give you a message that an error has occured, hit ok, and then take you thru a couple of menus 3. select Start installation or system>Boot installed system>Hard Drive, then choose the partition to boot from What this does is boot YOUR system using the rescue kernel on the disk, rather than the "broken" kernel on your hard drive. I have used this successfully to recover Novell's Linux Desktop (built on Suse 9.2), that had downloaded an incomplete set of kernel updates. (Exactly the same symptoms, getting dumped out to that prompt after "not found" 'ing hardware.) Fingers crossed Vaughan Powered by Suse Linux Enterprise Desktop 10 - RC1 Powered by Groupwise7
Boyd Lynn Gerber <gerberb@zenez.com> 05/23/06 10:22 AM >>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I started a SUSE Linux 10.1 upgrade from 10.0 on saturday. We had a bad weather and a car hit a power pole. My power was out for over 6 hours. I had just started and upgrade when the system died. The upgrade had installed linux-2.6.16.13-4. I have a linux-2.6.16.13-4-obj but no linux-2.6.16.13-4. When I boot the system I get ... waiting for /dev/had5 to appear: .... resume device /dev/hda5 not found (Ignoring). waiting for /dev/had6 to appear: .... not found exiting to (/bin/sh).
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
here's something that may be worth a try...
1. boot disk 1 of your install set, and select installation (yes installation, don't chicken out yet) This will boot using the KERNEL ON THE DISK
2. when it prompts for the setup language, hit Abort It will give you a message that an error has occured, hit ok, and then take you thru a couple of menus
3. select Start installation or system>Boot installed system>Hard Drive, then choose the partition to boot from
What this does is boot YOUR system using the rescue kernel on the disk, rather than the "broken" kernel on your hard drive.
I have used this successfully to recover Novell's Linux Desktop (built on Suse 9.2), that had downloaded an incomplete set of kernel updates. (Exactly the same symptoms, getting dumped out to that prompt after "not found" 'ing hardware.)
This workes. Also the making a new HD the same as the first as was also sugested. I wish I had found this before I blew away my UnixWare and Windows 2000 disk. I had just finished the installation the same as the hosed disk. I tried this and it works. You have to do some fiddling. With I was able to boot the disk to continue and back up the data. I then put it back to the broken state and tried my other HD that I made exactly the same with 10.1 on it. I was also able to copy over the data to it and I was able to boot it and use smart to update it. So I now have two ways to fix a similar problem. Thanks to every one for the support and assistance in resolving this. Thanks, - -- Boyd Gerber <gerberb@zenez.com> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQFEe6kdVtBjDid73eYRAg9LAJwMqer3rb+nQnBky3MwUkScX0wZtgCfUXdF iuwYHXZpy0x4Wriu9fjUn+s= =ThXd -----END PGP SIGNATURE-----
On Monday 29 May 2006 22:08, Boyd Lynn Gerber wrote:
here's something that may be worth a try...
1. boot disk 1 of your install set, and select installation (yes installation, don't chicken out yet) This will boot using the KERNEL ON THE DISK
2. when it prompts for the setup language, hit Abort It will give you a message that an error has occured, hit ok, and then take you thru a couple of menus
3. select Start installation or system>Boot installed system>Hard Drive, then choose the partition to boot from
What this does is boot YOUR system using the rescue kernel on the disk, rather than the "broken" kernel on your hard drive.
I have used this successfully to recover Novell's Linux Desktop (built on Suse 9.2), that had downloaded an incomplete set of kernel updates. (Exactly the same symptoms, getting dumped out to that prompt after "not found" 'ing hardware.)
This workes. Also the making a new HD the same as the first as was also sugested. I wish I had found this before I blew away my UnixWare and Windows 2000 disk. I had just finished the installation the same as the hosed disk. I tried this and it works. You have to do some fiddling. With I was able to boot the disk to continue and back up the data. I then put it back to the broken state and tried my other HD that I made exactly the same with 10.1 on it. I was also able to copy over the data to it and I was able to boot it and use smart to update it. So I now have two ways to fix a similar problem.
Thanks to every one for the support and assistance in resolving this.
Hi Boyd, Congratulations on your success! I also think it's great to have more than one method for tackling a serious problem like this. This thread is a 'keeper'! regards, Carl
participants (8)
-
Basil Chupin -
Boyd Lynn Gerber -
Bruce Marshall -
Carl Hartung -
Carl William Spitzer IV -
Carlos E. R. -
Rikard Johnels -
Vaughan Schipplock