After replacing the primary drive on a Raq4 raid array the GUI continues to
report
the raid drive failure with a flashing red alert. Anyway to clear this?
It's been over 48 hours and I beleive the drive is now formated and
mirroring again.
Tony
Heres the results of cat /proc/mdstat:
Personalities : [linear] [raid0] [raid1] [raid5] [translucent]
read_ahead 1024 sectors
md1 : active raid1 hdc1[1] 768000 blocks [2/1] [_U]
md3 : active raid1 hdc3[1] 205056 blocks [2/1] [_U]
md4 : active raid1 hdc4[1] 18869696 blocks [2/1] [_U]
md6 : active raid1 hdc6[1] 131456 blocks [2/1] [_U]
unused devices: <none>
And heres the output from dmesg:
Linux version 2.2.16C27_III (root@xxxxxxxxxxxxxxxx) (gcc version
egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Thu Jun 14 17:21:17 PDT
2001
Detected 448219 kHz processor.
Pending 0x00
Calibrating delay loop... 894.57 BogoMIPS
Memory: 257572k/262144k available (1244k kernel code, 416k reserved, 2848k
data, 64k init)
Dentry hash table entries: 32768 (order 6, 256k)
Buffer cache hash table entries: 262144 (order 8, 1024k)
Page cache hash table entries: 65536 (order 6, 256k)
VFS: Diskquotas version dquot_6.4.0 initialized
CPU: L1 I Cache: 32K L1 D Cache: 32K
CPU: AMD AMD-K6(tm) 3D processor stepping 0c
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.35a (19990819) Richard Gooch (rgooch@xxxxxxxxxxxxx)
PCI: Using configuration type 1
PCI: Probing PCI hardware
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
TCP: Hash tables configured (ehash 262144 bhash 65536)
Initializing RT netlink socket
Starting kswapd v 1.5
Cobalt watchdog v1.4 enabled
Cobalt I2C bus initialized
Cobalt temperature sensor v1.3 enabled
Serial driver version 4.27 with no serial options enabled
keyboard: Timeout - AT keyboard not present?
keyboard: Timeout - AT keyboard not present?
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
pty: 256 Unix98 ptys configured
Real Time Clock Driver v1.09
lcd: Cobalt LCD Driver v3.12
serialnumber: Version 1.9 initialized. Serial number=2a0000074b8dc801.
Copyright (c)1994-2000 Axent Technologies, Inc.
Uniform Multi-Platform E-IDE driver Revision: 6.30
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ALI15X3: IDE controller on PCI bus 00 dev 78
ALI15X3: chipset revision 193
ALI15X3: 100% native mode on irq 14
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
hda: ST320413A, ATA DISK drive
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
hdc: ST320423A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: ST320413A, 19092MB w/512kB Cache, CHS=38792/16/63, UDMA(33)
hdc: ST320423A, 19536MB w/512kB Cache, CHS=39693/16/63, UDMA(33)
md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
translucent personality registered
linear personality registered
raid0 personality registered
raid1 personality registered
raid5 personality registered
raid5: measuring checksumming speed
raid5: MMX detected, trying high-speed MMX checksum routines
pII_mmx : 942.594 MB/sec
p5_mmx : 872.871 MB/sec
8regs : 440.817 MB/sec
32regs : 282.321 MB/sec
using fastest function: pII_mmx (942.594 MB/sec)
sym53c8xx: at PCI bus 0, device 14, function 0
sym53c8xx: 53c875 detected
sym53c875-0: rev 0x4 on pci bus 0 device 14 function 0 irq 12
sym53c875-0: ID 7, Fast-20, Parity Checking
scsi0 : sym53c8xx-1.7.3a-20010304
scsi : 1 host.
scsi : detected total.
md.c: sizeof(mdp_super_t) = 4096
Partition check:
hda: unknown partition table
hdc: hdc1 hdc2 < hdc5 hdc6 > hdc3 hdc4
autodetecting RAID arrays
(read) hdc1's sb offset: 768000 [events: 0000006c]
(read) hdc3's sb offset: 205056 [events: 0000006c]
(read) hdc4's sb offset: 18869696 [events: 0000006c]
(read) hdc6's sb offset: 131456 [events: 0000006c]
autorun ...
considering hdc6 ...
adding hdc6 ...
created md6
bind<hdc6,1>
running: <hdc6>
now!
hdc6's event counter: 0000006c
md6: max total readahead window set to 128k
md6: 1 data-disks, max readahead per data-disk: 128k
raid1: device hdc6 operational as mirror 1
raid1: md6, not all disks are operational -- trying to recover array
raid1: raid set md6 active with 1 out of 2 mirrors
md: updating md6 RAID superblock on device
hdc6 [events: 0000006d](write) hdc6's sb offset: 131456
md: recovery thread got woken up ...
md: recovery thread finished ...
.
considering hdc4 ...
adding hdc4 ...
created md4
bind<hdc4,1>
running: <hdc4>
now!
hdc4's event counter: 0000006c
md4: max total readahead window set to 128k
md4: 1 data-disks, max readahead per data-disk: 128k
raid1: device hdc4 operational as mirror 1
raid1: md4, not all disks are operational -- trying to recover array
raid1: raid set md4 active with 1 out of 2 mirrors
md: updating md4 RAID superblock on device
hdc4 [events: 0000006d](write) hdc4's sb offset: 18869696
md: recovery thread got woken up ...
md: recovery thread finished ...
.
considering hdc3 ...
adding hdc3 ...
created md3
bind<hdc3,1>
running: <hdc3>
now!
hdc3's event counter: 0000006c
md3: max total readahead window set to 128k
md3: 1 data-disks, max readahead per data-disk: 128k
raid1: device hdc3 operational as mirror 1
raid1: md3, not all disks are operational -- trying to recover array
raid1: raid set md3 active with 1 out of 2 mirrors
md: updating md3 RAID superblock on device
hdc3 [events: 0000006d](write) hdc3's sb offset: 205056
md: recovery thread got woken up ...
md: recovery thread finished ...
.
considering hdc1 ...
adding hdc1 ...
created md1
bind<hdc1,1>
running: <hdc1>
now!
hdc1's event counter: 0000006c
md1: max total readahead window set to 128k
md1: 1 data-disks, max readahead per data-disk: 128k
raid1: device hdc1 operational as mirror 1
raid1: md1, not all disks are operational -- trying to recover array
raid1: raid set md1 active with 1 out of 2 mirrors
md: updating md1 RAID superblock on device
hdc1 [events: 0000006d](write) hdc1's sb offset: 768000
md: recovery thread got woken up ...
md: recovery thread finished ...
.
... autorun DONE.
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 64k freed
Adding Swap: 131448k swap-space (priority -1)
Cobalt Networks Bandwidth Limiting Module
Copyright (c) 1999, Cobalt Networks, Inc.
All rights reserved
eth0: Invalid EEPROM checksum 0x98a7, check settings before activating this
device!
eth0: Intel PCI EtherExpress Pro100 82559ER, 00:10:E0:01:C7:86, I/O at
0x6200, IRQ 11.
Board assembly 000000-000, Physical connectors present:
Primary interface chip None PHY #0.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0xdbd8681d).
Receiver lock-up workaround activated.
eth1: Invalid EEPROM checksum 0x32a7, check settings before activating this
device!
eth1: Intel PCI EtherExpress Pro100 82559ER, 00:10:E0:01:C7:20, I/O at
0x6240, IRQ 10.
Board assembly 000000-000, Physical connectors present:
Primary interface chip None PHY #0.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0xdbd8681d).
Receiver lock-up workaround activated.
portmap: RPC call returned error 111
RPC: task of released request still queued!
RPC: (task is on xprt_pending)
portmap: RPC call returned error 111
RPC: task of released request still queued!
RPC: (task is on xprt_pending)
lockd_up: makesock failed, error=-111
portmap: RPC call returned error 111
RPC: task of released request still queued!
RPC: (task is on xprt_pending
_______________________________________________
cobalt-users mailing list
cobalt-users@xxxxxxxxxxxxxxx
To Subscribe or Unsubscribe, please go to:
http://list.cobalt.com/mailman/listinfo/cobalt-users