[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
mlx0 not finding ld on failure?
I just had a disk array (temporarily) die on my 1000A, with some
unexpected results with NetBSD-5.
from a good boot:
NetBSD 5.2_STABLE (ARWEN-based on GENERIC $Revision: 1.343 $) #0: Mon Jun 24
23:08:44 PDT 2013
AlphaServer 1000A 5/400, 400MHz, s/n
mlx0 at pci0 dev 12 function 0: Mylex RAID (v2 interface)
mlx0: interrupting at dec_1000a irq 3
mlx0: DAC960P/PD, 3 channels, firmware 2.70-0-00, 32MB RAM
ld0 at mlx0 unit 0: RAID5, online
ld0: 16380 MB, 8320 cyl, 64 head, 63 sec, 512 bytes/sect x 33546240 sectors
ld1 at mlx0 unit 1: RAID5, online
ld1: 32768 MB, 8322 cyl, 128 head, 63 sec, 512 bytes/sect x 67108864 sectors
ld2 at mlx0 unit 2: RAID5, online
ld2: 32768 MB, 8322 cyl, 128 head, 63 sec, 512 bytes/sect x 67108864 sectors
ld3 at mlx0 unit 3: RAID5, online
ld3: 4536 MB, 2304 cyl, 64 head, 63 sec, 512 bytes/sect x 9289728 sectors
ld1-3 are on an external disk array, which was not available due a power
SRM and ARC both saw that ld0 was OK and ld1-3 were offline, SRM could
still boot the kernel from ld0. the kernel did not see *any* ld
devices, leaving me dead in the water until I was able to move the
drives to another enclosure and run the storageworks configuration
utility to mark them as optimal again.
known issue, or send-pr time?
Aaron J. Grier | "Not your ordinary poofy goof." |
Main Index |
Thread Index |