Date: Thu, 02 Jun 2011 20:20:42 +0200 From: Bartosz Stec <bartosz.stec@it4pro.pl> To: freebsd-fs@freebsd.org Subject: Re: [ZFSv28] Loader hangs, import failes, zfs filesystem unavailable. Message-ID: <4DE7D47A.5070105@it4pro.pl> In-Reply-To: <4DE7C122.2040004@it4pro.pl> References: <4DE7C122.2040004@it4pro.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
W dniu 2011-06-02 18:58, Bartosz Stec pisze: > Hi list, > Today I needed to shut down my home server (FreeSBD9-CURRENT, 3 x 40GB > ATA HDD in RADZ1, ZFS only, GPT, i386) for a moment. After power up, > loader started to spin cursor indifinitely, and didn't load the > kernel. No error messages, no hints, just spinning cursor. > I tried booting from other HDDs in case that bootstrap area errors on > single hdd but no luck. > I wanted to play with latest current LiveFS snapshot (with ZFSv28 > support), but apparently latest one is from february?? > Finally I ended with mfsBSD from http://mfsbsd.vx.sk/ > I've downloaded "8.2-RELEASE-i386 with ZFSv28 special edition > <http://mfsbsd.vx.sk/iso/mfsbsd-se-8.2-zfsv28-i386.iso>" iso, burned > it and booted machine. Here's what happened when i was trying to > import zpool: > > mfsbsd# zpool status > no pools available > mfsbsd# zpool import > pool: zroot > id: 16074929158756467860 > state: ONLINE > status: The pool was last accessed by another system. > action: The pool can be imported using its name or numeric > identifier and > the '-f' flag. > see: http://www.sun.com/msg/ZFS-8000-EY > config: > > zroot ONLINE > raidz1-0 ONLINE > gptid/2ea57c66-bc69-11df-8955-0050dad823cd ONLINE > gptid/5bc92016-6852-11df-a16c-0050dad823cd ONLINE > gptid/87d467cc-bc3b-11df-8066-0050dad823cd ONLINE > mfsbsd# zpool import -f zroot > cannot import 'zroot': one or more devices is currently unavailable > > There was also some kernel messages while running zpool commands, they > are visible at the end of dmesg output: > > mfsbsd# dmesg > Copyright (c) 1992-2011 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 is a registered trademark of The FreeBSD Foundation. > FreeBSD 8.2-RELEASE #2 r219081M: Wed Mar 2 10:29:25 CET 2011 > root@www4:/usr/obj/i386/usr/src_v28/sys/GENERIC i386 > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: mobile AMD Athlon(tm) XP 2200+ (1800.08-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0x681 Family = 6 Model = 8 > Stepping = 1 > > Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE> > AMD Features=0xc0480800<SYSCALL,MP,MMX+,3DNow!+,3DNow!> > real memory = 2147483648 (2048 MB) > avail memory = 2053263360 (1958 MB) > ACPI APIC Table: <AMIINT VIA_K7 > > ioapic0 <Version 0.3> irqs 0-23 on motherboard > kbd1 at kbdmux0 > acpi0: <AMIINT VIA_K7> on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 > cpu0: <ACPI CPU> on acpi0 > acpi_button0: <Power Button> on acpi0 > pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 > pci0: <ACPI PCI bus> on pcib0 > agp0: <VIA 8367 (KT266/KY266x/KT333) host to PCI bridge> on hostb0 > agp0: aperture size is 128M > pcib1: <PCI-PCI bridge> at device 1.0 on pci0 > pci1: <PCI bus> on pcib1 > vgapci0: <VGA-compatible display> mem > 0xdfe80000-0xdfefffff,0xd0000000-0xd7ffffff irq 16 at device 0.0 on > pci1 > xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xec00-0xec7f mem > 0xdfffff80-0xdfffffff irq 17 at device 6.0 on pci0 > miibus0: <MII bus> on xl0 > xlphy0: <3Com internal media interface> PHY 24 on miibus0 > xlphy0: 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, > 100baseTX-FDX, 100baseTX-FDX-flow, auto, auto-flow > xl0: Ethernet address: 00:50:da:d8:23:cd > xl0: [ITHREAD] > rl0: <RealTek 8139 10/100BaseTX> port 0xe800-0xe8ff mem > 0xdffffe00-0xdffffeff irq 18 at device 7.0 on pci0 > miibus1: <MII bus> on rl0 > rlphy0: <RealTek internal media interface> PHY 0 on miibus1 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > rl0: Ethernet address: 00:40:f4:b4:e9:3c > rl0: [ITHREAD] > uhci0: <VIA 83C572 USB controller> port 0xdc00-0xdc1f irq 21 at > device 16.0 on pci0 > uhci0: [ITHREAD] > usbus0: <VIA 83C572 USB controller> on uhci0 > uhci1: <VIA 83C572 USB controller> port 0xe000-0xe01f irq 21 at > device 16.1 on pci0 > uhci1: [ITHREAD] > usbus1: <VIA 83C572 USB controller> on uhci1 > uhci2: <VIA 83C572 USB controller> port 0xe400-0xe41f irq 21 at > device 16.2 on pci0 > uhci2: [ITHREAD] > usbus2: <VIA 83C572 USB controller> on uhci2 > ehci0: <VIA VT6202 USB 2.0 controller> mem 0xdffffd00-0xdffffdff irq > 21 at device 16.3 on pci0 > ehci0: [ITHREAD] > usbus3: EHCI version 1.0 > usbus3: <VIA VT6202 USB 2.0 controller> on ehci0 > isab0: <PCI-ISA bridge> at device 17.0 on pci0 > isa0: <ISA bus> on isab0 > atapci0: <VIA 8235 UDMA133 controller> port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 17.1 on > pci0 > ata0: <ATA channel 0> on atapci0 > ata0: [ITHREAD] > ata1: <ATA channel 1> on atapci0 > ata1: [ITHREAD] > pci0: <simple comms> at device 17.6 (no driver attached) > acpi_button1: <Sleep Button> on acpi0 > fdc0: <floppy drive controller> port 0x3f2-0x3f3,0x3f4-0x3f5,0x3f7 > irq 6 drq 2 on acpi0 > fdc0: [FILTER] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > uart0: [FILTER] > uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 > uart1: [FILTER] > ppc0: <Parallel port> port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on > acpi0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/9 bytes threshold > ppc0: [ITHREAD] > ppbus0: <Parallel port bus> on ppc0 > plip0: <PLIP network interface> on ppbus0 > plip0: [ITHREAD] > lpt0: <Printer> on ppbus0 > lpt0: [ITHREAD] > lpt0: Interrupt-driven port > ppi0: <Parallel I/O> on ppbus0 > atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0 > atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0 > atkbd0: <AT Keyboard> irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > atkbd0: [ITHREAD] > pmtimer0 on isa0 > orm0: <ISA Option ROM> at iomem 0xc0000-0xc9fff pnpid ORM0000 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 > acpi_throttle0: <ACPI CPU Throttling> on cpu0 > powernow0: <PowerNow! K7> on cpu0 > device_attach: powernow0 attach returned 6 > Timecounter "TSC" frequency 1800078810 Hz quality 800 > Timecounters tick every 1.000 msec > md0: Preloaded image </mfsroot> 33923072 bytes at 0xc0fd9834 > usbus0: 12Mbps Full Speed USB v1.0 > usbus1: 12Mbps Full Speed USB v1.0 > usbus2: 12Mbps Full Speed USB v1.0 > usbus3: 480Mbps High Speed USB v2.0 > ad0: 39205MB <Maxtor 6E040L0 NAR61590> at ata0-master UDMA133 > ugen0.1: <VIA> at usbus0 > uhub0: <VIA UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0 > ugen1.1: <VIA> at usbus1 > uhub1: <VIA UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1 > ugen2.1: <VIA> at usbus2 > uhub2: <VIA UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus2 > ugen3.1: <VIA> at usbus3 > uhub3: <VIA EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus3 > ad1: 38166MB <SAMSUNG SP0411N TW100-08> at ata0-slave UDMA100 > ad2: 39205MB <Maxtor 6E040L0 NAR61590> at ata1-master UDMA133 > uhub0: 2 ports with 2 removable, self powered > uhub1: 2 ports with 2 removable, self powered > uhub2: 2 ports with 2 removable, self powered > acd0: DVDROM <TSSTcorpDVD-ROM TS-H352A/TS03> at ata1-slave UDMA33 > uhub3: 6 ports with 6 removable, self powered > acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 > acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 > Trying to mount root from ufs:/dev/md0 > ZFS NOTICE: Prefetch is disabled by default on i386 -- to enable, > add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf. > ZFS WARNING: Recommended minimum kmem_size is 512MB; expect unstable > behavior. > Consider tuning vm.kmem_size and vm.kmem_size_max > in /boot/loader.conf. > ZFS filesystem version 5 > ZFS storage pool version 28 > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > log_sysevent: type 19 is not implemented > > And here is gpart output: > > mfsbsd# gpart show > => 34 80293181 ad0 GPT (38G) > 34 128 1 freebsd-boot (64K) > 162 2097152 2 freebsd-swap (1.0G) > 2097314 76068013 3 freebsd-zfs (36G) > 78165327 2127888 - free - (1.0G) > > => 34 78165293 ad1 GPT (37G) > 34 128 1 freebsd-boot (64K) > 162 2097152 2 freebsd-swap (1.0G) > 2097314 76068013 3 freebsd-zfs (36G) > > => 34 80293181 ad2 GPT (38G) > 34 128 1 freebsd-boot (64K) > 162 2097152 2 freebsd-swap (1.0G) > 2097314 76068013 3 freebsd-zfs (36G) > 78165327 2127888 - free - (1.0G) > > > Any idea what happened to the pool, why I am unable to boot and import > it, and what can I do to investigate or fix this issue? > Update: I tried with OpenSolaris 2009.06 <http://dlc.sun.com/osol/opensolaris/2009/06/osol-0906-x86.iso>; liveCD. Pool was visible, but import wasn't possible because ZFSv28 was too new for this realease. Then i tried with latest OpenIndiana, but unfortunately, it doesn't even see my pool. -- Bartosz Stec
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DE7D47A.5070105>