Re: Reading a damaged disk
I'm not sure if it's available for OpenBSD, but there's dd_rescue as well, which I gather substitutes blocks of zeros for any unreadable sectors. That would allow you to create an image file with some holes filled in with zeros. You then would be able to avoid I/O errors by working against that image file instead of the disk itself. Good luck! On Mon, Sep 24, 2012 at 3:33 PM, Brian Seklecki (Mobile) laval...@spiritual-machines.org wrote: CloneZilla has a provision for backing-off invalid/unreadble sectors using a configurable set of thresholds. ~BAS (Hates to recommend GNU/Linux based systems, but G4U didn't cut it with my last failed drive) -- *This email is intended only for its recipients. If you are reading this, and are not a recipient of this email, won't you please explain to me how this happened? Luck must be on your side, or perhaps you're just a shoulder-surfer extraordinaire. Please think about the environment, then print this email. *
Re: mount nullfs
Does this mean that the performance of a local NFS mount is actually better than that of mount_nullfs? On Sat, Apr 16, 2011 at 9:50 AM, Tomas Bodzar tomas.bod...@gmail.comwrote: The question is if implementations still sucks as before years http://undeadly.org/cgi?action=articlesid=20050527155028 On Sat, Apr 16, 2011 at 3:59 PM, Dan Brosemer o...@svartalfheim.net wrote: On Sat, Apr 16, 2011 at 01:08:52AM +0200, Paul de Weerd wrote: On Sat, Apr 16, 2011 at 01:59:12AM +0300, Claudiu Pruna wrote: | B B Hi list, | | B B I was wondering, in OpenBSD is there an equivalent to FreeBSD's | mount_nullfs or to Linux's mount -o bind ? Sure; it's in the attic .. don't wake the spiders! http://www.openbsd.org/cgi-bin/cvsweb/src/sys/miscfs/nullfs/Attic/ I use a local NFS mount when I want to accomplish this. B It drags in a lot of complexity, but it has worked for me for years. -Dan -- Young man, in mathematics you don't understand things, you just get used to them. - John von Neumann
Re: Sed error message on latest ramdisk_CD #164
What about: df -i ? There may be no more inodes available, even though there is still some space left on device, and the same No space left on device message is generally produced in such cases. On Tue, Oct 19, 2010 at 11:32 AM, Kevin Chadwick ma1l1i...@yahoo.co.uk wrote: At the last part of the install, just after timezone entry using install48.iso. (Ramdisk_CD) #164 Oct 18 17:42:33 An error message is given saying. Uid0 on /: file system full /: write failed , file system is full sed: stdout: No space left on device /bin/df gives blocks usedavail /dev/rd0a 3487344047 99% Install seems fine and even the mail to root is there. -- Young man, in mathematics you don't understand things, you just get used to them. - John von Neumann
Re: computer hangs after varying amount of data is received from network via ssh
On Wed, Oct 13, 2010 at 8:59 PM, Nick Holland n...@holland-consulting.net wrote: On 10/13/10 17:25, Robert wrote: On Wed, 13 Oct 2010 16:55:18 -0400 Ted Unangst ted.unan...@gmail.com wrote: can be done about it, and 10 year old quirky PC hardware doesn't attract a of interest... As long as it's on [1] I hope it does? I guess I'm not the only one who uses a Pentium 4 (or older stuff) for firewalls and other systems, since they are very cheap to buy and replace, and are more than sufficient (speed) for a lot of tasks. regards, Robert [1] http://www.openbsd.org/i386.html There are big differences between well-designed hardware, poorly designed and implemented hardware, hardware is working properly and hardware that is malfunctioning. A lot of hardware out there was tested with Windows-of-the-Day (and maybe the day before) and that's it. Anything else it works with, great, but it was by luck, not design. A lot of early AMD stuff was junk. I'm not talking about the AMD chips themselves, I'm talking about the REST of the computer. I've got a few AMD K6 systems, and NONE of them can build from source at the rated speed with OpenBSD. They'll run the OS just fine, but they can't build, giving sig11's at random places during the process. Replace the RAM with stuff that has worked well in 133MHz bus machines, same thing. Slow down the bus speed, increase the multiplier, and suddenly they work fine. I don't think that's an OpenBSD problem, and I really don't want developers fighting with that. I have heard reports of these kinds of problems extending well into the Athlon days... In your case, though, yes, I'd look closely at your hardware. Not sure why you have both a 150G disk and a 15G disk...double your chances of disk failure taking your system out...for 10% more storage. I also see re2 is on irq12. That's the PS/2 mouse IRQ. Sure, you don't have a mouse on your machine, maybe you have the mouse port off in the BIOS...but I'd be completely unsurprised if your HW mfg screwed the pooch and didn't really disconnect the PS/2 hardware from IRQ controller, and that could be causing some of your issues there (twist knobs in the system BIOS, you can probably fix this). And I'd not be surprised in the least if BOTH were problems for you... Nick. Actually the same issue occurred previously when the only difference was that I had configured re0 as the active interface. I thought the fact that it was using the same irq as pciide1 might be the source of the issue. Most recently, I have tried extracting the NIC in question. The only remaining NIC is now using irq 10 (along with pciide1.) Similar issues occurred. I list here the output - similar sequences have been listed many times, all values aside from c_bcount, c_skip, and possibly cn vary. pciide1:1:0: bus-master DMA error: missing interrupt, status=0x21 wd1a: device timeout writing fsbn 581104768 of 5811047680581104799 (wd1 bn 581184768; cn 576492 tn 13 sn 13), retrying wd1(pciide1:1:0): timeout type: ata c_bcount: 16384 c_skip: 0 I am going to see if I can eliminate the old PATA drive and associated controller / driver from the picture with hardware I have available. -- Young man, in mathematics you don't understand things, you just get used to them. - John von Neumann
computer hangs after varying amount of data is received from network via ssh
I am attempting to copy data from a USB mass storage device formatted with ext2 to an ffs filesystem on a SATA drive. The OpenBSD system containing the target filesystem lacks a USB 2.0 interface, so I am attempting to copy files over the network from a USB 2.0 equipped system running the PartedMagic linux liveCD. Here is the command I am using from the liveCD environment in order to attempt the copy operation: r...@partedmagic:/# tar -c mybook1.5 | ssh 192.168.66.77 'tar -vxf - -C /belongtome/mybook1.5' After hundreds of megabytes are successfully transferred, the following message occurs on the OpenBSD system, effectively halting it: re2: watchdog timeout wd0(pciide0:0:0): timeout type: ata c_bcount: 16384 c_skip: 0 Below is the dmesg output from the OpenBSD system: OpenBSD 4.7 (GENERIC) #558: Wed Mar 17 20:46:15 MDT 2010 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: AMD Duron(tm) Processor (AuthenticAMD 686-class, 64KB L2 cache) 808 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real mem = 804794368 (767MB) avail mem = 771067904 (735MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 03/08/01, BIOS32 rev. 0 @ 0xf0ee0, SMBIOS rev. 2.3 @ 0xf2db0 (46 entries) bios0: vendor Award Software, Inc. version ASUS A7V-E ACPI BIOS Revision 1002D date 03/08/2001 bios0: ASUSTeK Computer INC. A7V-E apm0 at bios0: Power Management spec V1.2 (BIOS management disabled) apm0: APM power management enable: unrecognized device ID (9) apm0: APM engage (device 1): power management disabled (1) apm0: AC on, battery charge unknown acpi at bios0 function 0x0 not configured pcibios0 at bios0: rev 2.1 @ 0xf/0x1742 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf1690/176 (9 entries) pcibios0: PCI Interrupt Router at 000:07:0 (VIA VT82C586 ISA rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0x8000 0xc8000/0x4800 cpu0 at mainbus0: (uniprocessor) pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 VIA VT8363 Host rev 0x03 viaagp0 at pchb0: v2 agp0 at viaagp0: aperture at 0xfc00, size 0x1000 ppb0 at pci0 dev 1 function 0 VIA VT8363 AGP rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 3DFX Interactive Voodoo3 rev 0x01 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) pcib0 at pci0 dev 7 function 0 VIA VT82C686 ISA rev 0x40 pciide0 at pci0 dev 7 function 1 VIA VT82C571 IDE rev 0x06: ATA100, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: ST315322A wd0: 16-sector PIO, LBA, 14592MB, 29886400 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 4 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: IDE-CD, R/RW 4x4x24, Z024 ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, DMA mode 2 viaenv0 at pci0 dev 7 function 4 VIA VT82C686 SMBus rev 0x40: 24-bit timer at 3579545Hz pciide1 at pci0 dev 11 function 0 CMD Technology SiI3512 SATA rev 0x01: DMA pciide1: using irq 10 for native-PCI interrupt pciide1: port 1: device present, speed: 1.5Gb/s wd1 at pciide1 channel 1 drive 0: ST31500341AS wd1: 16-sector PIO, LBA48, 1430799MB, 2930277168 sectors wd1(pciide1:1:0): using BIOS timings, Ultra-DMA mode 6 re0 at pci0 dev 12 function 0 Realtek 8169 rev 0x10: RTL8169/8110SB (0x1000), irq 10, address 00:14:d1:1d:3b:e8 rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 3 re1 at pci0 dev 13 function 0 Realtek 8169 rev 0x10: RTL8169/8110SB (0x1000), irq 11, address 00:14:d1:1d:3b:f4 rgephy1 at re1 phy 7: RTL8169S/8110S PHY, rev. 3 re2 at pci0 dev 14 function 0 Realtek 8169 rev 0x10: RTL8169/8110SB (0x1000), irq 12, address 00:14:d1:1d:39:8a rgephy2 at re2 phy 7: RTL8169S/8110S PHY, rev. 3 isa0 at pcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 biomask e765 netmask ff65 ttymask mtrr: Pentium Pro MTRR support vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root root on wd0a swap on wd0b dump on wd0b WARNING: / was not properly unmounted -- Young man, in mathematics you don't understand things, you just get used to them. - John von Neumann
Re: computer hangs after varying amount of data is received from network via ssh
I will run fsck against my root when I get a chance. I'll also look into installing 4.8. Thanks 2010/10/13 Guillaume Duali g.du...@otasc.org: Hi, You can try a 'fsck' to check your / And you can test to put 4.8 on your laptop to see if the problem persist. Regards, Guillaume Le 13 oct. 2010 ` 19:24, Robert Halberg robert.halb...@gmail.com a icrit : I am attempting to copy data from a USB mass storage device formatted with ext2 to an ffs filesystem on a SATA drive. The OpenBSD system containing the target filesystem lacks a USB 2.0 interface, so I am attempting to copy files over the network from a USB 2.0 equipped system running the PartedMagic linux liveCD. Here is the command I am using from the liveCD environment in order to attempt the copy operation: r...@partedmagic:/# tar -c mybook1.5 | ssh 192.168.66.77 'tar -vxf - -C /belongtome/mybook1.5' After hundreds of megabytes are successfully transferred, the following message occurs on the OpenBSD system, effectively halting it: re2: watchdog timeout wd0(pciide0:0:0): timeout type: ata c_bcount: 16384 c_skip: 0 Below is the dmesg output from the OpenBSD system: OpenBSD 4.7 (GENERIC) #558: Wed Mar 17 20:46:15 MDT 2010 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: AMD Duron(tm) Processor (AuthenticAMD 686-class, 64KB L2 cache) 808 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real mem = 804794368 (767MB) avail mem = 771067904 (735MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 03/08/01, BIOS32 rev. 0 @ 0xf0ee0, SMBIOS rev. 2.3 @ 0xf2db0 (46 entries) bios0: vendor Award Software, Inc. version ASUS A7V-E ACPI BIOS Revision 1002D date 03/08/2001 bios0: ASUSTeK Computer INC. A7V-E apm0 at bios0: Power Management spec V1.2 (BIOS management disabled) apm0: APM power management enable: unrecognized device ID (9) apm0: APM engage (device 1): power management disabled (1) apm0: AC on, battery charge unknown acpi at bios0 function 0x0 not configured pcibios0 at bios0: rev 2.1 @ 0xf/0x1742 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf1690/176 (9 entries) pcibios0: PCI Interrupt Router at 000:07:0 (VIA VT82C586 ISA rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0x8000 0xc8000/0x4800 cpu0 at mainbus0: (uniprocessor) pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 VIA VT8363 Host rev 0x03 viaagp0 at pchb0: v2 agp0 at viaagp0: aperture at 0xfc00, size 0x1000 ppb0 at pci0 dev 1 function 0 VIA VT8363 AGP rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 3DFX Interactive Voodoo3 rev 0x01 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) pcib0 at pci0 dev 7 function 0 VIA VT82C686 ISA rev 0x40 pciide0 at pci0 dev 7 function 1 VIA VT82C571 IDE rev 0x06: ATA100, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: ST315322A wd0: 16-sector PIO, LBA, 14592MB, 29886400 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 4 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: IDE-CD, R/RW 4x4x24, Z024 ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, DMA mode 2 viaenv0 at pci0 dev 7 function 4 VIA VT82C686 SMBus rev 0x40: 24-bit timer at 3579545Hz pciide1 at pci0 dev 11 function 0 CMD Technology SiI3512 SATA rev 0x01: DMA pciide1: using irq 10 for native-PCI interrupt pciide1: port 1: device present, speed: 1.5Gb/s wd1 at pciide1 channel 1 drive 0: ST31500341AS wd1: 16-sector PIO, LBA48, 1430799MB, 2930277168 sectors wd1(pciide1:1:0): using BIOS timings, Ultra-DMA mode 6 re0 at pci0 dev 12 function 0 Realtek 8169 rev 0x10: RTL8169/8110SB (0x1000), irq 10, address 00:14:d1:1d:3b:e8 rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 3 re1 at pci0 dev 13 function 0 Realtek 8169 rev 0x10: RTL8169/8110SB (0x1000), irq 11, address 00:14:d1:1d:3b:f4 rgephy1 at re1 phy 7: RTL8169S/8110S PHY, rev. 3 re2 at pci0 dev 14 function 0 Realtek 8169 rev 0x10: RTL8169/8110SB (0x1000), irq 12, address 00:14:d1:1d:39:8a rgephy2 at re2 phy 7: RTL8169S/8110S PHY, rev. 3 isa0 at pcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 biomask e765 netmask ff65 ttymask mtrr: Pentium Pro MTRR support vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root root on wd0a swap on wd0b dump on wd0b WARNING
