You might try "init=/bin/sh" to keep any init scripts from running. That
way you can piece together what it's trying to do, tracing from /etc/inittab
Those errors look like the kernel is up but some init script is unhappy.
-brad
On Oct 3, 2010, at 5:24 PM, Rob Jarratt wrote:
I have actually tried both ways, with and without DK0
plugged in. That
particular boot I sent the log for had both disks plugged in
Mind you the spare disk that is in there now is DK0. That replaced a disk at
DKA100 which had VMS on it, which I had to take out temporarily to make way
for the temporary disk to put the second instance of Debian on. So when the
machine was working I had VMS on DKA100 and Debian on DKA200. Now I have the
temporary Debian on DK0 and the "proper" Debian on DKA200.
I will try your suggestion when I next get the chance to test, which won't
be for a few days now. I may also try putting the VMS disk back in so I have
DKA100 and DKA200 again, not sure if this will make a difference.
Regards
Rob
-----Original Message-----
From: cctalk-bounces at
classiccmp.org [mailto:cctalk-
bounces at
classiccmp.org] On Behalf Of Patrick Finnegan
Sent: 03 October 2010 21:16
To: General Discussion: On-Topic and Off-Topic Posts
Subject: Re: Repairing Debian on an Alpha 433au
On Sunday, October 03, 2010, Rob Jarratt wrote:
The 433au I have came with an instance of Debian
which has DECnet
installed on it, I am not sure what version of Debian it is. After a
power outage the superblock on DKA200 was corrupted. I managed to
install another instance of Debian (3.1r0) on DK0 and run e2fsck -p on
the DKA200 disk to fix it. However when I try to boot the original
Debian instance it says it can't find /dev/sdb3. In the new instance
of Debian I can mount the sdb3 disk without issue. Below is the output
on the console when it fails to boot. There is a message about the
driver sd needing to be updated, but this was a working system so I am
not convinced that is the problem. Can anyone offer any insight as to
why this will still not boot?
The kernel is only seeing one disk. By any chance, are you pulling the
first disk
> (DKA0?) when you try booting from the 2nd disk (DKA200)?
>
> Maybe try telling aboot root=/dev/sda3 for your root device instead.
>
> Pat
> --
> Purdue University Research Computing ---
http://www.rcac.purdue.edu/
> The Computer Refuge ---
http://computer-refuge.org