On 30 Jun 2008, Daniel Dalton wrote:
> On Mon, Jun 30, 2008 at 10:50:03AM +0100, Anthony Campbell wrote:
>
> > On 30 Jun 2008, Daniel Dalton wrote:
> > No error messages. I do get:
> > aetting up linux-image-2.6.25-2-amd64 (2.6.25-6) ...
> > Running depmod.
> > Finding valid ramdisk creators.
>
> should be fine
>
> > The kernel is correct; I'm currently using linux-image-2.6.23-amd64.
>
> indeed
>
> >
> > I take the point about using a rescue disk but I'm not sure of what to
> > try for /etc/fstab. I know that a fresh installation of linux uses
>
> Erm, didn't you say you found this on google earlier? Isn't that how we
> got started talking about rescue cds? Or have I mistaken... You know you
> can also backup your fstab before you touch it so it is just a matter of
> doing this when in the rescue cd:
> cp /path/to/backup/fstab /etc
> (that will restore your backup)
>
> > different syntax but I don't remember what it is or how it works.
> > Currently I have:
>
> Don't ask me about fstab, I haven't read up on this much, perhaps others
> can help with this.
>
Yes, I do know about rescue CDs, backing up /etc/fstab etc. But I didn't
really want to go down that route unless it's necessary and I really
don't know where to begin sorting this one out. None of the Goggle stuff
is very helpful. I'm not at all sure that messing about with /etc/fstab
would help.
I don't seem to be alone with this one. There was a recent (June 21)
post with almost identical errors:
Begin: Running /scripts/init-bottom ...
mount: No such file or directory
mount: No such file or directory
Target file system doesn't have /sbin/init
No init found. Try passing init= bootarg.
BusyBox v1.10.2 (Debian 1:1.10.2-1) built-in shell (ash)
Enter 'help' for alist of built-in commands
/bin/sh: can't access tty; job control off
(initramfs)
I have no idea where to start debugging from. I think that the
problem is more about the kernel, not about the mdadm. I suppose
I somehow did not comiped in the kernel something needed for
finding the sATA devices, but I used the default kernel
configuration and I was thinking that this should work. Morover,
I cannot boot the LinuxOLD image (which was working perfectly
before), since it ends in a kernel panic message.
Any idea on how to boot this machine and bring back in a working
condition is welcome.
This is:
http://www.mail-archive.com/debian-user@lists.debian.org/msg519211.html
Time for a bug report, I think.
Anthony
--
Anthony Campbell - [EMAIL PROTECTED]
Microsoft-free zone - Using Debian GNU/Linux
http://www.acampbell.org.uk (blog, book reviews,
and sceptical articles)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
