José M. Fandiño
2006-Apr-05 15:00 UTC
GEOM_RAID3: Device datos is broken, too few valid components
Hello list, Last night one disk of my desktop machine dead causing a hard lock of the computer. It was a component of a mirror volume so it wasn't as serious as it initially looked. Unfortunately, the metadata structure of my data partition (a geom raid3 array with tree components ) seems to be corrupted by this hard lock, the following message is scrolled constantly on the screen: GEOM_RAID3: Device datos created (id=3217021940). GEOM_RAID3: Device datos: provider ad6s2 detected. GEOM_RAID3: Device datos: provider ad5s2 detected. GEOM_RAID3: Device datos: provider ad4s2 detected. GEOM_RAID3: Component ad6s2 (device datos) broken, skipping. GEOM_RAID3: Component ad4s2 (device datos) broken, skipping. GEOM_RAID3: Device datos is broken, too few valid components. GEOM_RAID3: Device datos destroyed. Checking the search engine results it isn't a very usual problem, the advice in the returned hits is rerunning "graid label -h datos ad4s2 ad5s2 ad6s2", but before of erasing all my data I would like to ask to list members. How dangerous is running the mentioned command in this context? Thank you. Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-PRERELEASE #2: Fri Mar 24 01:46:58 CET 2006 root@:/usr/local/obj/usr/local/src/sys/HOME ACPI APIC Table: <Nvidia AWRDACPI> Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) XP 2800+ (2079.56-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0 Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE> AMD Features=0xc0400800<SYSCALL,MMX+,3DNow+,3DNow> real memory = 536805376 (511 MB) avail memory = 515940352 (492 MB) ioapic0 <Version 1.1> irqs 0-23 on motherboard bktr_mem: memory holder loaded npx0: [FAST] npx0: <math processor> on motherboard npx0: INT 16 interface acpi0: <Nvidia AWRDACPI> on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: <ACPI CPU> on acpi0 acpi_button0: <Power Button> on acpi0 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff,0xcf0-0xcf3 on acpi0 pci0: <ACPI PCI bus> on pcib0 agp0: <NVIDIA nForce2 AGP Controller> mem 0xe0000000-0xe3ffffff at device 0.0 on pci0 pci0: <memory, RAM> at device 0.1 (no driver attached) pci0: <memory, RAM> at device 0.2 (no driver attached) pci0: <memory, RAM> at device 0.3 (no driver attached) pci0: <memory, RAM> at device 0.4 (no driver attached) pci0: <memory, RAM> at device 0.5 (no driver attached) isab0: <PCI-ISA bridge> at device 1.0 on pci0 isa0: <ISA bus> on isab0 pci0: <serial bus, SMBus> at device 1.1 (no driver attached) ohci0: <OHCI (generic) USB controller> mem 0xec003000-0xec003fff irq 20 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: <OHCI (generic) USB controller> on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: <OHCI (generic) USB controller> mem 0xec004000-0xec004fff irq 21 at device 2.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: <OHCI (generic) USB controller> on ohci1 usb1: USB revision 1.0 uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ehci0: <NVIDIA nForce2 USB 2.0 controller> mem 0xec005000-0xec0050ff irq 22 at device 2.2 on pci0 ehci0: [GIANT-LOCKED] usb2: EHCI version 1.0 usb2: companion controllers, 4 ports each: usb0 usb1 usb2: <NVIDIA nForce2 USB 2.0 controller> on ehci0 usb2: USB revision 2.0 uhub2: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 6 ports with 6 removable, self powered pci0: <multimedia, audio> at device 6.0 (no driver attached) pcib1: <ACPI PCI-PCI bridge> at device 8.0 on pci0 pci1: <ACPI PCI bus> on pcib1 re0: <RealTek 8169S Single-chip Gigabit Ethernet> port 0x9000-0x90ff mem 0xeb006000-0xeb0060ff irq 16 at device 11.0 on pci1 miibus0: <MII bus> on re0 rgephy0: <RTL8169S/8110S media interface> on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto re0: Ethernet address: 00:0d:61:78:cf:2f atapci0: <ITE IT8212F UDMA133 controller> port 0x9410-0x9417,0x9800-0x9803,0x9c10-0x9c17,0xa000-0xa003,0xa400-0xa40f irq 17 at device 12.0 on pci1 ata2: <ATA channel 0> on atapci0 ata3: <ATA channel 1> on atapci0 pci1: <serial bus, FireWire> at device 14.0 (no driver attached) atapci1: <nVidia nForce2 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 9.0 on pci0 ata0: <ATA channel 0> on atapci1 ata1: <ATA channel 1> on atapci1 pcib2: <ACPI PCI-PCI bridge> at device 30.0 on pci0 pci2: <ACPI PCI bus> on pcib2 drm0: <ATI Rage 128 Pro PF (AGP)> port 0xc000-0xc0ff mem 0xe4000000-0xe7ffffff,0xe9000000-0xe9003fff irq 19 at device 0.0 on pci2 info: [drm] AGP at 0xe0000000 64MB info: [drm] Initialized r128 2.5.0 20030725 speaker0: <PC speaker> port 0x61 on acpi0 fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: <Standard parallel printer port> port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: <Parallel port bus> on ppc0 plip0: <PLIP network interface> on ppbus0 lpt0: <Printer> on ppbus0 lpt0: Interrupt-driven port ppi0: <Parallel I/O> on ppbus0 atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0 atkbd0: <AT Keyboard> irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: <PS/2 Mouse> irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model MouseMan+, device ID 0 pmtimer0 on isa0 orm0: <ISA Option ROMs> at iomem 0xc0000-0xcbfff,0xcc000-0xcd7ff on isa0 sc0: <System console> at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 2079563677 Hz quality 800 Timecounters tick every 1.000 msec ad0: 38166MB <Seagate ST340823A 3.32> at ata0-master UDMA100 acd0: DVDROM <TOSHIBA DVD-ROM SD-M1612/1004> at ata0-slave UDMA33 acd1: DVDR <HL-DT-ST DVDRAM GSA-4081B/A100> at ata1-slave UDMA33 ad4: 152627MB <Seagate ST3160021A 8.01> at ata2-master UDMA100 ad5: 152627MB <Seagate ST3160021A 8.01> at ata2-slave UDMA100 ad6: 152627MB <Seagate ST3160021A 8.01> at ata3-master UDMA100 cd1 at ata1 bus 0 target 1 lun 0 cd1: <HL-DT-ST DVDRAM GSA-4081B A100> Removable CD-ROM SCSI-0 device cd1: 33.000MB/s transfers cd1: cd present [1 x 2048 byte records] cd0 at ata0 bus 0 target 1 lun 0 cd0: <TOSHIBA DVD-ROM SD-M1612 1004> Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present GEOM_RAID3: Device datos created (id=3217021940). GEOM_RAID3: Device datos: provider ad4s2 detected. GEOM_RAID3: Device datos: provider ad5s2 detected. GEOM_RAID3: Device datos: provider ad6s2 detected. GEOM_RAID3: Component ad6s2 (device datos) broken, skipping. GEOM_RAID3: Component ad4s2 (device datos) broken, skipping. GEOM_RAID3: Device datos is broken, too few valid components. GEOM_RAID3: Device datos destroyed. GEOM_MIRROR: Device home created (id=1272328468). GEOM_MIRROR: Device home: provider ad0s4d detected. GEOM_MIRROR: Device local created (id=3856788567). GEOM_MIRROR: Device local: provider ad0s4e detected. Root mount waiting for: GMIRROR GMIRROR Root mount waiting for: GMIRROR GMIRROR Root mount waiting for: GMIRROR GMIRROR Root mount waiting for: GMIRROR GMIRROR GEOM_MIRROR: Force device home start due to timeout. GEOM_MIRROR: Device home: provider ad0s4d activated. GEOM_MIRROR: Device home: provider mirror/home launched. WARNING: Expected rawoffset 0, found 13446405 Root mount waiting for: GMIRROR GEOM_MIRROR: Force device local start due to timeout. GEOM_MIRROR: Device local: provider ad0s4e activated. GEOM_MIRROR: Device local: provider mirror/local launched. Trying to mount root from ufs:/dev/ad0s2a -- -----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------
Pawel Jakub Dawidek
2006-Apr-06 15:32 UTC
GEOM_RAID3: Device datos is broken, too few valid components
On Wed, Apr 05, 2006 at 04:58:51PM +0200, Jos? M. Fandi?o wrote: +> Hello list, +> +> Last night one disk of my desktop machine dead causing a hard lock of the +> computer. It was a component of a mirror volume so it wasn't as serious as +> it initially looked. +> +> Unfortunately, the metadata structure of my data partition (a geom raid3 +> array with tree components ) seems to be corrupted by this hard lock, +> the following message is scrolled constantly on the screen: +> +> GEOM_RAID3: Device datos created (id=3217021940). +> GEOM_RAID3: Device datos: provider ad6s2 detected. +> GEOM_RAID3: Device datos: provider ad5s2 detected. +> GEOM_RAID3: Device datos: provider ad4s2 detected. +> GEOM_RAID3: Component ad6s2 (device datos) broken, skipping. +> GEOM_RAID3: Component ad4s2 (device datos) broken, skipping. +> GEOM_RAID3: Device datos is broken, too few valid components. +> GEOM_RAID3: Device datos destroyed. +> +> Checking the search engine results it isn't a very usual problem, the advice +> in the returned hits is rerunning "graid label -h datos ad4s2 ad5s2 ad6s2", +> but before of erasing all my data I would like to ask to list members. +> +> How dangerous is running the mentioned command in this context? 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. Of course (as I understand) one of those broken components was really broken, right? If yes, you should 'graid3 rebuild' it immediatelly after 'label' command. If no, you should still rebuild one of them after labeling it. -- Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20060406/f465958a/attachment.pgp
Seemingly Similar Threads
- Finding which GEOM provider is generating errors in a graid3
- gmirror(8) and graid3(8) changes.
- gmirror+gjournal: unable to boot after crash
- shutdown -r / shutdown -h / reboot all hang and don't cleanly dismount
- GELI partition mount on boot fails after 7.0 -> 7.1-PRERELEASE upgrade