Re: gpt zfs raidz1 boot failure
On 2/8/2012 12:42 PM, George Kontostanos wrote: On Wed, Feb 8, 2012 at 6:03 PM, Chris Jones wrote: If you build a zfs in degraded mode, it's not bootable. But if you build it normally, then remove a disk to put it in degraded mode, it is bootable. I might be missing something here but it looks like you are trying to boot from a degraded raidz1 pool consisted from 1 drive? Correct. I've also replicated the problem using a degraded mirror consisting of 1 drive. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: gpt zfs raidz1 boot failure
This actually made for an interesting bug, once I dug into it some more: http://www.freebsd.org/cgi/query-pr.cgi?pr=164861 If you build a zfs in degraded mode, it's not bootable. But if you build it normally, then remove a disk to put it in degraded mode, it is bootable. Chris On 2/4/2012 9:56 PM, Chris Jones wrote: I have a raidz1 in degraded mode, with only 1 disk available. When I try to boot it, I get this: ZFS: can only boot from disk, mirror, raidz1, raidz2 and raidz3 vdevs ZFS: i/o error - all block copies unavailable ZFS: can't read MOS ZFS: unexpected object set type 0 ...followed by a couple of attempts to load maxroot/boot/kernel/kernel. I've carefully followed the instructions at http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/9.0-RELEASE -- except that I'm starting with a degraded zfs so I can transition my data from gmirror. Here's more system info: maxwell$ uname -a FreeBSD maxwell.cjones.org 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:15:25 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 maxwell# gpart show ada2 => 34 488281183 ada2 GPT (232G) 34128 1 freebsd-boot (64k) 162 488281055 2 freebsd-zfs (232G) maxwell# zpool status pool: maxroot state: DEGRADED status: One or more devices has been taken offline by the administrator. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Online the device using 'zpool online' or replace the device with 'zpool replace'. scan: none requested config: NAME STATE READ WRITE CKSUM maxroot DEGRADED 0 0 0 raidz1-0 DEGRADED 0 0 0 ada2p2 ONLINE 0 0 0 8747991784175675917 OFFLINE 0 0 0 was /usr/bigfile errors: No known data errors The errors seem to indicate that it's getting to the first- and second-stage bootstrap, but it's unable to load /boot/zfsloader; correct? The first line of error text seems to indicate that the bootstrap thinks my pool isn't a raidz1; but the output of zpool says otherwise. Any thoughts? Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
gpt zfs raidz1 boot failure
I have a raidz1 in degraded mode, with only 1 disk available. When I try to boot it, I get this: ZFS: can only boot from disk, mirror, raidz1, raidz2 and raidz3 vdevs ZFS: i/o error - all block copies unavailable ZFS: can't read MOS ZFS: unexpected object set type 0 ...followed by a couple of attempts to load maxroot/boot/kernel/kernel. I've carefully followed the instructions at http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/9.0-RELEASE -- except that I'm starting with a degraded zfs so I can transition my data from gmirror. Here's more system info: maxwell$ uname -a FreeBSD maxwell.cjones.org 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:15:25 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 maxwell# gpart show ada2 => 34 488281183 ada2 GPT (232G) 34128 1 freebsd-boot (64k) 162 488281055 2 freebsd-zfs (232G) maxwell# zpool status pool: maxroot state: DEGRADED status: One or more devices has been taken offline by the administrator. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Online the device using 'zpool online' or replace the device with 'zpool replace'. scan: none requested config: NAME STATE READ WRITE CKSUM maxroot DEGRADED 0 0 0 raidz1-0 DEGRADED 0 0 0 ada2p2 ONLINE 0 0 0 8747991784175675917 OFFLINE 0 0 0 was /usr/bigfile errors: No known data errors The errors seem to indicate that it's getting to the first- and second-stage bootstrap, but it's unable to load /boot/zfsloader; correct? The first line of error text seems to indicate that the bootstrap thinks my pool isn't a raidz1; but the output of zpool says otherwise. Any thoughts? Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
JMicron JMB363 lossage?
Now it appears that this machine fails under heavy I/O load. I was trying again to copy data across from one drive to the other, and I got a bunch of write errors. Unfortunately the kernel was in single-user mode, so I don't have a good record of the errors. Before I investigate more deeply, has anybody seen this before? Here are some (hopefully) relevant excerpts from dmesg: FreeBSD 7.0-RELEASE #0: Sun Nov 16 18:08:04 MST 2008 ch...@evilmax.cjones.org:/usr/src/sys/amd64/compile/EVILMAX ... ACPI APIC Table: ... acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) ... pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 ... pcib6: irq 35 at device 10.0 on pci0 pci6: on pcib6 atapci1: port 0xdce0-0xdce7,0xdcd8-0xdcdb,0xdce8-0xdcef,0xdcdc-0xdcdf,0xdcf0-0xdcff mem 0xefffe000-0xefff irq 35 at device 0.0 on pci6 atapci1: [ITHREAD] atapci1: AHCI called from vendor specific driver atapci1: AHCI Version 01.00 controller with 2 ports detected ata4: on atapci1 ata4: [ITHREAD] ata5: on atapci1 ata5: [ITHREAD] ata6: on atapci1 ata6: [ITHREAD] ... ad8: 238418MB at ata4-master SATA300 ad10: 238418MB at ata5-master SATA300 WARNING: Expected rawoffset 0, found 63 WARNING: Expected rawoffset 0, found 63 ... Trying to mount root from ufs:/dev/ad8s1a I was copying from ad8 to gvinum volumes on ad10, and I was alternately getting errors from ad8 or ad10, depending on whether I was using dump or tar to do the copying. It appears to only happen under heavy disk load, after 5-10 minutes. Chris Lowell Gilbert wrote: Chris Jones writes: I have an amd64 machine with two drives. I've got my system set up on ad8, and I'm building a RAID0 array using gvinum that will span ad8 and ad10. So for now, I have partitions on ad8 plus a set of volumes on ad10 that I want to move all my data to. Today I was doing a test move of all the data, using dump | restore like this: # dump -0aL -f - /var | ( cd /mnt/var && restore -rf - ) I got about a dozen messages like this: DUMP: read error from /dev/ad8s1d: Bad address: [block 10992192]: count=5120 What is causing this message, and is it a cause for alarm? Here's my bsdlabel for ad8s1: # /dev/ad8s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 104857604.2BSD 2048 16384 8 b: 4123872 1048576 swap c: 4882795470unused0 0 # "raw" part, don't edit d: 104857600 51724484.2BSD 2048 16384 28528 e: 2097152 1100300484.2BSD 2048 16384 28528 f: 376152347 1121272004.2BSD 2048 16384 28528 Thanks in advance for any help. It could be a serious problem, but is not necessarily such. Can you use smarttools to query the disk firmware for *its* opinion? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: DUMP: read error: Bad address
Lowell Gilbert wrote: Chris Jones writes: # dump -0aL -f - /var | ( cd /mnt/var && restore -rf - ) I got about a dozen messages like this: DUMP: read error from /dev/ad8s1d: Bad address: [block 10992192]: count=5120 It could be a serious problem, but is not necessarily such. Can you use smarttools to query the disk firmware for *its* opinion? SMART Error Log Version: 1 No Errors Logged ...so I assume the drive thinks it's doing just fine. Is this likely coming from a signal error, like a bad cable? Is it random driver lossage? Most importantly, is the ATA driver going to retry and correct this error, or does it mean I'm getting corrupted data on my disks? Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
DUMP: read error: Bad address
Hi folks-- I have an amd64 machine with two drives. I've got my system set up on ad8, and I'm building a RAID0 array using gvinum that will span ad8 and ad10. So for now, I have partitions on ad8 plus a set of volumes on ad10 that I want to move all my data to. Today I was doing a test move of all the data, using dump | restore like this: # dump -0aL -f - /var | ( cd /mnt/var && restore -rf - ) I got about a dozen messages like this: DUMP: read error from /dev/ad8s1d: Bad address: [block 10992192]: count=5120 What is causing this message, and is it a cause for alarm? Here's my bsdlabel for ad8s1: # /dev/ad8s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 104857604.2BSD 2048 16384 8 b: 4123872 1048576 swap c: 4882795470unused0 0 # "raw" part, don't edit d: 104857600 51724484.2BSD 2048 16384 28528 e: 2097152 1100300484.2BSD 2048 16384 28528 f: 376152347 1121272004.2BSD 2048 16384 28528 Thanks in advance for any help. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Dropped USB keyboard events
Hi folks-- I recently installed my first FreeBSD workstation after many years with NetBSD exclusively. Overall, I'm happy; but I'm seeing one particularly irritating bug. At seemingly random intervals, the computer seems to stop listening for keyboard events for as long as a second at a time. Though I'm no speed demon at the keyboard, this can mean a few keystrokes that go missing before the computer catches up with me. Sometimes when it catches up, it will get a key which I pressed during the hiatus; and sometimes it will duplicate the last key I pressed before it stopped paying attention. I've tried swapping to a different USB keyboard. I've tried plugging the keyboard in directly to the USB port, instead of via hubs. I've tried console mode instead of X. In all cases, the strange behavior is still present. I'm using FreeBSD 6.2-RELEASE on a Dell Latitude D620 laptop. Here are the many lines of USB-relevant output from dmesg: uhci0: port 0xbf80-0xbf9f irq 20 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xbf60-0xbf7f irq 21 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xbf40-0xbf5f irq 22 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xbf20-0xbf3f irq 23 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xffa8-0xffa803ff irq 20 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered uhub5: vendor 0x413c product 0x0058, class 9/0, rev 2.00/0.00, addr 2 uhub5: multiple transaction translators uhub5: 4 ports with 4 removable, self powered uhub6: vendor 0x0424 product 0x2504, class 9/0, rev 2.00/0.01, addr 3 uhub6: multiple transaction translators uhub6: 4 ports with 4 removable, self powered uhub7: vendor 0x0424 product 0x2504, class 9/0, rev 2.00/0.01, addr 4 uhub7: multiple transaction translators uhub7: 4 ports with 4 removable, self powered ums0: Microsoft Microsoft 3-Button Mouse with IntelliEye(TM), rev 1.10/3.00, add r 5, iclass 3/1 ums0: 3 buttons and Z dir. uhub8: Dell Dell USB Keyboard Hub, class 9/0, rev 1.10/2.00, addr 6 uhub8: 3 ports with 2 removable, bus powered ukbd0: Dell Dell USB Keyboard, rev 1.10/2.00, addr 7, iclass 3/1 kbd2 at ukbd0 uhid0: Dell Dell USB Keyboard, rev 1.10/2.00, addr 7, iclass 3/1 ... uhub9: vendor 0x413c product 0xa005, class 9/0, rev 2.00/50.18, addr 2 uhub9: 4 ports with 0 removable, self powered uhub10: vendor 0x0b97 product 0x7761, class 9/0, rev 1.10/1.10, addr 3 uhub10: 3 ports with 2 removable, bus powered ugen0: O2 O2Micro CCID SC Reader, rev 1.10/1.10, addr 4 I'd appreciate any advice on getting my lost keystrokes back. Chris -- Chris Jones [EMAIL PROTECTED]www.cjones.org PGP ID 5AFDD40A ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mpd PPTP to Cisco 3000 VPN Concentrator routing problem
Original message from Joe Marcus Clarke: > I was able to get past the routing loop by readdressing the interface as > soon as it came up. This is a good starter howto on that procedure: > > http://www.cs.rpi.edu/~flemej/fbsd-cisco-vpn/fbsd-cisco-vpn.pdf Yeah I went through this, but my iface up-script doesn't seem to work, which was my original question. I didn't make it far enough to find out mppe is broken as well. > You might also consider trying out security/vpnc if the concentrator > also allows for IPSec clients using the Cisco VPN client. I'll check it out, thanks. I didn't have any luck with isakmpd because it apparently doesn't support xauth and some other things I need. -- Chris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mpd PPTP to Cisco 3000 VPN Concentrator routing problem
Oh. :( I thought it negotiated the encryption ok because I see this: [ciscovpn] CCP: LayerUp Compress using: MPPE, 128 bit, stateless Decompress using: MPPE, 128 bit, stateless And capturing on the interface, I see echo req's coming in from the concentrator, but I encounter a routing loop when I try to send across the tunnel. Disabling encryption isn't an option, even for testing, I'm afraid. Original message from Joe Marcus Clarke: > On Thu, 2004-01-08 at 02:49, Chris Jones wrote: > > Hi. I've gone over list archives and seen this issue discussed before, > > but the sugggested solutions aren't working for me. I am using > > mpd-3.15_1 on FreeBSD 4.9-STABLE to connect to a Cisco 3000 Series VPN > > Concentrator. I have negotiated CHAP and MPPE and the ng0 interface > > comes up, but when I try to do anything I get this: > > > > $ ping 10.10.58.7 > > PING 10.10.58.7 (10.10.58.7): 56 data bytes > > ping: sendto: Resource deadlock avoided > > ping: sendto: No buffer space available > > > > A little investigation showed that this is a known routing issue and > > that it is possible to work around by re-addressing the ng0 interface > > with the VPN concentrator's private IP and set a default route to it. I > > did this, but I still have the same problem. :( > > > > Does anyone see what I am doing wrong here? Below are my routing table > > and ifconfig before running mpd, after running mpd, and after running > > the "fix". Below that is my mpd.conf and its output (verbose). > > > > I appreciate any help on this, I've been going crazy trying to figure > > out what I'm doing wrong. I can get it to work using the OSX PPTP > > client, but not mpd. > > Good luck. I have tried to get this working, but have never been able > to get mpd encryption to work with the Concentrator's encryption > (neither has anyone else to my knowledge). If you disable encryption on > the concentrator, the tunnel will come up, and you will be able to pass > traffic across it. Any other combination does not work. I haven't > tried 3.16 yet, but looking at the ChangeLog, I doubt it addresses this > problem. > > Joe > > -- > PGP Key : http://www.marcuscom.com/pgp.asc -- Chris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mpd PPTP to Cisco 3000 VPN Concentrator routing problem
Hi. I've gone over list archives and seen this issue discussed before, but the sugggested solutions aren't working for me. I am using mpd-3.15_1 on FreeBSD 4.9-STABLE to connect to a Cisco 3000 Series VPN Concentrator. I have negotiated CHAP and MPPE and the ng0 interface comes up, but when I try to do anything I get this: $ ping 10.10.58.7 PING 10.10.58.7 (10.10.58.7): 56 data bytes ping: sendto: Resource deadlock avoided ping: sendto: No buffer space available A little investigation showed that this is a known routing issue and that it is possible to work around by re-addressing the ng0 interface with the VPN concentrator's private IP and set a default route to it. I did this, but I still have the same problem. :( Does anyone see what I am doing wrong here? Below are my routing table and ifconfig before running mpd, after running mpd, and after running the "fix". Below that is my mpd.conf and its output (verbose). I appreciate any help on this, I've been going crazy trying to figure out what I'm doing wrong. I can get it to work using the OSX PPTP client, but not mpd. - Chris VPN External IP: C.O.R.P VPN Interal IP: 10.10.58.7 *** before running mpd DestinationGatewayFlagsRefs Use Netif Expire default192.168.131.254UGS 00de0 127.0.0.1 127.0.0.1 UH 00lo0 192.168.131link#1 UC 00de0 192.168.131.25400:00:0f:00:00:00 UHLW10de0 36 *** after running mpd ng0: flags=88d1 mtu 1494 inet 10.10.58.156 --> C.O.R.P netmask 0x inet6 fe80::203::fe73:504c%ng0 prefixlen 64 scopeid 0x3 DestinationGatewayFlagsRefs Use Netif Expire default192.168.131.254UGS 0 30de0 10.10.58.156 lo0UHS 00lo0 127.0.0.1 127.0.0.1 UH 00lo0 192.168.131link#1 UC 00de0 192.168.131.25400:00:0f:00:00:00 UHLW10de0 4 C.O.R.P10.10.58.156 UH 00ng0 *** run fix from iface up-script ifconfig ng0 inet 10.10.58.156 10.10.58.7 netmask 0x route delete default route add default -interface ng0 *** after running fix ng0: flags=88d1 mtu 1494 inet6 fe80::203::fe73:504c%ng0 prefixlen 64 scopeid 0x3 inet 10.10.58.156 --> 10.10.58.7 netmask 0x DestinationGatewayFlagsRefs Use Netif Expire defaultng0US 00ng0 10.10.58.7 10.10.58.156 UH 00ng0 10.10.58.156 lo0UHS 00lo0 127.0.0.1 127.0.0.1 UH 00lo0 192.168.131link#1 UC 00de0 192.168.131.25400:00:0f:00:00:00 UHLW00de0 ciscovpn: new -i ng0 ciscovpn work set bundle authname "user" set bundle password "password" set ipcp ranges 10.10.58.0/23 C.O.R.P/32 set link max-redial -1 set link keep-alive 0 0 set link disable acfcomp protocomp set bundle no crypt-reqd set bundle enable compression encryption set ccp yes mppc set ccp yes mpp-e128 set ccp no mpp-e40 set ccp yes mpp-stateless set link disable pap chap set link no chap-md5 set link no chap-msv2 set link no pap set link accept chap-msv1 set iface idle 0 set ipcp disable vjcomp set ipcp enable req-pri-dns req-sec-dns set iface up-script /usr/local/etc/mpd/ciscovpn-iface-up.sh open *** mpd.links work: set link type pptp set pptp peer C.O.R.P set pptp enable originate outcall *** mpd output # mpd Multi-link PPP for FreeBSD, by Archie L. Cobbs. Based on iij-ppp, by Toshiharu OHNO. mpd: pid 1033, version 3.15 ([EMAIL PROTECTED] 00:39 7-Jan-2004) [ciscovpn] ppp node is "mpd1033-ciscovpn" [ciscovpn] using interface ng0 [ciscovpn] IFACE: Open event [ciscovpn] IPCP: Open event [ciscovpn] IPCP: state change Initial --> Starting [ciscovpn] IPCP: LayerStart [ciscovpn:work] [ciscovpn] bundle: OPEN event in state CLOSED [ciscovpn] opening link "work"... [work] link: OPEN event [work] LCP: Open event [work] LCP: state change Initial --> Starting [work] LCP: LayerStart [work] device: OPEN event in state DOWN pptp0: connecting to C.O.R.P:1723 [work] device is now in state OPENING pptp0: connected to C.O.R.P:1723 pptp0: attached to connection with C.O.R.P:1723 pptp0-0: outgoing call connected at 1000 bps [work] PPTP call successful [work] device: UP event in state OPENING [work] device is now in state UP [work] link: UP event [work] link: origination is local [work] LCP: Up eve
