[Harry Zink]
> Doing fdisk /dev/hdf works just fine.
> Doing fdisk /dev/hdg or /dev/hdk results in the old 'unable to open
> hdj/hdk'
ls -l /dev/hd[gk]* ... you make need a later MAKEDEV (or edit yours)
to create all the necessary files
> Alright, try turning off the RAID again ... raidstop -all or raidstop
> /dev/md0.
> This generates the following:
> raidstop /dev/md0
> /dev/md0: Device or resource busy
mounted filesystem... clear processes using it and umount it
(show df output too)
> So, this time it won't let go of hdj and hdk (I moved the drives
> around during the rebuild), which *DO* exist, and whose partition ID I
> can't change (even though it is currently blank/unformatted) becaused
> I can't use fdisk...
>
> md0 : active raid0 hdh1[1] hdg1[0] 19806976 blocks 16k chunks
md is using hdh1 and hdg1 ... it's not using hdj or hdk
If you wish them (hdh1, hdg1) to not get run automatically, fdisk them
and set the type back to 83 from fd (the autorun consideration proves
all these partitions are still "fd")
These are all the same things hashed over before, so no, I don't really
expect this email to have any real consequence. *sigh*
James
