Re: Vinum or HD error?
On Sunday, 1 February 2004 at 12:42:31 -0600, Hari Bhaskaran wrote: Hi, here is a transcript of vinum reporting an HD failure. I just want to confirm this is really a HD error before the throw the HD out the window vinum volume fs5 is really not mirrored (~ 29G of only 1 120g disk mapped as such via vinum). OS: 4.7-RELEASE-p24 Feb 1 11:58:44 mach01 /kernel: ad1s1e: hard error reading fsbn 362562737 of 177087033-177087048 (ad1s1 bn 362562737; cn 22568 tn 124 sn 5) trying PIO mode Feb 1 11:58:45 mach01 /kernel: ad1s1e: hard error reading fsbn 362562737 of 177087033-177087048 (ad1s1 bn 362562737; cn 22568 tn 124 sn 5) status=59 error=40 Yes. These errors come from the disk driver. It's possible that reformatting the drive might help, but I certainly wouldn't rely on that drive again. Feb 1 11:58:45 mach01 /kernel: vinum: fs5.p0.s0 is crashed by force Feb 1 11:58:45 mach01 /kernel: vinum: fs5.p0 is faulty Feb 1 11:58:45 mach01 /kernel: vinum: fs5 is down Feb 1 11:58:45 mach01 /kernel: fatal:fs5.p0.s0 read error, block 177087033 for 8192 bytes Feb 1 11:58:45 mach01 /kernel: fs5.p0.s0: user buffer block 7217456 for 8192 bytes These error messages come from Vinum. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgp0.pgp Description: PGP signature
Vinum or HD error?
Hi, here is a transcript of vinum reporting an HD failure. I just want to confirm this is really a HD error before the throw the HD out the window vinum volume fs5 is really not mirrored (~ 29G of only 1 120g disk mapped as such via vinum). OS: 4.7-RELEASE-p24 Feb 1 11:58:44 mach01 /kernel: ad1s1e: hard error reading fsbn 362562737 of 177087033-177087048 (ad1s1 bn 362562737; cn 22568 tn 124 sn 5) trying PIO mode Feb 1 11:58:45 mach01 /kernel: ad1s1e: hard error reading fsbn 362562737 of 177087033-177087048 (ad1s1 bn 362562737; cn 22568 tn 124 sn 5) status=59 error=40 Feb 1 11:58:45 mach01 /kernel: vinum: fs5.p0.s0 is crashed by force Feb 1 11:58:45 mach01 /kernel: vinum: fs5.p0 is faulty Feb 1 11:58:45 mach01 /kernel: vinum: fs5 is down Feb 1 11:58:45 mach01 /kernel: fatal:fs5.p0.s0 read error, block 177087033 for 8192 bytes Feb 1 11:58:45 mach01 /kernel: fs5.p0.s0: user buffer block 7217456 for 8192 bytes Any help is appreciated -- Hari Bhaskaran ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Vinum or HD error?
I fixed some similar problems by changing the drive cable. but I am by no means an expert on this. Micheas On Sun, 2004-02-01 at 10:42, Hari Bhaskaran wrote: Hi, here is a transcript of vinum reporting an HD failure. I just want to confirm this is really a HD error before the throw the HD out the window vinum volume fs5 is really not mirrored (~ 29G of only 1 120g disk mapped as such via vinum). OS: 4.7-RELEASE-p24 Feb 1 11:58:44 mach01 /kernel: ad1s1e: hard error reading fsbn 362562737 of 177087033-177087048 (ad1s1 bn 362562737; cn 22568 tn 124 sn 5) trying PIO mode Feb 1 11:58:45 mach01 /kernel: ad1s1e: hard error reading fsbn 362562737 of 177087033-177087048 (ad1s1 bn 362562737; cn 22568 tn 124 sn 5) status=59 error=40 Feb 1 11:58:45 mach01 /kernel: vinum: fs5.p0.s0 is crashed by force Feb 1 11:58:45 mach01 /kernel: vinum: fs5.p0 is faulty Feb 1 11:58:45 mach01 /kernel: vinum: fs5 is down Feb 1 11:58:45 mach01 /kernel: fatal:fs5.p0.s0 read error, block 177087033 for 8192 bytes Feb 1 11:58:45 mach01 /kernel: fs5.p0.s0: user buffer block 7217456 for 8192 bytes Any help is appreciated -- Hari Bhaskaran ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Write in TERRY BAUM for Congress on March 2, 2004 http://www.terrybaum.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Vinum or HD error?
On Sun, Feb 01, 2004 at 02:47:16PM -0500, dave wrote: Hello, Can you tell me about your vinum setup? Are you using IDE or scsi drives? What raidlevel are you using? And, do you have your root partition Two IDE drives, 120G each (1 WD, 1 maxtor), although this particular volume in Q is *not* mirrored at all - it is only on one drive. This volume doesn't contain any critical data and I am not trying to recover any data out of it. I am just trying to figure out what happened for my own knowledge and to know whether to replace the HD etc. I thought those error code (in my earlier mail) might say something. The output of vinum list is given below No, the root partition is not raided - that wasn't possible in 4.7 (yes, there is an inactive copy, but no thru vinum) # vinum list 2 drives: D regalis State: up Device /dev/ad0s1e Avail: 0/110374 MB (0%) D formosa State: up Device /dev/ad1s1e Avail: 0/113143 MB (0%) 11 volumes: V varbase State: up Plexes: 2 Size: 3072 MB V varlogState: up Plexes: 2 Size: 1024 MB V vartmpState: up Plexes: 2 Size: 1024 MB V tmp State: up Plexes: 2 Size: 3072 MB V usrbase State: up Plexes: 2 Size: 3072 MB V usrhome State: up Plexes: 2 Size: 3072 MB V fs1 State: up Plexes: 2 Size: 2048 MB V fs2 State: up Plexes: 2 Size: 25 GB V fs3 State: up Plexes: 2 Size: 40 GB V fs4 State: up Plexes: 1 Size: 26 GB V fs5 State: down Plexes: 1 Size: 29 GB 20 plexes: P varbase.p0 C State: up Subdisks: 1 Size: 3072 MB P varbase.p1 C State: up Subdisks: 1 Size: 3072 MB P varlog.p0 C State: up Subdisks: 1 Size: 1024 MB P varlog.p1 C State: up Subdisks: 1 Size: 1024 MB P vartmp.p0 C State: up Subdisks: 1 Size: 1024 MB P vartmp.p1 C State: up Subdisks: 1 Size: 1024 MB P tmp.p0 C State: up Subdisks: 1 Size: 3072 MB P tmp.p1 C State: up Subdisks: 1 Size: 3072 MB P usrbase.p0 C State: up Subdisks: 1 Size: 3072 MB P usrbase.p1 C State: up Subdisks: 1 Size: 3072 MB P usrhome.p0 C State: up Subdisks: 1 Size: 3072 MB P usrhome.p1 C State: up Subdisks: 1 Size: 3072 MB P fs1.p0 C State: up Subdisks: 1 Size: 2048 MB P fs1.p1 C State: up Subdisks: 1 Size: 2048 MB P fs2.p0 C State: up Subdisks: 1 Size: 25 GB P fs2.p1 C State: up Subdisks: 1 Size: 25 GB P fs3.p0 C State: up Subdisks: 1 Size: 40 GB P fs3.p1 C State: up Subdisks: 1 Size: 40 GB P fs4.p0 C State: up Subdisks: 1 Size: 26 GB P fs5.p0 C State: faulty Subdisks: 1 Size: 29 GB 20 subdisks: S varbase.p0.s0 State: up PO:0 B Size: 3072 MB S varbase.p1.s0 State: up PO:0 B Size: 3072 MB S varlog.p0.s0 State: up PO:0 B Size: 1024 MB S varlog.p1.s0 State: up PO:0 B Size: 1024 MB S vartmp.p0.s0 State: up PO:0 B Size: 1024 MB S vartmp.p1.s0 State: up PO:0 B Size: 1024 MB S tmp.p0.s0 State: up PO:0 B Size: 3072 MB S tmp.p1.s0 State: up PO:0 B Size: 3072 MB S usrbase.p0.s0 State: up PO:0 B Size: 3072 MB S usrbase.p1.s0 State: up PO:0 B Size: 3072 MB S usrhome.p0.s0 State: up PO:0 B Size: 3072 MB S usrhome.p1.s0 State: up PO:0 B Size: 3072 MB S fs1.p0.s0 State: up PO:0 B Size: 2048 MB S fs1.p1.s0 State: up PO:0 B Size: 2048 MB S fs2.p0.s0 State: up PO:0 B Size: 25 GB S fs2.p1.s0 State: up PO:0 B Size: 25 GB S fs3.p0.s0 State: up PO:0 B Size: 40 GB S fs3.p1.s0 State: up PO:0 B Size: 40 GB S fs4.p0.s0 State: up PO:0 B Size: 26 GB S fs5.p0.s0 State: crashed PO:0 B Size: 29 GB raided? Thanks. Dave. -- Hari Bhaskaran ___ [EMAIL
