Date: Wed, 10 Mar 2004 19:28:58 -0500 From: Don Bowman <don@sandvine.com> To: 'Scott Long' <scottl@freebsd.org>, Don Bowman <don@sandvine.com> Cc: "'scsi@freebsd.org'" <scsi@freebsd.org> Subject: RE: ASR, 5.2, rebuild Message-ID: <FE045D4D9F7AED4CBFF1B3B813C85337045D84A2@mail.sandvine.com>
next in thread | raw e-mail | index | archive | help
From: Scott Long [mailto:scottl@freebsd.org] > On Wed, 10 Mar 2004, Don Bowman wrote: > > > > I have a system with a 6-disk raid-5. One of the > > disks failed [light went red on the front > > of the enclosure], and i have now swapped it. > > I'm assuming (although i can't see from the > > manual) that the asr will automatically start > > rebuilding. Is this true? > > > > Since asr-utils no longer work on 5.2, is there a way > > with camcontrol or something to see that it > > is rebuilding, and/or see the progress? I don't > > want to take the machine down to go to the bios. > > > > For a 6-disk raid with 15KRPM 75KB drives, is > > there an estimation for the rebuild time? > > > > The rebuild task is completely transparent to CAM > and the rest of the OS. We really need to get > asrtools working again. I think that someone posted > a hack recently that might allow it to work, but > I'm not sure how reliable it is. So the update on this is that the asr doesn't start the rebuild. I had to reboot, go into the bios, and select rebuild. While it was still rebuilding, i let the machine boot, and now i'm left wondering if the rebuild finished. There as a pr recently which suggested that a link in /etc/devfs.conf of: link rasr0 rdpti0 would help. This makes the device link available. However, asr-utils wants older versions of libstdc++, libc, etc, so make sure you have compat4x. $ raidutil -L physical seems to run ok: Address Type Manufacturer/Model Capacity Status --------------------------------------------------------------------------- d0b1t0d0 Disk Drive (DASD) SEAGATE ST373453LC 70007MB Optimal d0b1t2d0 Disk Drive (DASD) SEAGATE ST373453LC 70007MB Optimal d0b1t4d0 Disk Drive (DASD) SEAGATE ST373453LC 70007MB Failed drive d0b1t5d0 Disk Drive (DASD) SEAGATE ST373453LC 70007MB Optimal d0b1t6d0 Disk Drive (DASD) SEAGATE ST373453LC 70007MB Optimal d0b1t8d0 Processor SUPER GEM359 REV001 ----- Optimal d0b1t9d0 Disk Drive (DASD) SEAGATE ST373453LC 70007MB Optimal The 'Failed Drive' is the one that has been replaced and i would have thought it was rebuilding on. $ raidutil -L spare Gives: Failure:Can't find component by address # ./raidutil -L version # Controller Cache FW NVRAM BIOS SMOR Serial --------------------------------------------------------------------------- d0 ADAP2010S 32MB 3B05 CHNL 1.1 1.62 1.12/79I BD0E40303FA works. so do i now tell raidutil -a rebuild d0b1t0d0 ? # ./raidutil -a verify d0b1t0d0 Invalid command on RAID seems to imply there's some issues. So i ran the rebuild, and now i see: # ./raidutil -L raid Address Type Manufacturer/Model Capacity Status --------------------------------------------------------------------------- d0b1t0d0 RAID 5 (Redundant ADAPTEC RAID-5 350035MB Reconstruct 0% d0b1t0d0 Disk Drive (DASD) SEAGATE ST373453LC 70007MB Optimal d0b1t2d0 Disk Drive (DASD) SEAGATE ST373453LC 70007MB Optimal d0b1t4d0 Disk Drive (DASD) SEAGATE ST373453LC 70007MB Replaced Drive d0b1t5d0 Disk Drive (DASD) SEAGATE ST373453LC 70007MB Optimal d0b1t6d0 Disk Drive (DASD) SEAGATE ST373453LC 70007MB Optimal d0b1t9d0 Disk Drive (DASD) SEAGATE ST373453LC 70007MB Optimal so I guess some things work with asr-utils.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FE045D4D9F7AED4CBFF1B3B813C85337045D84A2>