Re: mismatching vinum configurations
On Sunday, 20 July 2003 at 20:27:00 +0200, Joan Picanyol i Puig wrote: > Hi, > > I had a power failure, and the on-disk configuration for vinum went > bizarre. The logs read from disks are at http://biaix.org/pk/debug/ > (log.$DEVICE files). They're not much help, and a lot of the files are inaccessible. The output of 'vinum dumpconfig' would be easier. > The logs in da0 (barracuda) are the ones obviously wrong, I'm pretty > sure the others are ok. Is this a 'virtually' dead drive? It's not a hardware problem, if that's what you mean. > Can I force vinum to use the other's drive configuration? Yes. > What's the less traumatic way to recover the data? I've never tried this, but a thing you could do is: vinum -> setdaemon 4(turn off config updates) vinum -> read /dev/ad0s1d (or another drive with valid config) vinum -> start This could bring back your entire configuration. If anything goes wrong, it's not serious, because the config updates are turned off. Why do you have two drives on each SCSI disk? > Most of the data is mirrored over da0 & da1, but I can't start any of > the mirrored volumes (I get 'Drive is down') What should I do to access > the mirrored volumes? If 'start' above doesn't work, you can try running a Vinum config file like: drive barracuda device /dev/da0s1f Let me know how it works out. Greg -- See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
Re: Compiling problems
No strange things in the logs. I tried supping to CURRENT aswell - same make buildworld problem. :-( Do you have any more ideas? I don't want to do a complete reinstall. //Tobias ===> share/termcap gzip -cn /usr/src/share/termcap/termcap.5 > termcap.5.gz TERM=dumb TERMCAP=dumb: ex - /usr/src/share/termcap/termcap.src < /usr/src/share/termcap/reorder Incomplete termcap entry *** Error code 1 Stop in /usr/src/share/termcap. *** Error code 1 Stop in /usr/src/share. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Doug White wrote: On Fri, 18 Jul 2003, Tobias Larsson wrote: Hi, The same problem is still there, even after deleting the whole /usr/src and resupping :-( MD5 (/usr/src/share/termcap/termcap.src) = 9301473e4dcf275418c1c88a8894c9a2 Any more ideas? Are you getting any SIGBUS or SIGSEGV warnings in your logs? Something is certainly different with your system than everyone else's... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mismatching vinum configurations
On Sun, Jul 20, 2003 at 08:27:00PM +0200, Joan Picanyol i Puig wrote: > Hi, > > I had a power failure, and the on-disk configuration for vinum went > bizarre. The logs read from disks are at http://biaix.org/pk/debug/ > (log.$DEVICE files). The logs in da0 (barracuda) are the ones obviously > wrong, I'm pretty sure the others are ok. Is this a 'virtually' dead > drive? Can I force vinum to use the other's drive configuration? What's > the less traumatic way to recover the data? I had the same problem twice. Also a power failure. There was no way I could fix it without trauma. I had to do the following (and I'm not joking about the reboots): WARNING: do not follow the steps below if you're not entirely sure what you're doing unless you already have nothing to lose... 1. Nuke the complete configuration, but make sure you know exactly what it was. 2. Reconfigure vinum from scratch in exactly the same way it was before. 3. Reboot the machine. I got kernel panics trying to recover my vinum volumes and that only made matters worse (it always can). 4a.For mirrored volumes you should be able to mark one drive as up, and mark the other(s) as empty (ie manually set the state). This forces a complete resync. Let it finish and reboot the machine afterwards. 4b.For RAID5 volumes you manually have to mark all disks as up and rebuild the parity. After that it's probably good to reboot the machine avoid kernel panics. Reboot twice if you're paranoid. Verify that the parity is ok! 5. fsck(8). 6. Drink lot's of alcoholic beverages to recover yourself after you verified you recovered vinum. 7. Reboot yourself. FYI, -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mismatching vinum configurations
Hi, I had a power failure, and the on-disk configuration for vinum went bizarre. The logs read from disks are at http://biaix.org/pk/debug/ (log.$DEVICE files). The logs in da0 (barracuda) are the ones obviously wrong, I'm pretty sure the others are ok. Is this a 'virtually' dead drive? Can I force vinum to use the other's drive configuration? What's the less traumatic way to recover the data? Most of the data is mirrored over da0 & da1, but I can't start any of the mirrored volumes (I get 'Drive is down') What should I do to access the mirrored volumes? tks -- pica ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
