Hi Dave, You could prepare the replacement drive offline and test it first, provided you have a generic kernel you can do this on any piece of hardware you have lying around. By the way there is no need to install anything, check out a previous answer I wrote, it's for changing RAID levels but the concept is pretty much the same :
http://lists.freebsd.org/pipermail/freebsd-questions/2005-July/092529.html Good luck, Ruben -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Sent: April 11, 2007 7:02 PM To: freebsd-questions@freebsd.org Subject: replacing failing drive Hello, I've got a drive that i'm uncertain if it's failing. It is making an occational clicking noise, which is getting more frequent. I installed smartmontools and tried to start them, output below: #smartctl -a /dev/ad0 smartctl version 5.37 [i386-portbld-freebsd6.1] Copyright (C) 2002-6 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. #/usr/local/etc/rc.d/smartd start Starting smartd. (pass0:vpo0:0:5:0): INQUIRY. CDB: 12 0 0 0 24 0 (pass0:vpo0:0:5:0): CAM Status: Command timeout (pass0:vpo0:0:5:0): INQUIRY. CDB: 12 0 0 0 40 0 (pass0:vpo0:0:5:0): CAM Status: Command timeout (pass0:vpo0:0:5:0): Vendor Specific Command. CDB: 85 8 e 0 0 0 1 0 0 0 0 0 0 0 ec 0 (pass0:vpo0:0:5:0): CAM Status: Command timeout (pass0:vpo0:0:5:0): Vendor Specific Command. CDB: 85 8 e 0 0 0 1 0 0 0 0 0 0 0 a1 0 (pass0:vpo0:0:5:0): CAM Status: Command timeout Does this mean this drive is failing? I've got another identical drive that i run smartd on and it doesn't have any issues picking up it's smart id or in running tests on it. This is on a 6.2 box. If this drive is failing i'd like to drop in another one with minimum downtime. Could someone check my procedure: 1. Install new drive as slave 2. Use sysinstall to partition the new drive (i only use a single partition) 3. Use sysinstall to create bsd labels and give them the same values as the master drive 4. Use sysinstall to install the boot manager on slave drive 5. Use dump/restore to copy all data on to the slave drive. 6. Power down the box, remove old master drive, set new drive to master, and reboot Thanks. Dave. _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.446 / Virus Database: 269.2.0/756 - Release Date: 4/10/2007 10:44 PM -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.446 / Virus Database: 269.2.0/756 - Release Date: 04/10/2007 10:44 PM _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
