Date: Wed, 21 Feb 2001 20:34:01 -0500 From: Greg Lehey <grog@lemis.com> To: Modestas <modestas@ignera.lt> Cc: freebsd-questions@freebsd.org Subject: Re: Vinum problem - help urgently needed Message-ID: <20010221203401.D1215@sydney.worldwide.lemis.com> In-Reply-To: <020801c09cce$1da7dbf0$0201a8c0@ignera.lt>; from modestas@ignera.lt on Thu, Feb 22, 2001 at 02:50:59PM %2B0200 References: <00fd01c096b1$4cead4d0$0201a8c0@ignera.lt> <20010215084222.U60977@wantadilla.lemis.com> <020801c09cce$1da7dbf0$0201a8c0@ignera.lt>
next in thread | previous in thread | raw e-mail | index | archive | help
> X-Mailer: Microsoft Outlook Express 5.00.3018.1300 [Format recovered--see http://www.lemis.com/email/email-format.html] Your MUA mutilates quoted text. On Thursday, 22 February 2001 at 14:50:59 +0200, Modestas wrote: > > Thanks for suggestions. > > I have successfully mounted vinum volume without fsck (and even without > setting down any of plexes) and have copied all the data. After that I ha= ve > recreated vinum volume, and the logs are clear now, and system works fine, > so the reason for the problems is still unknown. Read what I said below. Your problem is almost certainly flaky hardware, and there's a good chance it will happen again. Greg > ----- Original Message ----- > From: "Greg Lehey" <grog@lemis.com> > To: "Modestas" <modestas@ignera.lt> > Sent: Thursday, February 15, 2001 12:12 AM > Subject: Re: Vinum problem - help urgently needed > > >> [Format recovered--see http://www.lemis.com/email/email-format.html] >> >> On Wednesday, 14 February 2001 at 20:09:39 +0200, Modestas wrote: >>> X-MSMail-Priority: Normal >>> X-Mailer: Microsoft Outlook Express 5.00.3018.1300 >> >> Please don't writ one line per paragraph. Please don't wrap log >> output. >> >>> After replacing the motherboard I have started the server and sytem >>> stopped saying that vinum volume is crashed. I have noticed that one >>> of my IDE connectors wan't connected. After conecting the drive and >>> starting vinum said that one of plexes is faulty another is >>> crashed. I have started both plexes manually. 1st plex has started >>> succesfully, another revived and started also. Now I'm not able to >>> run fsck on vinum volume - it says : >>> >>> ** /dev/vinum/ignera >>> BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALT= ERNATE >>> /dev/vinum/vinum0: INCOMPLETE LABEL: type 4.2BSD fsize 1024, frag 8, cp= g 0, size 39034880 >>> >>> Previously whole system was working succesfully appr. 10 months. >>> >>> System FreeBSD 4.2 stable, compiled from sources. >>> >>> 14 Feb 2001 21:26:22.942699 *** vinum started *** >>> 14 Feb 2001 21:26:24.721319 list >>> 14 Feb 2001 21:26:40.748143 stop ignera.p1 >>> 14 Feb 2001 21:26:44.526115 list >>> 14 Feb 2001 21:26:49.959260 quit >>> 14 Feb 2001 21:27:06.941978 *** vinum started *** >>> 14 Feb 2001 21:27:08.939598 list >>> 14 Feb 2001 21:27:20.642377 start ignera.p1 >>> 14 Feb 2001 21:27:30.557362 stop ignera.p0 >> >> I'm not sure what you're doing here, and the output in >> /var/log/messages is missing. I'm guessing, though, that this isn't >> your problem. >> >>> Feb 14 17:28:06 server01 syslogd: exiting on signal 15 >>> Feb 14 19:01:58 server01 /kernel: ts of the Univer=F3ity of California.= All riwhts re{ervel. >>> Feb 14 19:01:58 server01 /kernel: Fvee=C2SD 4=AE=B2-STABLE #5: Wu=E4$No= v 22 08:5y:54 EET 2800 >>> Feb 14 19:01:58 server01 /kernel: ` root@server01.igner=E1.ba|t=AEnet:/= usr/src/sys/co=EDpil=E5/I=07NERQ >>> Feb 14 19:01:58 server01 /kernel: =D4imecounter "i9254" fruqw=E5ncy 11= 93182 Hz >>> Feb 14 19:01:58 server01 /kernel: Timecounter &TSC" =A6reyuency 349269= 014$Hz >>> Feb 14 19:01:58 server01 /kernel: CP]: Penti=F5m II/Pentiu=ED II0Xeon/A= uleron (34y.07-MHz 686-cla=F3s CPU) >>> Feb 14 19:01:58 server01 /kernel: _rigi=EE =3D "Ge=EEuioeIntel# Id =3D= 0=F8652" Stepping =3D 2 >>> Feb 14 19:01:58 server01 /kernel: Features?4x183f9ff=3DFPU,V]E,DE,PSE= =ACTSC,MSR<PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV, PaT,QSE36,MM=D8,FXSR> >>> Feb 14 19:01:58 server01 /kernel: real me}ory =3D 933=3D=B555x4 h134x1= 6K bytes) >>> Feb 14 19:01:58 server01 /kernel: a~ail mem=EFry =3D 127369216 (124784K= bytes) >> >> Well, it doesn't take a genius to recognize that something is >> seriously wrong here. I'd guess that either disk or controller has >> died and not realised it. I'm afraid you're in for some serious >> recovery. >> >>> Any help will be appreciated. All the data and backups of data are >>> in the vinum volume. >> >> Well, if you're very lucky, you might be able to get plex 1 up and >> running. Use "setstate" to set the states of plex 0 and subdisks to >> 'down', and the states of plex 0 and subdisks to 'up'. Don't try >> fsck, just mount read-only and copy to tape. You're probably better >> off if you don't do this until you repair the hardware damage. >> >> Vinum is good for many things, but I think you've found a problem >> where it can't help. >> >> Greg >> -- >> When replying to this message, please take care not to mutilate the >> original text. >> For more information, see http://www.lemis.com/email.html >> Finger grog@lemis.com for PGP public key >> See complete headers for address and phone numbers >> >> > -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply. For more information, see http://www.lemis.com/questions.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010221203401.D1215>