Hello, > > Pawel Jakub Dawidek wrote: > > > You should be safe as long as the order of slices you give here is the > > > same as it was when device was initially labeled.
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. is it reasonable to ignore this missing flag? # 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 -- -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS/IT d- s+:+() a32 C+++ UBL+++$ P+ L+++ E--- W++ N+ o++ K- w--- O+ M+ V- PS+ PE+ Y++ PGP+>+++ t+ 5 X+$ R- tv-- b+++ DI D++>+++ G++ e- h+(++) !r !z ------END GEEK CODE BLOCK------ _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
