Re: letting go of a twed disk

On Sun, 5 Jun 2005, Randy Bush wrote:

> -current i386 as of feb 6
>
> while replacing things on a raid array, a new twed unit has
> appeared and become un-removable
>
>     # of units: 4
> 	    Unit 0: RAID 5 931.31 GB ( 1953116672 blocks): OK
> 	    Unit 1: JBOD 232.83 GB ( 488281250 blocks): OK
> 	    Unit 5: JBOD 34.47 GB ( 72303840 blocks): OK
> 	    Unit 6: JBOD 232.88 GB ( 488397168 blocks): OK
>
>     3ware CLI> maint deleteunit c0 u1
>     Deleting unit /c0/u1 ...Failed.
>     (0x0B:0x0015): Failed to notify os of unit change

You're trying to delete a plain disk here.

> looks like the opsys has latched on to it
>
>     # fdisk twed2

careful ...

>     ******* Working on device /dev/twed2 *******
>     parameters extracted from in-core disklabel are:
>     cylinders=30401 heads=255 sectors/track=63 (16065 blks/cyl)
>
>     Figures below won't work with BIOS for partitions not in cyl 1
>     parameters to be used for BIOS calculations are:
>     cylinders=30401 heads=255 sectors/track=63 (16065 blks/cyl)
>
>     fdisk: invalid fdisk partition table found

Everything past this point is bogus in the fdisk output.

> is there any way to get the opsys to let go of it so i can
> deleteunit it and make it a spare?

Typically you need to umount any filesystem(s) mounted on that device.

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite_at_gumbysoft.com          |  www.FreeBSD.org