7 messages in org.freebsd.freebsd-scsiRe: mly problem (AR 170)| From | Sent On | Attachments |
|---|---|---|
| Clemens Hermann | May 16, 2001 12:06 pm | |
| Chris Dillon | May 16, 2001 1:46 pm | |
| Clemens Hermann | May 17, 2001 2:42 am | |
| Clemens Hermann | May 17, 2001 3:03 am | |
| Chris Dillon | May 17, 2001 10:01 am | |
| Chris Dillon | May 17, 2001 10:05 am | |
| Clemens Hermann | May 17, 2001 1:23 pm |
| Subject: | Re: mly problem (AR 170) | |
|---|---|---|
| From: | Chris Dillon (cdil...@wolves.k12.mo.us) | |
| Date: | May 16, 2001 1:46:28 pm | |
| List: | org.freebsd.freebsd-scsi | |
On Wed, 16 May 2001, Clemens Hermann wrote:
today I installed a mylex AcceleRaid 170 on FreeBSD 4.3 Release. I have two mirrors which worked right out of the box (da0/da1). The only problem: when I boot the system I get the following messages:
mly0: physical device 0:6 gone mly0: physical device 0:6 gone mly0: enclosure 6 unit 0 access offlinemly0: physical device 0:6 gone mly0: physical device 0:6 gone
There does no such disk exist, according to the controller-setup this is the processor. Are these messages a problem?
Shouldn't be. I had problems with the enclosure management processor on the system I'm using, but Mike Smith fixed the mly driver recently and alleviated the problem. That fix should be in 4.3-RELEASE, I believe.
Furthermore: - How can I check the status of the controller/devices? - How will I know when a drive fails? - do any userland tools exist? - is there any docu available?
No userland tools exist yet to manage the controller and its devices, that I know of. With a managed hot-plug enclosure, I'm not sure that you would even need any. I do know that the driver (via the kernel) will emit a warning when a RAID array goes critical. You can test it yourself by simply removing a drive from your redundant array, assuming you have a hot-plug setup. I've done this to test things out, and it works great. As long as you have the controller set up to do automatic rebuilds you should only have to replace the drive and wait for the array to be rebuilt. Once that is done, you will be notified when the array is optimal again.
Here is some dmesg output from a system that booted up with a drive missing from its RAID array, and then automatically rebuilt the array when I inserted the new drive, all while the system was going about its normal business:
mly0: <Mylex AcceleRAID 170> mem 0xfc5fe000-0xfc5fffff irq 10 at device 1.1 on
pci2
mly0: AcceleRAID 170 , 1 channel, firmware 6.00-7-00 (20001214), 32MB RAM
da0 at mly0 bus 1 target 0 lun 0
da0: <RAID 1 critical > Fixed Direct Access SCSI-3 device
da0: 135.168MB/s transfers
da0: 17480MB (35799040 512 byte sectors: 255H 63S/T 2228C)
[ The system is booted and multiuser. Now, I insert the replacement
drive...]
mly0: physical device 0:1 found
mly0: physical device 0:1 automatic rebuild started
mly0: logical device 0 (da0) automatic rebuild started
[ Many minutes pass while the array is rebuilt... ]
mly0: logical device 0 (da0) rebuild completed
mly0: physical device 0:1 rebuild completed
mly0: physical device 0:1 online
mly0: logical device 0 (da0) online
-- Chris Dillon - cdil...@wolves.k12.mo.us - cdil...@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org
To Unsubscribe: send mail to majo...@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message