Some problems with USB stick
-
The inode error will happen with bad media, not just when the filesystem is out of inodes. Change to a new CF card and the error would likely go away. If both cards are the same brand, try a different brand or type.
Also, you should be running NanoBSD/embedded on there and not a full install, or you will wear out the CF, it's just a matter of time.
-
kingston and transend have the same bag :(
I can't install the embedded version of Pfsense on CF, write error on N byte on both cards
Advise me brends which 100% works fine.
thx
-
I use Sandisk, Transcend, Kingston, all without problems.
It could also be an issue with your CF adapter (usb card reader, cf-to-ide adapter, etc) causing write errors.
The fact that you can't write a nanobsd image to the card tells me that it's definitely something with the CF or what it's being attached to.
-
CF i mean USB stick
I try almost all available USB ports (burn embedded PF)
Maybe i bought none legal devise -
the same bag on both sticks :(
in addition first one is new …
-
The Kingston DTmini10 is a USB flash drive. Spec sheet, pdf.
It should work though. ???Steve
-
it's a miracle after i clear my kingston (scan with HDD regenerator ) i can burn the embedded PF(in progress and no bags yet ):)
Fantastic :)Thx so mush :)
is it difference between 2GB and 4 GB embedded images ?
-
CF, USB, shouldn't really matter. Only major difference is the PC interface. Same notes about wear-down would apply, and there have been cases of "ghost shift" shoddy media that appear to be branded but are falsified.
Check this guy's report on SD media:
http://www.bunniestudios.com/blog/?p=918It could be a BIOS bug, but that is doubtful if you have trouble writing it on two devices (the PC you're imaging it from, and also the firewall device).
-
Running a scan on that may have caused some defective sectors to be remapped or removed from service on the media, but it probably isn't a long-term solution. It may work for a while though.
-
на встроенной версии pfsense оно может снова поломаться ?
on an embedded version of pfsense it can go wrong again?
-
Eventually, yes, but it would take longer to show up since there are less writes to the embedded version.
-
current hdd is a piece of %% :)
Nov 2 20:11:23 last message repeated 5 times
Nov 2 20:03:08 kernel: ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2657743
Nov 2 20:00:02 kernel: ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2657743
Nov 2 20:00:02 kernel: ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2657743
Nov 2 20:00:01 check_reload_status: check_reload_status is starting
Nov 2 19:59:00 last message repeated 5 times
Nov 2 19:50:44 last message repeated 5 times
Nov 2 19:41:26 kernel: ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2657743
Nov 2 19:38:20 kernel: ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2657743
Nov 2 19:38:20 kernel: ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2657743
Nov 2 19:37:49 kernel: g_vfs_done():ad0s1a[WRITE(offset=1360723968, length=16384)]error = 5
Nov 2 19:37:49 kernel: ad0: FAILURE - WRITE_DMA status=51 <ready,dsc,error>error=84 <icrc,aborted>LBA=2657743
Nov 2 19:37:49 kernel: ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2657743
Nov 2 19:37:49 kernel: ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2657743
Nov 2 19:37:18 kernel: g_vfs_done():ad0s1a[WRITE(offset=1360723968, length=16384)]error = 5
Nov 2 19:37:18 kernel: ad0: FAILURE - WRITE_DMA status=51 <ready,dsc,error>error=84 <icrc,aborted>LBA=2657743
Nov 2 19:37:18 last message repeated 3 times
Nov 2 19:35:14 kernel: ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2657743
Nov 2 19:35:14 kernel: ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2657743
Nov 2 19:33:41 kernel: g_vfs_done():ad0s1a[WRITE(offset=1360723968, length=16384)]error = 5
Nov 2 19:33:41 kernel: ad0: FAILURE - WRITE_DMA status=51 <ready,dsc,error>error=84 <icrc,aborted>LBA=2657743
Nov 2 19:33:41 kernel: ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2657743
Nov 2 19:33:41 kernel: ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2657743
Nov 2 19:33:10 kernel: g_vfs_done():ad0s1a[WRITE(offset=1360723968, length=16384)]error = 5
Nov 2 19:33:10 kernel: ad0: FAILURE - WRITE_DMA status=51 <ready,dsc,error>error=84 <icrc,aborted>LBA=2657743
Nov 2 19:33:10 last message repeated 3 times
Nov 2 19:32:08 last message repeated 2 times
Nov 2 19:30:04 kernel: ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2657743
Nov 2 19:26:27 kernel: ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2657743
Nov 2 19:26:27 kernel: vnode_pager_putpages: residual I/O 4096 at 5
Nov 2 19:25:26 last message repeated 2 times
Nov 2 19:24:24 kernel: ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2657743
Nov 2 19:22:20 kernel: ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2657743
Nov 2 19:21:18 kernel: vnode_pager_putpages: residual I/O 4096 at 5
Nov 2 19:20:16 last message repeated 2 times
Nov 2 19:19:14 kernel: ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2657743
Nov 2 19:19:14 kernel: ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2657743
Nov 2 19:19:13 kernel: ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=10161807
Nov 2 19:16:08 kernel: vnode_pager_putpages: residual I/O 4096 at 5
Nov 2 19:14:04 kernel: ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=2657743
g_vfs_done():ad0s1a[WRITE(offset=1360723968, length=32768)]error = 5</icrc,aborted></ready,dsc,error></icrc,aborted></ready,dsc,error></icrc,aborted></ready,dsc,error></icrc,aborted></ready,dsc,error> -
May not be a POS, could be the controller/BIOS. Disable DMA (check the doc wiki for how) and try again.
-
I try to change IDE cable , maybe it helps
-
I had forgotten my own experience with CF.
You MUST disable udma in the bios if you are using compact flash and BSD. PIO mode only. Something about compact flash not fully meeting the IDE spec, though it works fine under linux.
I'm not sure about USB but i'd try this first.Steve
-
I repair my hard ( victoria , hdd regenerator,Low level Format) and change Ide cable
funny function
THX for conversation!Nov 4 10:45:38 sshd[6791]: Accepted keyboard-interactive/pam for admin from 192.168.0.2 port 41079 ssh2
Nov 3 21:28:34 last message repeated 14 times
Nov 3 21:28:21 last message repeated 31 times
Nov 3 21:27:50 kernel: arp: 192.168.0.2 is on rl1 but got reply from 00:20:ed:69:37:f1 on vr0
Nov 3 21:27:50 php: : Processing -
Nov 3 21:27:50 php: : Processing start -
Nov 3 21:27:50 php: : Processing vr0 - start
Nov 3 21:27:50 check_reload_status: rc.linkup starting
Nov 3 21:27:49 kernel: arp: 192.168.0.2 is on rl1 but got reply from 00:20:ed:69:37:f1 on vr0
Nov 3 21:27:49 kernel: vr0: link state changed to UP
Nov 3 21:27:31 last message repeated 6 times
Nov 3 21:27:17 kernel: arp: 192.168.1.1 is on vr0 but got reply from 00:30:4f:69:73:3b on rl1
Nov 3 21:25:54 php: : Processing -
Nov 3 21:25:54 php: : Processing start -
Nov 3 21:25:54 php: : Processing rl0 - start
Nov 3 21:25:54 kernel: rl0: link state changed to UP
Nov 3 21:25:54 check_reload_status: rc.linkup starting
Nov 3 21:25:52 kernel: rl0: link state changed to DOWN
Nov 3 21:25:51 kernel: rl0: link state changed to UP
Nov 3 21:25:36 login: login on ttyv0 as root
Nov 3 21:25:34 check_reload_status: check_reload_status is starting
Nov 3 21:25:34 php: : Resyncing configuration for all packages.
Nov 3 21:25:33 dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Nov 3 21:25:33 dhcpd: All rights reserved.
Nov 3 21:25:33 dhcpd: Copyright 2004-2008 Internet Systems Consortium.
Nov 3 21:25:33 dhcpd: Internet Systems Consortium DHCP Server V3.0.7
Nov 3 21:25:33 php: : Creating rrd update script
Nov 3 21:25:29 dnsmasq[578]: read /etc/hosts - 2 addresses
Nov 3 21:25:29 dnsmasq[578]: using nameserver 192.168.1.1#53
Nov 3 21:25:29 dnsmasq[578]: reading /etc/resolv.conf
Nov 3 21:25:29 dnsmasq[578]: compile time options: IPv6 GNU-getopt BSD-bridge ISC-leasefile no-DBus no-I18N TFTP
Nov 3 21:25:29 dnsmasq[578]: started, version 2.45 cachesize 150
Nov 3 21:25:29 dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Nov 3 21:25:29 dhcpd: All rights reserved.
Nov 3 21:25:29 dhcpd: Copyright 2004-2008 Internet Systems Consortium.
Nov 3 21:25:29 dhcpd: Internet Systems Consortium DHCP Server V3.0.7
Nov 3 21:25:28 kernel: rl1: link state changed to UP
Nov 3 21:25:27 kernel: pflog0: promiscuous mode enabled
Nov 3 21:25:26 kernel: Trying to mount root from ufs:/dev/ad2s1a
Nov 3 21:25:26 kernel: ad2: 9541MB <wdc wd100eb-00csf0="" 04.01b04="">at ata1-master UDMA100
Nov 3 21:25:26 kernel: IPsec: Initialized Security Association Processing.
Nov 3 21:25:26 kernel: Timecounters tick every 1.000 msec
Nov 3 21:25:26 kernel: Timecounter "TSC" frequency 1462510354 Hz quality 800
Nov 3 21:25:26 kernel: uhub1: device problem (STALLED), disabling port 1
Nov 3 21:25:26 kernel: unknown: <pnp0c01>can't assign resources (memory)
Nov 3 21:25:26 kernel: speaker0: <pc speaker="">at port 0x61 pnpid PNP0800 on isa0
Nov 3 21:25:26 kernel: unknown: <pnp0303>can't assign resources (port)
Nov 3 21:25:26 kernel: vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Nov 3 21:25:26 kernel: sio1: port may not be enabled
Nov 3 21:25:26 kernel: sio1: configured irq 3 not in bitmap of probed irqs 0</generic></pnp0303></pc></pnp0c01></wdc>
