3 Oct
2010
3 Oct
'10
4:03 p.m.
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?
Thanks
Rob
aboot: loading uncompressed vmlinuz-2.6.26-1-alpha-generic...
aboot: loading compressed vmlinuz-2.6.26-1-alpha-generic...
aboot: zero-filling 854608 bytes at 0xfffffc000167c980
aboot: loading initrd (1421885 bytes/1388 blocks) at 0xfffffc0013d70000
aboot: starting kernel vmlinuz-2.6.26-1-alpha-generic with arguments ro
root=/d
ev/sdb3 console=ttyS0,9600n1
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.26-1-alpha-generic (Debian 2.6.26-13)
(waldi at de
bian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 Sat
Jan
10 17:21:47 UTC 2009
[ 0.000000] Booting GENERIC on Miata using machine vector Miata from SRM
[ 0.000000] Major Options: MAGIC_SYSRQ
[ 0.000000] Command line: ro root=/dev/sdb3 console=ttyS0,9600n1
[ 0.000000] memcluster 0, usage 1, start 0, end 236
[ 0.000000] memcluster 1, usage 0, start 236, end 40959
[ 0.000000] memcluster 2, usage 1, start 40959, end 40960
[ 0.000000] freeing pages 236:2048
[ 0.000000] freeing pages 2985:40959
[ 0.000000] reserving pages 2985:2986
[ 0.000000] Initial ramdisk at: 0xfffffc0013d70000 (1421885 bytes)
[ 0.000000] pci: cia revision 1 (pyxis)
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total
pag
es: 40679
[ 0.000000] Kernel command line: ro root=/dev/sdb3 console=ttyS0,9600n1
[ 0.000000] PID hash table entries: 2048 (order: 11, 16384 bytes)
[ 0.000000] HWRPB cycle frequency bogus. Estimated 433127999 Hz
[ 0.000000] Using epoch = 2000
[4194001.855599] Console: colour VGA+ 80x25
[4194001.855599] console [ttyS0] enabled
[4194003.204231] Dentry cache hash table entries: 65536 (order: 6, 524288
bytes)
[4194003.294075] Inode-cache hash table entries: 32768 (order: 5, 262144
bytes)
[4194003.414192] Memory: 313552k/327672k available (2158k kernel code,
11952k re
served, 3313k data, 304k init)
[4194003.551887] Security Framework initialized
[4194003.603645] Capability LSM initialized
[4194003.650520] Mount-cache hash table entries: 512
[4194003.707161] Initializing cgroup subsys ns
[4194003.757942] Initializing cgroup subsys cpuacct
[4194003.813606] Initializing cgroup subsys devices
[4194003.877082] net_namespace: 1208 bytes
[4194003.924934] NET: Registered protocol family 16
[4194003.983528] EISA bus registered
[4194004.024543] pci: passed tb register update test
[4194004.081184] pci: passed sg loopback i/o read test
[4194004.139778] pci: passed pte write cache snoop test
[4194004.199348] pci: failed valid tag invalid pte reload test (mcheck;
workarou
nd available)
[4194004.298957] pci: passed pci machine check test
[4194004.353645] pci: tbia workaround enabled
[4194004.403449] pci: enabling save/restore of SRM state
[4194004.468879] PCI: Bridge: 0000:00:14.0
[4194004.515754] IO window: 8000-8fff
[4194004.557746] MEM window: 0x09000000-0x090fffff
[4194004.614387] PREFETCH window: 0x0000000009100000-0x00000000091fffff
[4194004.701301] Linux Plug and Play Support v0.97 (c) Adam Belay
[4194004.785285] NET: Registered protocol family 2
[4194004.850715] IP route cache hash table entries: 4096 (order: 2, 32768
bytes)
[4194004.937629] TCP established hash table entries: 16384 (order: 5, 262144
byt
es)
[4194005.027473] TCP bind hash table entries: 16384 (order: 4, 131072 bytes)
[4194005.109504] TCP: Hash tables configured (established 16384 bind 16384)
[4194005.190558] TCP reno registered
[4194005.233527] NET: Registered protocol family 1
[4194005.289191] checking if image is initramfs... it is
[4194006.371222] Freeing initrd memory: 1388k freed
[4194006.430792] VFS: Disk quotas dquot_6.5.1
[4194006.479620] Dquot-cache hash table entries: 1024 (order 0, 8192 bytes)
[4194006.560675] msgmni has been set to 615
[4194006.608526] Block layer SCSI generic (bsg) driver version 0.4 loaded
(major
253)
[4194006.699347] io scheduler noop registered
[4194006.748175] io scheduler anticipatory registered
[4194006.805792] io scheduler deadline registered
[4194006.859503] io scheduler cfq registered (default)
[4194006.918097] isapnp: Scanning for PnP cards...
[4194007.324346] isapnp: No Plug & Play device found
[4194007.417120] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ
sharin
g enabled
[4194007.512823] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[4194007.588018] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[4194007.684698] brd: module loaded
[4194007.731573] serio: i8042 KBD port at 0x60,0x64 irq 1
[4194007.793096] serio: i8042 AUX port at 0x60,0x64 irq 12
[4194007.858526] mice: PS/2 mouse device common for all mice
[4194007.924932] EISA: Probing bus 0 at eisa.0
[4194007.974737] atkbd.c: keyboard reset failed on isa0060/serio0
[4194008.047979] TCP cubic registered
[4194008.088994] NET: Registered protocol family 17
[4194008.145635] registered taskstats version 1
[4194008.197393] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[4194008.275518] Freeing unused kernel memory: 304k freed
[4194008.352666] atkbd.c: keyboard reset failed on isa0060/serio1
[4194008.698369] SCSI subsystem initialized
[4194008.765752] qla1280: QLA1040 found on PCI bus 1, dev 9
[4194009.400517] scsi(0:0): Resetting SCSI BUS
[4194012.454227] scsi0 : QLogic QLA1040 PCI to SCSI Host Adapter
[4194012.454227] Firmware version: 7.65.06, Driver version 3.26
[4194012.625125] Driver 'sd' needs updating - please use bus_type methods
[4194012.704226] scsi 0:0:0:0: Direct-Access COMPAQ ST32550W
6415
PQ: 0 ANSI: 2
/bin/cat: [4194012.818484] scsi(0:0:0:0): Sync: period 10, offset 12, Wide,
Tagg
ed queuing: depth 31
/sys/block/sdb/dev: No such file or directory
Waiting 1 seconds for /sys/block/sdb/dev to show up
/bin/cat: /sys/block/sdb/dev: No such file or directory
Waiting 2 seconds for /sys/block/sdb/dev to show up
/bin/cat: /sys/block/sdb/dev: No such file or directory
Waiting 4 seconds for /sys/block/sdb/dev to show up
[4194018.073364] sd 0:0:0:0: [sda] 4110000 512-byte hardware sectors (2104
MB)
[4194018.160278] sd 0:0:0:0: [sda] Write Protect is off
[4194018.223755] sd 0:0:0:0: [sda] Write cache: disabled, read cache:
enabled, s
upports DPO and FUA
[4194018.332153] sd 0:0:0:0: [sda] 4110000 512-byte hardware sectors (2104
MB)
[4194018.419067] sd 0:0:0:0: [sda] Write Protect is off
[4194018.482544] sd 0:0:0:0: [sda] Write cache: disabled, read cache:
enabled, s
upports DPO and FUA
[4194018.588012] sda: sda1 sda2 sda3 sda4
[4194018.657348] sd 0:0:0:0: [sda] Attached SCSI disk
/bin/cat: /sys/block/sdb/dev: No such file or directory
Waiting 8 seconds for /sys/block/sdb/dev to show up
/bin/cat: /sys/block/sdb/dev: No such file or directory
Waiting 16 seconds for /sys/block/sdb/dev to show up
/bin/cat: /sys/block/sdb/dev: No such file or directory
Device /sys/block/sdb/dev seems to be down.
/bin/mknod: missing operand after `b'
Special files require major and minor device numbers.
Try `/bin/mknod --help' for more information.
/bin/cat: /sys/block/sdb/sdb3/dev: No such file or directory
Waiting 1 seconds for /sys/block/sdb/sdb3/dev to show up
/bin/cat: /sys/block/sdb/sdb3/dev: No such file or directory
Waiting 2 seconds for /sys/block/sdb/sdb3/dev to show up
/bin/cat: /sys/block/sdb/sdb3/dev: No such file or directory
Waiting 4 seconds for /sys/block/sdb/sdb3/dev to show up
/bin/cat: /sys/block/sdb/sdb3/dev: No such file or directory
Waiting 8 seconds for /sys/block/sdb/sdb3/dev to show up
/bin/cat: /sys/block/sdb/sdb3/dev: No such file or directory
Waiting 16 seconds for /sys/block/sdb/sdb3/dev to show up
/bin/cat: /sys/block/sdb/sdb3/dev: No such file or directory
Device /sys/block/sdb/sdb3/dev seems to be down.
/bin/mknod[4194075.827241] Kernel panic - not syncing: Attempted to kill
init!
: missing operand after `b'
Special files require major and minor device numbers.
Try `/bin/mknod --help' for more information.
mount: special device /dev/sdb3 does not exist
Switching root ...
/usr/lib/yaird/exec/run_init: current directory on the same filesystem as
the ro
ot: Success
3 Oct
3 Oct
4:15 p.m.
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
5:24 p.m.
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:
first disk
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 (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
5 Oct
5 Oct
11:31 a.m.
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
Brad Parker
Heeltoe Consulting
781-483-3101
http://www.heeltoe.com
-----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:
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 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
9 Oct
9 Oct
9:27 a.m.
I tried this and I did not get to a shell. I can examine the files in /etc
from the OS on the spare disk, but I am not expert
enough to work out where
to really look.
Regards
Rob
-----Original Message-----
From: cctalk-bounces at classiccmp.org [mailto:cctalk-
bounces at classiccmp.org] On Behalf Of Brad Parker
Sent: 05 October 2010 16:31
To: General Discussion: On-Topic and Off-Topic Posts
Subject: Re: Repairing Debian on an Alpha 433au
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
Brad Parker
Heeltoe Consulting
781-483-3101
http://www.heeltoe.com
-----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:
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 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
9:15 a.m.
I tried changing to DK0 to DK100 but it made no difference and to be honest
I did not expect it to make a difference.
Clearly there is something wrong with recognising partitions on sdb
(DKA200). If I boot off DK100, which is running Debian 3.1 (Kernel 2.4 it
seems) it can see sdb3 just fine. I don't get all the boot logging that I
get from the corrupted disk though. It would be nice to see what is going on
during a good boot on the temporary disk, how do I turn on boot logging? I
tried adding "debug loglevel=7" to the boot command but nothing extra was
printed.
I also thought I would try pointing the temporary disk's kernel at sdb3 like
this:
b vmlinuz ro initrd=/initrd.img root=/dev/sdb3
But the boot just appeared to hang. I am guessing that it does not help that
the corrupted instance uses 2.6.26 kernel and the temporary kernel is 2.4.
Sorry but I am not very expert on Linux. I am confused by the fact that it
seems to fail to mount sdb3 when booting off sdb3, but succeeds in booting
off sda and then reading sdb3.
Regards
Rob
-----Original Message-----
From: cctalk-bounces at classiccmp.org [mailto:cctalk-
bounces at classiccmp.org] On Behalf Of Rob Jarratt
Sent: 03 October 2010 21:04
To: General Discussion: On-Topic and Off-Topic Posts
Subject: Repairing Debian on an Alpha 433au
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?
Thanks
Rob
aboot: loading uncompressed vmlinuz-2.6.26-1-alpha-generic...
aboot: loading compressed vmlinuz-2.6.26-1-alpha-generic...
aboot: zero-filling 854608 bytes at 0xfffffc000167c980
aboot: loading initrd (1421885 bytes/1388 blocks) at 0xfffffc0013d70000
aboot: starting kernel vmlinuz-2.6.26-1-alpha-generic with arguments ro
root=/d
ev/sdb3 console=ttyS0,9600n1
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.26-1-alpha-generic (Debian 2.6.26-13)
(waldi at de
bian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1
Sat
Jan
10 17:21:47 UTC 2009
[ 0.000000] Booting GENERIC on Miata using machine vector Miata from
SRM
[ 0.000000] Major Options: MAGIC_SYSRQ
[ 0.000000] Command line: ro root=/dev/sdb3 console=ttyS0,9600n1
[ 0.000000] memcluster 0, usage 1, start 0, end 236
[ 0.000000] memcluster 1, usage 0, start 236, end 40959
[ 0.000000] memcluster 2, usage 1, start 40959, end 40960
[ 0.000000] freeing pages 236:2048
[ 0.000000] freeing pages 2985:40959
[ 0.000000] reserving pages 2985:2986
[ 0.000000] Initial ramdisk at: 0xfffffc0013d70000 (1421885 bytes)
[ 0.000000] pci: cia revision 1 (pyxis)
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on.
Total
pag
es: 40679
[ 0.000000] Kernel command line: ro root=/dev/sdb3
console=ttyS0,9600n1
[ 0.000000] PID hash table entries: 2048 (order:
11, 16384 bytes)
[ 0.000000] HWRPB cycle frequency bogus. Estimated 433127999 Hz
[ 0.000000] Using epoch = 2000
[4194001.855599] Console: colour VGA+ 80x25 [4194001.855599] console
[ttyS0] enabled [4194003.204231] Dentry cache hash table entries: 65536
(order: 6, 524288
bytes)
[4194003.294075] Inode-cache hash table entries: 32768 (order: 5, 262144
bytes)
[4194003.414192] Memory: 313552k/327672k available (2158k kernel code,
11952k re served, 3313k data, 304k init) [4194003.551887] Security
Framework
initialized [4194003.603645] Capability LSM
initialized [4194003.650520]
Mount-cache hash table entries: 512 [4194003.707161] Initializing cgroup
subsys ns [4194003.757942] Initializing cgroup subsys cpuacct
[4194003.813606] Initializing cgroup subsys devices [4194003.877082]
net_namespace: 1208 bytes [4194003.924934] NET: Registered protocol
family 16 [4194003.983528] EISA bus registered [4194004.024543] pci:
passed
tb register update test [4194004.081184] pci: passed
sg loopback i/o read
test
[4194004.139778] pci: passed pte write cache snoop
test [4194004.199348]
pci: failed valid tag invalid pte reload test (mcheck; workarou nd
available)
[4194004.298957] pci: passed pci machine check test
[4194004.353645] pci:
tbia workaround enabled [4194004.403449] pci: enabling save/restore of SRM
state [4194004.468879] PCI: Bridge: 0000:00:14.0
[4194004.515754] IO window: 8000-8fff
[4194004.557746] MEM window: 0x09000000-0x090fffff
[4194004.614387] PREFETCH window: 0x0000000009100000-
0x00000000091fffff
[4194004.701301] Linux Plug and Play Support v0.97 (c) Adam Belay
[4194004.785285] NET: Registered protocol family 2 [4194004.850715] IP
route
cache hash table entries: 4096 (order: 2, 32768
bytes)
[4194004.937629] TCP established hash table entries: 16384 (order: 5,
262144
byt
es)
[4194005.027473] TCP bind hash table entries: 16384 (order: 4, 131072
bytes)
[4194005.109504] TCP: Hash tables configured
(established 16384 bind
16384)
[4194005.190558] TCP reno registered [4194005.233527]
NET: Registered
protocol family 1 [4194005.289191] checking if image is initramfs... it is
[4194006.371222] Freeing initrd memory: 1388k freed [4194006.430792] VFS:
Disk quotas dquot_6.5.1 [4194006.479620] Dquot-cache hash table entries:
1024 (order 0, 8192 bytes) [4194006.560675] msgmni has been set to 615
[4194006.608526] Block layer SCSI generic (bsg) driver version 0.4 loaded
(major
253)
[4194006.699347] io scheduler noop registered [4194006.748175] io
scheduler
anticipatory registered [4194006.805792] io scheduler
deadline registered
[4194006.859503] io scheduler cfq registered (default) [4194006.918097]
isapnp: Scanning for PnP cards...
[4194007.324346] isapnp: No Plug & Play device found [4194007.417120]
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharin g enabled
[4194007.512823] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[4194007.588018] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[4194007.684698] brd: module loaded [4194007.731573] serio: i8042 KBD port
at 0x60,0x64 irq 1 [4194007.793096] serio: i8042 AUX port at 0x60,0x64 irq
12
[4194007.858526] mice: PS/2 mouse device common for
all mice
[4194007.924932] EISA: Probing bus 0 at eisa.0 [4194007.974737] atkbd.c:
keyboard reset failed on isa0060/serio0 [4194008.047979] TCP cubic
registered [4194008.088994] NET: Registered protocol family 17
[4194008.145635] registered taskstats version 1 [4194008.197393]
drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [4194008.275518]
Freeing unused kernel memory: 304k freed [4194008.352666] atkbd.c:
keyboard reset failed on isa0060/serio1 [4194008.698369] SCSI subsystem
initialized [4194008.765752] qla1280: QLA1040 found on PCI bus 1, dev 9
[4194009.400517] scsi(0:0): Resetting SCSI BUS [4194012.454227] scsi0 :
QLogic
QLA1040 PCI to SCSI Host Adapter
[4194012.454227] Firmware version: 7.65.06, Driver version 3.26
[4194012.625125] Driver 'sd' needs updating - please use bus_type methods
[4194012.704226] scsi 0:0:0:0: Direct-Access COMPAQ ST32550W
6415
PQ: 0 ANSI: 2
/bin/cat: [4194012.818484] scsi(0:0:0:0): Sync: period 10, offset 12,
Wide, Tagg
ed queuing: depth 31
/sys/block/sdb/dev: No such file or directory Waiting 1 seconds for
/sys/block/sdb/dev to show up
/bin/cat: /sys/block/sdb/dev: No such file or directory Waiting 2 seconds
for
/sys/block/sdb/dev to show up
/bin/cat: /sys/block/sdb/dev: No such file or directory Waiting 4 seconds
for
/sys/block/sdb/dev to show up [4194018.073364] sd
0:0:0:0: [sda] 4110000
512-byte hardware sectors (2104
MB)
[4194018.160278] sd 0:0:0:0: [sda] Write Protect is off [4194018.223755]
sd
0:0:0:0: [sda] Write cache: disabled, read cache:
enabled, s
upports DPO and FUA
[4194018.332153] sd 0:0:0:0: [sda] 4110000 512-byte hardware sectors (2104
MB)
[4194018.419067] sd 0:0:0:0: [sda] Write Protect is off [4194018.482544]
sd
0:0:0:0: [sda] Write cache: disabled, read cache:
enabled, s
upports DPO and FUA
[4194018.588012] sda: sda1 sda2 sda3 sda4 [4194018.657348] sd 0:0:0:0:
[sda]
Attached SCSI disk
/bin/cat: /sys/block/sdb/dev: No such file or directory Waiting 8 seconds
for
/sys/block/sdb/dev to show up
/bin/cat: /sys/block/sdb/dev: No such file or directory Waiting 16 seconds
for
/sys/block/sdb/dev to show up
/bin/cat: /sys/block/sdb/dev: No such file or directory Device
/sys/block/sdb/dev seems to be down.
/bin/mknod: missing operand after `b'
Special files require major and minor device numbers.
Try `/bin/mknod --help' for more information.
/bin/cat: /sys/block/sdb/sdb3/dev: No such file or directory Waiting 1
seconds for /sys/block/sdb/sdb3/dev to show up
/bin/cat: /sys/block/sdb/sdb3/dev: No such file or directory Waiting 2
seconds for /sys/block/sdb/sdb3/dev to show up
/bin/cat: /sys/block/sdb/sdb3/dev: No such file or directory Waiting 4
seconds for /sys/block/sdb/sdb3/dev to show up
/bin/cat: /sys/block/sdb/sdb3/dev: No such file or directory Waiting 8
seconds for /sys/block/sdb/sdb3/dev to show up
/bin/cat: /sys/block/sdb/sdb3/dev: No such file or directory Waiting 16
seconds for /sys/block/sdb/sdb3/dev to show up
/bin/cat: /sys/block/sdb/sdb3/dev: No such file or directory Device
/sys/block/sdb/sdb3/dev seems to be down.
/bin/mknod[4194075.827241] Kernel panic - not syncing: Attempted to kill
init!
: missing operand after `b'
Special files require major and minor device numbers.
Try `/bin/mknod --help' for more information.
mount: special device /dev/sdb3 does not exist Switching root ...
/usr/lib/yaird/exec/run_init: current directory on the same filesystem as
the
ro
ot: Success
1:51 p.m.
One more interesting fact. I got a Debian 5.06 install CD and tried that. It
could not detect the CD-ROM drive, but I let it drop to a shell. In there it
could see /dev/sda3, but not /dev/sdb3, in fact there were no /dev /sdb*
files at all. So it would appear not to recognise the drive at all.
Regards
Rob
[4194006.430792]
-----Original Message-----
From: cctalk-bounces at classiccmp.org [mailto:cctalk-
bounces at classiccmp.org] On Behalf Of Rob Jarratt
Sent: 09 October 2010 14:16
To: 'General Discussion: On-Topic and Off-Topic Posts'
Subject: RE: Repairing Debian on an Alpha 433au
I tried changing to DK0 to DK100 but it made no difference and to be
honest I
did not expect it to make a difference.
Clearly there is something wrong with recognising partitions on sdb
(DKA200). If I boot off DK100, which is running Debian 3.1 (Kernel 2.4 it
seems) it can see sdb3 just fine. I don't get all the boot logging that I
get
from
the corrupted disk though. It would be nice to see
what is going on during
a
good boot on the temporary disk, how do I turn on boot
logging? I tried
adding "debug loglevel=7" to the boot command but nothing extra was
printed.
I also thought I would try pointing the temporary disk's kernel at sdb3
like
this:
b vmlinuz ro initrd=/initrd.img root=/dev/sdb3
But the boot just appeared to hang. I am guessing that it does not help
that
the corrupted instance uses 2.6.26 kernel and the
temporary kernel is 2.4.
Sorry but I am not very expert on Linux. I am confused by the fact that it
seems to fail to mount sdb3 when booting off sdb3, but succeeds in booting
off sda and then reading sdb3.
Regards
Rob
to
-----Original Message-----
From: cctalk-bounces at classiccmp.org [mailto:cctalk-
bounces at classiccmp.org] On Behalf Of Rob Jarratt
Sent: 03 October 2010 21:04
To: General Discussion: On-Topic and Off-Topic Posts
Subject: Repairing Debian on an Alpha 433au
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 fix it.
pci:
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?
Thanks
Rob
aboot: loading uncompressed vmlinuz-2.6.26-1-alpha-generic...
aboot: loading compressed vmlinuz-2.6.26-1-alpha-generic...
aboot: zero-filling 854608 bytes at 0xfffffc000167c980
aboot: loading initrd (1421885 bytes/1388 blocks) at
0xfffffc0013d70000
aboot: starting kernel vmlinuz-2.6.26-1-alpha-generic with arguments
ro root=/d
ev/sdb3 console=ttyS0,9600n1
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.26-1-alpha-generic (Debian 2.6.26-13)
(waldi at de
bian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24))
#1
Sat
Jan
10 17:21:47 UTC 2009
[ 0.000000] Booting GENERIC on Miata using machine vector Miata from
SRM
[ 0.000000] Major Options: MAGIC_SYSRQ
[ 0.000000] Command line: ro root=/dev/sdb3 console=ttyS0,9600n1
[ 0.000000] memcluster 0, usage 1, start 0, end 236
[ 0.000000] memcluster 1, usage 0, start 236, end 40959
[ 0.000000] memcluster 2, usage 1, start 40959, end 40960
[ 0.000000] freeing pages 236:2048
[ 0.000000] freeing pages 2985:40959
[ 0.000000] reserving pages 2985:2986
[ 0.000000] Initial ramdisk at: 0xfffffc0013d70000 (1421885 bytes)
[ 0.000000] pci: cia revision 1 (pyxis)
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on.
Total
pag
es: 40679
[ 0.000000] Kernel command line: ro root=/dev/sdb3
console=ttyS0,9600n1
[ 0.000000] PID hash table entries: 2048
(order: 11, 16384 bytes)
[ 0.000000] HWRPB cycle frequency bogus. Estimated 433127999 Hz
[ 0.000000] Using epoch = 2000
[4194001.855599] Console: colour VGA+ 80x25 [4194001.855599] console
[ttyS0] enabled [4194003.204231] Dentry cache hash table entries:
65536
(order: 6, 524288
bytes)
[4194003.294075] Inode-cache hash table entries: 32768 (order: 5,
262144
bytes)
[4194003.414192] Memory: 313552k/327672k available (2158k kernel code,
11952k re served, 3313k data, 304k init) [4194003.551887] Security
Framework
initialized [4194003.603645] Capability LSM
initialized
[4194003.650520] Mount-cache hash table entries: 512 [4194003.707161]
Initializing cgroup subsys ns [4194003.757942] Initializing cgroup
subsys cpuacct [4194003.813606] Initializing cgroup subsys devices
[4194003.877082]
net_namespace: 1208 bytes [4194003.924934] NET: Registered protocol
family 16 [4194003.983528] EISA bus registered [4194004.024543] pci:
passed
tb register update test [4194004.081184] pci:
passed sg loopback i/o
read
test
[4194004.139778] pci: passed pte write cache
snoop test
[4194004.199348]
pci: failed valid tag invalid pte reload test (mcheck; workarou nd
available)
> [4194004.298957] pci: passed pci machine check test [4194004.353645] tbia
workaround enabled [4194004.403449] pci: enabling save/restore of
SRM state [4194004.468879] PCI: Bridge: 0000:00:14.0
[4194004.515754] IO window: 8000-8fff
[4194004.557746] MEM window: 0x09000000-0x090fffff
[4194004.614387] PREFETCH window: 0x0000000009100000-
0x00000000091fffff
[4194004.701301] Linux Plug and Play Support v0.97 (c) Adam Belay
[4194004.785285] NET: Registered protocol family 2 [4194004.850715] IP
route
cache hash table entries: 4096 (order: 2, 32768
bytes)
[4194004.937629] TCP established hash table entries: 16384 (order: 5,
262144
byt
es)
[4194005.027473] TCP bind hash table entries: 16384 (order: 4, 131072
bytes)
[4194005.109504] TCP: Hash tables configured
(established 16384 bind
16384)
> [4194005.190558] TCP reno registered [4194005.233527] NET: Registered
> protocol family 1 [4194005.289191] checking if image is initramfs...
> it is [4194006.371222] Freeing initrd memory: 1388k freed VFS:
Disk quotas dquot_6.5.1 [4194006.479620]
Dquot-cache hash table entries:
1024 (order 0, 8192 bytes) [4194006.560675] msgmni has been set to 615
[4194006.608526] Block layer SCSI generic (bsg) driver version 0.4
loaded (major
253)
[4194006.699347] io scheduler noop registered [4194006.748175] io
scheduler
anticipatory registered [4194006.805792] io
scheduler deadline
registered [4194006.859503] io scheduler cfq registered (default)
[4194006.918097]
isapnp: Scanning for PnP cards...
[4194007.324346] isapnp: No Plug & Play device found [4194007.417120]
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharin g
enabled [4194007.512823] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a
16550A [4194007.588018] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a
16550A [4194007.684698] brd: module loaded [4194007.731573] serio:
i8042 KBD port at 0x60,0x64 irq 1 [4194007.793096] serio: i8042 AUX
port at 0x60,0x64 irq
12
[4194007.858526] mice: PS/2 mouse device common
for all mice
[4194007.924932] EISA: Probing bus 0 at eisa.0 [4194007.974737] atkbd.c:
keyboard reset failed on isa0060/serio0 [4194008.047979] TCP cubic
registered [4194008.088994] NET: Registered protocol family 17
[4194008.145635] registered taskstats version 1 [4194008.197393]
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[4194008.275518] Freeing unused kernel memory: 304k freed
[4194008.352666]
atkbd.c:
keyboard reset failed on isa0060/serio1
[4194008.698369] SCSI
subsystem initialized [4194008.765752] qla1280: QLA1040 found on PCI
bus 1, dev 9 [4194009.400517] scsi(0:0): Resetting SCSI BUS
[4194012.454227] scsi0
:
QLogic
QLA1040 PCI to SCSI Host Adapter
[4194012.454227] Firmware version: 7.65.06, Driver version 3.26
[4194012.625125] Driver 'sd' needs updating - please use bus_type
methods
[4194012.704226] scsi 0:0:0:0: Direct-Access
COMPAQ ST32550W
6415
PQ: 0 ANSI: 2
/bin/cat: [4194012.818484] scsi(0:0:0:0): Sync: period 10, offset 12,
Wide, Tagg
ed queuing: depth 31
/sys/block/sdb/dev: No such file or directory Waiting 1 seconds for
/sys/block/sdb/dev to show up
/bin/cat: /sys/block/sdb/dev: No such file or directory Waiting 2
seconds
for
/sys/block/sdb/dev to show up
/bin/cat: /sys/block/sdb/dev: No such file or directory Waiting 4
seconds
for
/sys/block/sdb/dev to show up [4194018.073364] sd
0:0:0:0: [sda]
4110000 512-byte hardware sectors (2104
MB)
[4194018.160278] sd 0:0:0:0: [sda] Write Protect is off
[4194018.223755]
sd
0:0:0:0: [sda] Write cache: disabled, read
cache:
enabled, s
upports DPO and FUA
[4194018.332153] sd 0:0:0:0: [sda] 4110000 512-byte hardware sectors
(2104
MB)
[4194018.419067] sd 0:0:0:0: [sda] Write Protect is off
[4194018.482544]
sd
0:0:0:0: [sda] Write cache: disabled, read
cache:
enabled, s
upports DPO and FUA
[4194018.588012] sda: sda1 sda2 sda3 sda4 [4194018.657348] sd 0:0:0:0:
[sda]
Attached SCSI disk
/bin/cat: /sys/block/sdb/dev: No such file or directory Waiting 8
seconds
for
/sys/block/sdb/dev to show up
/bin/cat: /sys/block/sdb/dev: No such file or directory Waiting 16
seconds
for
/sys/block/sdb/dev to show up
/bin/cat: /sys/block/sdb/dev: No such file or directory Device
/sys/block/sdb/dev seems to be down.
/bin/mknod: missing operand after `b'
Special files require major and minor device numbers.
Try `/bin/mknod --help' for more information.
/bin/cat: /sys/block/sdb/sdb3/dev: No such file or directory Waiting 1
seconds for /sys/block/sdb/sdb3/dev to show up
/bin/cat: /sys/block/sdb/sdb3/dev: No such file or directory Waiting 2
seconds for /sys/block/sdb/sdb3/dev to show up
/bin/cat: /sys/block/sdb/sdb3/dev: No such file or directory Waiting 4
seconds for /sys/block/sdb/sdb3/dev to show up
/bin/cat: /sys/block/sdb/sdb3/dev: No such file or directory Waiting 8
seconds for /sys/block/sdb/sdb3/dev to show up
/bin/cat: /sys/block/sdb/sdb3/dev: No such file or directory Waiting
16 seconds for /sys/block/sdb/sdb3/dev to show up
/bin/cat: /sys/block/sdb/sdb3/dev: No such file or directory Device
/sys/block/sdb/sdb3/dev seems to be down.
/bin/mknod[4194075.827241] Kernel panic - not syncing: Attempted to
kill init!
: missing operand after `b'
Special files require major and minor device numbers.
Try `/bin/mknod --help' for more information.
mount: special device /dev/sdb3 does not exist Switching root ...
/usr/lib/yaird/exec/run_init: current directory on the same filesystem
as
the
> ro
> ot: Success
5000
days inactive
5006
days old
6 comments
3 participants
participants (3)
-
brad＠heeltoe.com -
pat＠computer-refuge.org -
robert.jarratt＠ntlworld.com