Date: Fri, 09 Aug 2002 22:08:53 +0930 (CST) From: Jarrod Sayers <Jarrod.Sayers@unisa.edu.au> To: freebsd-stable@freebsd.org Subject: atacontrol wont release a disk? Message-ID: <20020809215948.Q5984-100000@dogbert.magill.unisa.edu.au>
next in thread | raw e-mail | index | archive | help
People, We had 3 80gb disks in a RAID0 array, created using atacontrol, this has worked a treat. The other day, we changed the 3 80's to 3 160's, built a new array and copied the data over. Ive popped one of the old disks in to a machine and the following keeps appearing on start up. Im fairly sure I deleted the array before taking the drives out but just incase, before I formatted it, i did a 'atacontrol delete 0' which made the error change to what you see below. Before that, it said 0 and 2 were down but 1 was an ST380020A (ad1 didnt appear too). Any ideas on removing it. Its currently in use and working fine, just looks odd.. --- ad0: 6149MB <QUANTUM FIREBALL EX6.4A> [13328/15/63] at ata0-master UDMA33 ad1: 76319MB <ST380020A> [155061/16/63] at ata0-slave UDMA33 ar0: ERROR - array broken ar0: ERROR - array broken ar0: ERROR - array broken ar0: 228957MB <ATA RAID0 array> [29187/255/63] status: BROKEN subdisks: 0 DOWN 1 INVALID no RAID config info on this disk 2 DOWN afd0: 120MB <LS-120 CSMO 05 UHD Floppy> [963/8/32] at ata1-master PIO2 acd0: CDROM <LG CD-ROM CRD-8522B> at ata1-slave PIO4 --- Cheers, Jarrod Sayers Information Strategy and Technology Services University of South Australia Phone: +61 8 8302 4809 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020809215948.Q5984-100000>