On Mon, Apr 10, 2006 at 03:32:58PM +0200, Jos? M. Fandi?o wrote: > I have follow this procedure and it worked for me: > > select "6. Escape to loader prompt" > OK unload > OK disable-module geom_raid3 > OK boot -s > # fsck -p > # mount -a > # graid3 dump ad4s2 | grep -w no > # graid3 dump ad5s2 | grep -w no > # graid3 dump ad6s2 | grep -w no > (this will give you the right order to use with the next command) > # graid3 label -h ad5s2 ad6s2 ad4s2 > # graid3 load > # graid3 remove -n 0 datos > # graid3 insert -n 0 datos ad5s2 > > now, all is working as expected. However I'm curious about the > missing flag "HARDCODED" for ad5s2. > This is because your "insert" command above didn't include the -h option. The remove/insert could be replaced by "graid3 rebuild datos ad5s2".
> is it reasonable to ignore this missing flag? > You can "graid3 configure -h" it. > # grai3 list > Geom name: datos > State: COMPLETE > Components: 3 > Flags: ROUND-ROBIN > GenID: 0 > SyncID: 1 > ID: 1391160618 > Providers: > 1. Name: raid3/datos > Mediasize: 311491352576 (290G) > Sectorsize: 1024 > Mode: r1w1e1 > Consumers: > 1. Name: ad4s2 > Mediasize: 155745676800 (145G) > Sectorsize: 512 > Mode: r1w1e1 > State: ACTIVE > Flags: DIRTY, HARDCODED > GenID: 0 > SyncID: 1 > Number: 2 > Type: PARITY > 2. Name: ad5s2 > Mediasize: 155745676800 (145G) > Sectorsize: 512 > Mode: r1w1e1 > State: ACTIVE > Flags: DIRTY > GenID: 0 > SyncID: 1 > Number: 0 > Type: DATA > 3. Name: ad6s2 > Mediasize: 155745676800 (145G) > Sectorsize: 512 > Mode: r1w1e1 > State: ACTIVE > Flags: DIRTY, HARDCODED > GenID: 0 > SyncID: 1 > Number: 1 > Type: DATA Cheers, -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer
pgpUNhHKYOyRS.pgp
Description: PGP signature
