[Armadillo:00801] CFbootとＨＤＤbootがｃｔｒｌDを要求するのですが修復方法は

[ishimatu]

ishimatsuでございます
ＣＦｂｏｏｔでもＨＤＤbootでも
途中でｃｔｒｌDまたはrootのパスワードを要求する
ようになってしまいました。

何がおきているのでしょうか
どうすれば修復できるのでしょうか。
以上宜しくお願いいたします。

以下にboot時のmessageを書きます
萩原の６４MB　CFの場合です。


Console: colour dummy device 80x30
Calibrating delay loop... 99.73 BogoMIPS
Memory: 32MB 32MB = 64MB total
Memory: 55876KB available (1874K code, 369K data, 72K init)
Dentry cache hash table entries: 8192 (order: 4, 65536 bytes)
Inode cache hash table entries: 4096 (order: 3, 32768 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
Journalled Block Device driver loaded
devfs: v1.12c (20020818) Richard Gooch (email@hidden)
devfs: boot_options: 0x0
i2c-core.o: i2c core module version 2.6.1 (20010830)
i2c-algo-bit.o: i2c bit algorithm module
i2c-armadillo9: i2c Armadillo-9 driver, (C) 2004-2005 Atmark Techno, Inc.
i2c-s3531a: Device Type [S-3531A]
i2c-s3531a: i2c S-3531A/S-353X0A driver, (C) 2001-2005 Atmark Techno, Inc.
i2c-at24cxx: i2c at24cxx eeprom driver, (C) 2004 Atmark Techno, Inc.
Console: switching to colour frame buffer device 80x60
pty: 256 Unix98 ptys configured
ttyAM%d0 at MMIO 0xff8c0000 (irq = 52) is a AMBA
ttyAM%d1 at MMIO 0xff8d0000 (irq = 54) is a AMBA
ttyAM%d2 at MMIO 0xff8e0000 (irq = 55) is a AMBA
ep93xx_eth() version: ep93xx_eth.c: V1.0 09/04/2003 Cirrus Logic
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
 Fixed Disk Card
 IDE interface
 [silicon] [unique] [single] [sleep] [standby] [idle] [low power]
Trying to free nonexistent resource <c699d000-c699d00f>
hdc: TOSHIBA THNCF064MMA, CFA DISK drive
ide1 at 0xc699d000-0xc699d007,0xc699d00e on irq 49
hdc: attached ide-disk driver.
hdc: 125184 sectors (64 MB) w/2KiB Cache, CHS=978/4/32
Partition check:
 /dev/ide/host1/bus0/target0/lun0: p1
SCSI subsystem driver Revision: 1.00
Armadillo9-NOR:0x00800000 at 0x60000000
 Amd/Fujitsu Extended Query Table v1.3 at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling fast programming due to code brokenness.
Armadillo9-NOR:using command line partition definition
Creating 4 MTD partitions on "NOR flash on Armadillo-9":
0x00000000-0x00010000 : "bootloader"
0x00010000-0x00180000 : "kernel"
0x00180000-0x007f0000 : "userland"
0x007f0000-0x00800000 : "config"
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
host/usb-ohci.c: USB OHCI at membase 0xff020000, IRQ 56
host/usb-ohci.c: usb-, ep93xx
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 3 ports detected
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <email@hidden>
hid-core.c: USB HID support drivers
usb.c: registered new driver audio
audio.c: v1.0.0:USB Audio Class driver
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
ip_tables: (C) 2000-2002 Netfilter core team
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NetWinder Floating Point Emulator V0.97 (double precision)
 /dev/ide/host1/bus0/target0/lun0: p1
 /dev/ide/host1/bus0/target0/lun0: p1
 /dev/ide/host1/bus0/target0/lun0: p1
 /dev/ide/host1/bus0/target0/lun0: p1
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 72K
init started:  BusyBox v1.00 (2006.01.04-15:04+0000) multi-call binary
Starting fsck for root filesystem.
fsck 1.25 (20-Sep-2001)
fsck.ext2: Bad magic number in super-block while trying to open /dev/ram0
(null):
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

WARNING: Error while checking root filesystem.
You can login as root now, the system will reboot after logout.

Give root password for system maintenance
(or type Control-D for normal startup):


以上です