Re: kinit/resume - what's it mean? how to boot from failed sys??
On Fri, 2008-03-21 at 08:09 -0700, Daniel Burrows wrote:
> On Thu, Mar 20, 2008 at 08:30:08PM +, michael <[EMAIL PROTECTED]> was
> heard to say:
> > Thanks for the ideas (eg using liveCD etc)... in the end from initramfs
> > I created /tmp/boot, told dmraid to not activate, and then mounted the
> > (known) /dev/hdaN partition as /tmp/boot and renamed the errant
> > (non-working dmraid) initrd.img-${KERNEL} to ${WHATEVER} and renamed
> > the initrd.img.${KERNEL}.bak (that presumably dmraid had created) to
> > initrd.img and did a reboot so it picked up the old, working initrd
> > image and away I went to the working system (then apt-get remove dmraid)
>
> If you're using grub, you can avoid some of those steps by just
> adjusting the boot script (type "e" at the boot menu and change the
> initrd that gets loaded).
true, but since I didn't know what was happening in /boot let alone
initrd names I had to mount it first but thanks for pointing out one can
temp amend Grub boot options
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kinit/resume - what's it mean? how to boot from failed sys??
On Thu, Mar 20, 2008 at 08:30:08PM +, michael <[EMAIL PROTECTED]> was heard
to say:
> Thanks for the ideas (eg using liveCD etc)... in the end from initramfs
> I created /tmp/boot, told dmraid to not activate, and then mounted the
> (known) /dev/hdaN partition as /tmp/boot and renamed the errant
> (non-working dmraid) initrd.img-${KERNEL} to ${WHATEVER} and renamed
> the initrd.img.${KERNEL}.bak (that presumably dmraid had created) to
> initrd.img and did a reboot so it picked up the old, working initrd
> image and away I went to the working system (then apt-get remove dmraid)
If you're using grub, you can avoid some of those steps by just
adjusting the boot script (type "e" at the boot menu and change the
initrd that gets loaded).
Daniel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kinit/resume - what's it mean? how to boot from failed sys??
On Thu, 2008-03-20 at 16:37 +, michael wrote:
> Hands up to making a mistake - I've been trying to get my AMD64
> Debian 'etch' box to recognise a Promise controller and thought that
> installing dmraid would help. I did a
>apt-get install dmraid
> and then rebooted... only to find it in BusyBox with a initramfs
> prompt and no idea as how to recover to a working system...
>
> I can see it's trying to run some /scripts and then kinit does
> something before attempting to 'resume' and saying there is no resume
> image then trying a normal boot but saying it can not read the image
> (then many more lines of complaints but am unsure how to copy to
> another machine)
>
>
> Any ideas? I'd guess rebooting somehow without these scripts and then
> removing dmraid would return me to a wokring system but I'm unsure
> how to do even this!
Thanks for the ideas (eg using liveCD etc)... in the end from initramfs
I created /tmp/boot, told dmraid to not activate, and then mounted the
(known) /dev/hdaN partition as /tmp/boot and renamed the errant
(non-working dmraid) initrd.img-${KERNEL} to ${WHATEVER} and renamed
the initrd.img.${KERNEL}.bak (that presumably dmraid had created) to
initrd.img and did a reboot so it picked up the old, working initrd
image and away I went to the working system (then apt-get remove dmraid)
ta, again, Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kinit/resume - what's it mean? how to boot from failed sys??
On 3/20/08, michael <[EMAIL PROTECTED]> wrote: > Hands up to making a mistake - I've been trying to get my AMD64 > Debian 'etch' box to recognise a Promise controller and thought that > installing dmraid would help. I did a > apt-get install dmraid > and then rebooted... only to find it in BusyBox with a initramfs > prompt and no idea as how to recover to a working system... > Any ideas? I'd guess rebooting somehow without these scripts and then > removing dmraid would return me to a wokring system but I'm unsure > how to do even this! Okay, to recover a system that doesn't boot properly, you can use the installation media, such as a Debian etch install CD. Instructions here: | http://www.debian.org/releases/stable/i386/ch08s07.html.en You can also make a boot floppy with the mkboot command, I think, once you have your system booted. If you lack boot media you can get it from here: | http://www.debian.org/distrib/netinst Just the floppies will do if you happen to be on dialup. Let me know if this helped. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kinit/resume - what's it mean? how to boot from failed sys??
On Thu, Mar 20, 2008 at 04:37:36PM +, michael wrote: > Hands up to making a mistake - I've been trying to get my AMD64 Debian > 'etch' box to recognise a Promise controller and thought that installing > dmraid would help. I did a >apt-get install dmraid > and then rebooted... only to find it in BusyBox with a initramfs prompt > and no idea as how to recover to a working system... > > I can see it's trying to run some /scripts and then kinit does something > before attempting to 'resume' and saying there is no resume image then > trying a normal boot but saying it can not read the image (then many more > lines of complaints but am unsure how to copy to another machine) maybe setup a serial terminal to allow capture of the session. > > > Any ideas? I'd guess rebooting somehow without these scripts and then > removing dmraid would return me to a wokring system but I'm unsure how to > do even this! best bet is probably to boot a live-cd and chroot into the system and attempt to fixup from there. At a guess, you're initrd can't find / in the real system. You *might* be able to get it mounted from within busybox and then `exit` to get it to continue the boot. But the tools are pretty limited and it requires a goodly bit of poking around to see exactly what the problem is... A signature.asc Description: Digital signature
kinit/resume - what's it mean? how to boot from failed sys??
Hands up to making a mistake - I've been trying to get my AMD64 Debian 'etch' box to recognise a Promise controller and thought that installing dmraid would help. I did a apt-get install dmraid and then rebooted... only to find it in BusyBox with a initramfs prompt and no idea as how to recover to a working system... I can see it's trying to run some /scripts and then kinit does something before attempting to 'resume' and saying there is no resume image then trying a normal boot but saying it can not read the image (then many more lines of complaints but am unsure how to copy to another machine) Any ideas? I'd guess rebooting somehow without these scripts and then removing dmraid would return me to a wokring system but I'm unsure how to do even this! Many thanks, Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
