Re: mpt problem on a Supermicro motherboard (FreeBSD 9.2 amd64)
Victor Sudakov wrote: I have several Supermicro-based servers with the mpt RAID adapter: # mptutil show adapter mpt0 Adapter: Board Name: UNUSED Board Assembly: Chip Name: C1068E Chip Revision: UNUSED RAID Levels: none # The problem is, I cannot configure any RAIDs (please see output below) from FreeBSD. If I configure volumes from BIOS setup, FreeBSD still sees them as separate physical discs. What am I doing wrong? I cannot use gmirror with these servers because a) if no MPT RAID is configured in BIOS setup, it cannot boot from HDD and b) if an MPT RAID *is* configured in BIOS setup, it occupies the last sector and prevents GEOM from working with these drives. Any help please? (or redirect me to a more appropriate maillist). After many unsuccessful trials and googling, we had to reconfigure the adapter from RAID mode to IT mode. It required flashing the adapter's BIOS from a Supermicro-supplied image and changing a jumper setting on the motherboard. Now as the adapter is in IT mode, it is a plain HBA the BIOS can boot from, and I have set up a gmirror on the SAS disks. After flashing the adapter BIOS, don't forget to enter its setup (Ctrl-C) and enable hotplugging of disks (called Removable Media Support in the menu, off by default). People come across similar problems and solutions on other OSes, like http://ubuntuforums.org/archive/index.php/t-973912.html -- Victor Sudakov Tomsk, Russia Russian Barefoot FAQ at http://www.barefooters.ru/barefoot.txt ___ 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: pkgng problem
must be code unrot On 19 August 2013 16:13, Michael W. Lucas mwlu...@michaelwlucas.com wrote: For the archives: I left the problem alone for a few days, with no changes on my side. Came back Monday. Tried again. Everything worked on the affected machines. ==ml -- Michael W. Lucas - mwlu...@michaelwlucas.com, Twitter @mwlauthor http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ Absolute OpenBSD 2/e - http://www.nostarch.com/openbsd2e coupon code ILUVMICHAEL gets you 30% off helps me. ___ 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 ___ 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: pkgng problem
For the archives: I left the problem alone for a few days, with no changes on my side. Came back Monday. Tried again. Everything worked on the affected machines. ==ml -- Michael W. Lucas - mwlu...@michaelwlucas.com, Twitter @mwlauthor http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ Absolute OpenBSD 2/e - http://www.nostarch.com/openbsd2e coupon code ILUVMICHAEL gets you 30% off helps me. ___ 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: pkgng problem
On 16/08/2013 13:43, Michael W. Lucas wrote: Hi, I'm sure someone has had this before, but I can't find any reference to it. # pkg upgrade Updating repository catalogue digests.txz 100% 997KB 997.1KB/s 997.1KB/s 00:00 packagesite.txz 100% 5530KB 1.8MB/s 3.2MB/s 00:03 pkg: Invalid manifest format: mapping values are not allowed in this context Incremental update completed, 0 packages processed: 0 packages updated, 0 removed and 22568 added. pkg: No digest falling back on legacy catalog format packagesite repository catalogue is up-to-date, no need to fetch fresh copy Nothing to do This is from a machine freshly converted to pkgng. Any suggestions? What repositories are you using? Please show us the result of: pkg -vv | sed -ne '/Repositories/,$p' I'd hazard a guess that the repository either had a bit of a flail when creating the catalogue, or it's running some ancient version of pkg. mapping values are not allowed in this context is an error message from libyaml, so you've got a +MANIFEST file (or the partial copy of it that gets incorporated into the repository catalogue) which it thinks contains a mapping ( a sequence of key : value pairs ) when the YAML parser was expecting an array or whatever. Cheers, Matthew ___ 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: pkgng problem
Thanks, Matt. # pkg -vv | sed -ne '/Repositories/,$p' Repositories: packagesite: url: http://pkg-test.freebsd.org/pkg-test-freebsd:9:x86:32/latest key: enabled: yes mirror_type: SRV Also: # pkg -v 1.1.4 ==ml -- Michael W. Lucas - mwlu...@michaelwlucas.com, Twitter @mwlauthor http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ Absolute OpenBSD 2/e - http://www.nostarch.com/openbsd2e coupon code ILUVMICHAEL gets you 30% off helps me. ___ 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: pkgng problem
On 16/08/2013 16:02, Michael W. Lucas wrote: Thanks, Matt. # pkg -vv | sed -ne '/Repositories/,$p' Repositories: packagesite: url: http://pkg-test.freebsd.org/pkg-test-freebsd:9:x86:32/latest key: enabled: yes mirror_type: SRV Also: # pkg -v 1.1.4 Well, looks like both of those are up-to-date versions. I wonder if the pkg-test build system threw a wobbly at all on it's i386 builder? Bapt is on holiday or I'd ask him. Cheers, Matthew ___ 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: pkgng problem
Matt, Another data point on this: Machines converted to pkgng a couple weeks ago can install new packages just fine despite showing the same error. And it looks like they download the new repo information: # pkg install sysrc Updating repository catalogue digests.txz 100% 997KB 997.1KB/s 997.1KB/s 00:00 packagesite.txz 100% 5530KB 1.4MB/s 1.9MB/s 00:04 pkg: Invalid manifest format: mapping values are not allowed in this contex Incremental update completed, 0 packages processed: 8292 packages updated, 1115 removed and 129 added. pkg: No digest falling back on legacy catalog format packagesite repository catalogue is up-to-date, no need to fetch fresh copy The following 1 packages will be installed: Installing sysrc: 5.2 The installation will require 39 kB more space 15 kB to be downloaded Proceed with installing packages [y/N]: y sysrc-5.2.txz 100% 16KB 15.8KB/s 15.8KB/s 00:00 Checking integrity... done [1/1] Installing sysrc-5.2... done Machines upgraded to pkgng this week, using the same script as I used a couple weeks ago, cannot install packages. # pkg install sysrc Updating repository catalogue digests.txz 100% 997KB 997.1KB/s 997.1KB/s 00:00 packagesite.txz 100% 5530KB 2.7MB/s 1.5MB/s 00:02 pkg: Invalid manifest format: mapping values are not allowed in this context Incremental update completed, 0 packages processed: 0 packages updated, 0 removed and 22568 added. pkg: No digest falling back on legacy catalog format packagesite repository catalogue is up-to-date, no need to fetch fresh copy pkg: No packages matching 'sysrc' has been found in the repositories Not sure if this supports the bad repo theory, but it's interesting. Thanks, ==ml -- Michael W. Lucas - mwlu...@michaelwlucas.com, Twitter @mwlauthor http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ Absolute OpenBSD 2/e - http://www.nostarch.com/openbsd2e coupon code ILUVMICHAEL gets you 30% off helps me. ___ 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: pkgng problem
Have you done a pkg update first, just in case you needed to pull in a pkgng update? -adrian ___ 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: pkgng problem
On Fri, Aug 16, 2013 at 11:23:41AM -0700, Adrian Chadd wrote: Have you done a pkg update first, just in case you needed to pull in a pkgng update? Yep, tried that. ==ml -- Michael W. Lucas - mwlu...@michaelwlucas.com, Twitter @mwlauthor http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ Absolute OpenBSD 2/e - http://www.nostarch.com/openbsd2e coupon code ILUVMICHAEL gets you 30% off helps me. ___ 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: route problem
Hi, Hope you have rebooted after enabling the gateway, but you can check this with sysctl net.inet.ip.forwarding :) So far from the server side it looks OK for me, but what are you pinging actually? How is done the configuration of the target device? This sounds like a pure routing problem, as you do not use NAT, then the devices in the 192.168.1.0/24 should know where to find your server. The basic ideas are: 1. Make 192.168.1.250 default gateway for the devices in 192.168.1.0/24 or 2. route add -net 192.168.2 gw 192.168.1.250 (syntax depends on the OS) Also check if the device you ping accepts pings - many devices denies this by default, also Windows 7/2008 and later has firewall enabled which do not permits pings. Best regards, Ivailo Tanusheff -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Pol Hallen Sent: Monday, May 20, 2013 10:59 PM To: FreeBSD Questions Subject: route problem Hi folks! On my lan I've: server1 re0 - 192.168.1.250 xl0 - 192.168.2.250 default192.168.1.212 UGS 0 189re0 127.0.0.1 link#8 UH 0 18lo0 192.168.1.0/24 link#1 U 0 6145re0 192.168.1.250 link#1 UHS 00lo0 192.168.2.0/24 link#7 U 0 2282xl0 192.168.2.250 link#7 UHS 00lo0 and gateway_enable=YES from server1 I can ping whole lan: 192.168.1.0/24, 192.168.2.0/24 from server2 re0 - 192.168.2.52 DestinationGatewayFlagsRefs Use Netif Expire default192.168.2.250 UGS 0 8450 fxp0 127.0.0.1 link#8 UH 00lo0 192.168.2.52 link#6 UHS 00lo0 I can ping 192.168.2.0/24 and ONLY 192.168.1.250. I need ping 192.168.1.0/24 lan but I can only see 192.168.1.250 any idea? thanks! Pol ___ 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 ___ 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: route problem
On 2013-05-20 3:58 pm, Pol Hallen wrote: Hi folks! On my lan I've: server1 re0 - 192.168.1.250 xl0 - 192.168.2.250 default192.168.1.212 UGS 0 189re0 127.0.0.1 link#8 UH 0 18lo0 192.168.1.0/24 link#1 U 0 6145re0 192.168.1.250 link#1 UHS 00lo0 192.168.2.0/24 link#7 U 0 2282xl0 192.168.2.250 link#7 UHS 00lo0 and gateway_enable=YES from server1 I can ping whole lan: 192.168.1.0/24, 192.168.2.0/24 from server2 re0 - 192.168.2.52 DestinationGatewayFlagsRefs Use Netif Expire default192.168.2.250 UGS 0 8450 fxp0 127.0.0.1 link#8 UH 00lo0 192.168.2.52 link#6 UHS 00lo0 I can ping 192.168.2.0/24 and ONLY 192.168.1.250. I need ping 192.168.1.0/24 lan but I can only see 192.168.1.250 any idea? thanks! Pol I'm pretty sure you need a route on server2 to 192.168.1.0/24. Try: route add 192.168.1.0/24 192.168.2.250 -- Andre Goree -=-=-=-=-=- Email - an...@drenet.net Website - http://blog.drenet.net PGP key - http://www.drenet.net/0x83ADAAAB.asc -=-=-=-=-=- ___ 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: route problem
Try: route add 192.168.1.0/24 192.168.2.250 does not run :-( Pol ___ 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: route problem
On 2013-05-20 4:19 pm, Pol Hallen wrote: Try: route add 192.168.1.0/24 192.168.2.250 does not run :-( Pol Interesting. I had a similar issue I got around with a similar route addition, though I was going from a LAN PC through my server that was running openvpn out to a remotely connected client. What was the error that the route command failed with? I could have the syntax wrong (may need a -net in there), but I'm sure I used almost the exact same thing to solve my issue -- in my case, I ran 'route add 10.0.1.0/24 10.0.0.98', where '10.0.1.0/24' is the openvpn client network and '10.0.0.98' is the LAN interface of the openvpn server. If you don't mind could you post the output of ifconfig from both boxes? -- Andre Goree -=-=-=-=-=- Email - an...@drenet.net Website - http://blog.drenet.net PGP key - http://www.drenet.net/0x83ADAAAB.asc -=-=-=-=-=- ___ 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: route problem
If you don't mind could you post the output of ifconfig from both boxes? server1: re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=8209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE ether 70:71:bc:94:c3:6d inet 192.168.1.250 netmask 0xff00 broadcast 192.168.1.255 inet6 fe80::7271:bcff:fe94:c36d%re0 prefixlen 64 scopeid 0x1 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (100baseTX full-duplex) status: active xl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=80008VLAN_MTU,LINKSTATE ether 00:60:08:6d:59:50 inet 192.168.2.250 netmask 0xff00 broadcast 192.168.2.255 inet6 fe80::260:8ff:fe6d:5950%xl0 prefixlen 64 scopeid 0x7 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=63RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 inet 127.0.0.1 netmask 0xff00 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL server2 fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=2009RXCSUM,VLAN_MTU,WOL_MAGIC ether 00:0f:fe:b3:db:8c inet6 fe80::20f:feff:feb3:db8c%fxp0 prefixlen 64 scopeid 0x6 inet 192.168.2.52 netmask 0xff00 broadcast 192.168.2.255 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (100baseTX full-duplex) status: active plip0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST metric 0 mtu 1500 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=63RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 inet 127.0.0.1 netmask 0xff00 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL ___ 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: route problem
On 2013-05-20 5:01 pm, Pol Hallen wrote: If you don't mind could you post the output of ifconfig from both boxes? server1: re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=8209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE ether 70:71:bc:94:c3:6d inet 192.168.1.250 netmask 0xff00 broadcast 192.168.1.255 inet6 fe80::7271:bcff:fe94:c36d%re0 prefixlen 64 scopeid 0x1 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (100baseTX full-duplex) status: active xl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=80008VLAN_MTU,LINKSTATE ether 00:60:08:6d:59:50 inet 192.168.2.250 netmask 0xff00 broadcast 192.168.2.255 inet6 fe80::260:8ff:fe6d:5950%xl0 prefixlen 64 scopeid 0x7 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=63RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 inet 127.0.0.1 netmask 0xff00 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL server2 fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=2009RXCSUM,VLAN_MTU,WOL_MAGIC ether 00:0f:fe:b3:db:8c inet6 fe80::20f:feff:feb3:db8c%fxp0 prefixlen 64 scopeid 0x6 inet 192.168.2.52 netmask 0xff00 broadcast 192.168.2.255 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (100baseTX full-duplex) status: active plip0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST metric 0 mtu 1500 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=63RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 inet 127.0.0.1 netmask 0xff00 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL On 'server1', what is the output of 'sysctl net.inet.ip.forwarding'? Perhaps you did not reboot after you set 'gateway_enable=YES'? This is from my box with forwarding enabled: root@daemon ~ # sysctl net.inet.ip.forwarding net.inet.ip.forwarding: 1 root@daemon ~ # -- Andre Goree -=-=-=-=-=- Email - an...@drenet.net Website - http://blog.drenet.net PGP key - http://www.drenet.net/0x83ADAAAB.asc -=-=-=-=-=- ___ 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: gettext problem in FreeBSD 8.3 system hosed
On Tue, Mar 26, 2013 at 06:53:11AM -0500, Antonio Olivares typed: Dear Sir, As bapt@ hints: try rebuilding binutils without NLS. -- -- I have binutils installed without NLS. I ran make deinstall reinstall inside /usr/ports/devel/binutils/ and it deinstalls and it fails to reinstall because it depends on gettext :( Now I guess I am really in trouble. Don't do make deinstall reinstall! Run make deinstall, than make config, disable the NLS option and then run make install. Ruben ___ 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: gettext problem in FreeBSD 8.3 system hosed
Dear Sir, As bapt@ hints: try rebuilding binutils without NLS. -- -- I have binutils installed without NLS. I ran make deinstall reinstall inside /usr/ports/devel/binutils/ and it deinstalls and it fails to reinstall because it depends on gettext :( Now I guess I am really in trouble. I am not using pkgng just ports. On three machines I am successfull, two 9.1-RELEASE-p1 and one 8.3-RELEASE, but this 9.1-RELEASE box I could not build some ports, I tried deinstall/reinstall options, and now I guess I am in a major problem, unless gettext starts to build soon, I uninstalled glib20, and tried reinstall it fails with gettext. There is a new version out, but it has not made it to ports :( I'll hang in there for a little while longer, but if it comes down to deleting and reinstalling all ports, I may do just that. Best Regards Thanks for the suggestions and advice provided. Antonio ___ 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: gettext problem in FreeBSD 8.3 system hosed
Dear folks, On Mon, Mar 25, 2013 at 11:52 AM, Antonio Olivares olivares14...@gmail.com wrote: Dear folks, As following /usr/port/UPDATING, I ran into a bit of trouble. System is hosed and I cannot update any ports. I tried to follow advice here: 20130316: AFFECTS: users of converters/libiconv and devel/gettext AUTHOR: b...@freebsd.org libiconv now handles the lib/charset.alias file instead of devel/gettext. If you are using pkgng 'and' upgrading from source with portupgrade or portmaster, first delete gettext, upgrade libiconv, then reinstall gettext. # pkg delete -f devel/gettext # portmaster converters/libiconv devel/gettext or # pkg delete -f devel/gettext # portupgrade converters/libiconv devel/gettext but I get error(s) in gettext. I see that there is a small problem with gettext: http://www.freebsd.org/cgi/query-pr.cgi?pr=177176 How can I get around it, I made errors by deleting devel/gmake, and devel/glib20 and I tried to reinstall these, I did a make deinstall reinstall to see if I could bypass the error, but update(s) always fail with gettext. Any ideas/suggestions to fix this problem? Thanks in Advance, Antonio In case if anyone is wondering which error I am encountering: It is the following: http://lists.freebsd.org/pipermail/freebsd-ports/2013-February/081576.html http://forums.freebsd.org/showthread.php?t=38558 devel/glib20 fails to build also with error: http://www.freebsd.org/cgi/query-pr.cgi?pr=177069 I have tried to follow the instructions included in /usr/ports/UPDATING but I have not succeeded in this machine. I am thinking of moving it to 8.4-BETA1 release and then reworking the ports or deleting them and restarting in case of not having replies I have gotten myself out of trouble before but it can take days to get the machine back in working order :( Best Regards, Antonio ___ 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: gettext problem in FreeBSD 8.3 system hosed
Antonio Olivares wrote: [snip] As following /usr/port/UPDATING, I ran into a bit of trouble. System is hosed and I cannot update any ports. I tried to follow advice here: 20130316: AFFECTS: users of converters/libiconv and devel/gettext AUTHOR: b...@freebsd.org libiconv now handles the lib/charset.alias file instead of devel/gettext. If you are using pkgng 'and' upgrading from source with portupgrade or portmaster, first delete gettext, upgrade libiconv, then reinstall gettext. # pkg delete -f devel/gettext # portmaster converters/libiconv devel/gettext or # pkg delete -f devel/gettext # portupgrade converters/libiconv devel/gettext [snip] I have tried to follow the instructions included in /usr/ports/UPDATING but I have not succeeded in this machine. I am thinking of moving it to 8.4-BETA1 release and then reworking the ports or deleting them and restarting in case of not having replies I have gotten myself out of trouble before but it can take days to get the machine back in working order :( Not exactly an answer here, in terms of recovery, but more along the lines of trying to figure out how it happened. Did you previously convert this machine to pkgng? The reason I ask is the instructions in UPDATING _only_ apply if you did so. If you did not, then you did not need to pay any attention to that section in UPDATING. I have not yet investigated the changeover to pkgng. I recently just did a portupgrade -a without doing as UPDATING suggested and had no difficulty with either port. So if you have not converted to pkgng then there is/was a misunderstanding in the reading of UPDATING. If you did convert to pkgng then you are in new territory I have not seen yet, and the point is moot. -Mike ___ 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: gettext problem in FreeBSD 8.3 system hosed
On 25 March 2013 20:12, Michael Powell nightre...@hotmail.com wrote: Antonio Olivares wrote: [snip] As following /usr/port/UPDATING, I ran into a bit of trouble. System is hosed and I cannot update any ports. I tried to follow advice here: 20130316: AFFECTS: users of converters/libiconv and devel/gettext AUTHOR: b...@freebsd.org libiconv now handles the lib/charset.alias file instead of devel/gettext. If you are using pkgng 'and' upgrading from source with portupgrade or portmaster, first delete gettext, upgrade libiconv, then reinstall gettext. # pkg delete -f devel/gettext # portmaster converters/libiconv devel/gettext or # pkg delete -f devel/gettext # portupgrade converters/libiconv devel/gettext [snip] I have tried to follow the instructions included in /usr/ports/UPDATING but I have not succeeded in this machine. I am thinking of moving it to 8.4-BETA1 release and then reworking the ports or deleting them and restarting in case of not having replies I have gotten myself out of trouble before but it can take days to get the machine back in working order :( Not exactly an answer here, in terms of recovery, but more along the lines of trying to figure out how it happened. Did you previously convert this machine to pkgng? The reason I ask is the instructions in UPDATING _only_ apply if you did so. If you did not, then you did not need to pay any attention to that section in UPDATING. I have not yet investigated the changeover to pkgng. I recently just did a portupgrade -a without doing as UPDATING suggested and had no difficulty with either port. So if you have not converted to pkgng then there is/was a misunderstanding in the reading of UPDATING. If you did convert to pkgng then you are in new territory I have not seen yet, and the point is moot. Having switched to pkgng failing in my duty to carefully read /usr/ports/UPDATING before rather blindly running portmaster -a I ran into this problem (to a smaller extent, at least). I ran the suggested pkg delete -f gettext, which instantly hosed sudo. (Why sudo has NLS on by default is beyond me. Why sudo isn't a static binary is another issue entirely.) However, su still worked I the portmaster stage ran without difficulty. In a pre-pkgng world ( without portmaster) I would run pkg_delete -f gettext cd /usr/ports/converters/libiconv make deinstall reinstall cd ../../devel/gettext make install as root. Or some variation on that, perhaps involving -C (I've become addicted to abusing make something -C someplace ;) /or a clean being added to the make arguments. -- -- ___ 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: gettext problem in FreeBSD 8.3 system hosed
On 25 March 2013 12:52, Antonio Olivares olivares14...@gmail.com wrote: Dear folks, As following /usr/port/UPDATING, I ran into a bit of trouble. System is hosed and I cannot update any ports. I tried to follow advice here: 20130316: AFFECTS: users of converters/libiconv and devel/gettext AUTHOR: b...@freebsd.org libiconv now handles the lib/charset.alias file instead of devel/gettext. If you are using pkgng 'and' upgrading from source with portupgrade or portmaster, first delete gettext, upgrade libiconv, then reinstall gettext. # pkg delete -f devel/gettext # portmaster converters/libiconv devel/gettext or # pkg delete -f devel/gettext # portupgrade converters/libiconv devel/gettext but I get error(s) in gettext. I see that there is a small problem with gettext: http://www.freebsd.org/cgi/query-pr.cgi?pr=177176 How can I get around it, I made errors by deleting devel/gmake, and devel/glib20 and I tried to reinstall these, I did a make deinstall reinstall to see if I could bypass the error, but update(s) always fail with gettext. Any ideas/suggestions to fix this problem? As bapt@ hints: try rebuilding binutils without NLS. -- -- ___ 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: PERL problem installing SQLgrey
On 20/02/2013 21:22, lcon...@go2france.com wrote: === p5-Date-Calc-6.3 depends on package: p5-Bit-Vector=7.1 - not found ===Verifying install for p5-Bit-Vector=7.1 in /usr/ports/math/p5-Bit-Vector === Extracting for p5-Bit-Vector-7.2_2 = SHA256 Checksum mismatch for Bit-Vector-7.2.tar.gz. and it can't find it anywhere else. bombs out with: fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/Bit-Vector-7.2.tar.gz: size mismatch: expected 135586, actual 137817 = Couldn't fetch it - please try to retrieve this = port manually into /usr/ports/distfiles/ and try again. *** Error code 1 Did you try updating your ports to the latest and: cd /usr/ports/math/p5-Bit-Vector make distclean and then try and install sqlgrey again? If you get the same error repeatably, then it's possibly a bug in the p5-Bit-Vector port -- perhaps the distfile was changed, in which case the port maintainer would have to update the distinfo to match. In any case, if you're still having problems, please ask again on freebsd-po...@freebsd.org Cheers, Matthew ___ 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: Booting Problem
On 29 January 2013, at 20:25, d...@safeport.com wrote: On Tue, 29 Jan 2013, Doug Hardie wrote: On 29 January 2013, at 07:18, Mario Lobo wrote: On Mon, 28 Jan 2013 15:16:14 -0800 Doug Hardie bc...@lafn.org wrote: I have a relatively old machine that I am trying to boot 9.1 on. The bios will not boot from USB stick. I am using an external CD drive. It starts the boot process fine and gets to the Bootstrap loader message with revision 1.1. Then it puts out the machine, date, time the CD was created and starts the spinner. It spins around about 2 times and stops. The system continues to read from the drive for another couple minutes. Then everything stops. Nothing more happens. The CD is good. I can boot it just fine using the same external drive on another machine. While I could remove the drive and temporarily mount in in the working machine and build it there, I would like to find a way to successfully boot from CD. This will become a remote machine and taking it apart later is not a viable option. What is the system you are using? What external devices does it have built-in support for? In the absence of any data - how about trying an external hard drive? 9.1 release - Generic. Basically the disk1. Don't have an extra external drive. Why not remove the hard drive, use another system to put FreeBSD on the drive, and put it back. From that point on you should be able to use the network to upgrade. I have done that before and it does work. However, with the various changes to the system, the root partition I had previously built that way for 8.2 is just not large enough for 9.1. Also, I wanted to go to a single partition (the 9.1 default). Probably freebsd-update will take me through major releases after this, but I was hoping for a better solution so I could avoid having to transport the machine a long way twice to be able to update it. ___ 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: Booting Problem
On 1/29/2013 10:25 PM, d...@safeport.com wrote: What is the system you are using? What external devices does it have built-in support for? In the absence of any data - how about trying an external hard drive? Why not remove the hard drive, use another system to put FreeBSD on the drive, and put it back. From that point on you should be able to use the network to upgrade. I had to do something like this to try out PC-BSD years ago. I had one computer that wouldn't boot the install CD. I moved the hard drive to a computer that would boot the install CD. The catch was the computer that could boot the install CD wouldn't boot PC-BSD from the hard drive. Sometimes you just find hardware that doesn't behave. I'd also double check your BIOS settings for USB emulation. Most external CD drives are just an IDE or SATA drive with an adapter. If you take it apart, you can put the drive into the computer and see if skipping the USB helps it to boot. It's also a nice way to find a cheap drive. ___ 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: Booting Problem
Doug Hardie wrote: On 29 January 2013, at 07:18, Mario Lobo wrote: On Mon, 28 Jan 2013 15:16:14 -0800 Doug Hardie bc...@lafn.org wrote: I have a relatively old machine that I am trying to boot 9.1 on. The bios will not boot from USB stick. I am using an external CD drive. It starts the boot process fine and gets to the Bootstrap loader message with revision 1.1. Then it puts out the machine, date, time the CD was created and starts the spinner. It spins around about 2 times and stops. The system continues to read from the drive for another couple minutes. Then everything stops. Nothing more happens. The CD is good. I can boot it just fine using the same external drive on another machine. While I could remove the drive and temporarily mount in in the working machine and build it there, I would like to find a way to successfully boot from CD. This will become a remote machine and taking it apart later is not a viable option. ___ 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 Can you boot a different OS (Win, Ububtu, gparted, etc ...) from the same drive on the same machine? Not so far. The drive works fine on other systems. You said in your orginal post The bios will not boot from USB stick. I see no reason why you would think your PC would BOOT from any USB attached devices. Since you have another PC that does boot off of usb cd drive, swap hard drives and use that pc to load FreeBSD to the hard drive. This method will work for you. ___ 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: Booting Problem
On 30 January 2013, at 05:16, Fbsd8 wrote: Doug Hardie wrote: On 29 January 2013, at 07:18, Mario Lobo wrote: On Mon, 28 Jan 2013 15:16:14 -0800 Doug Hardie bc...@lafn.org wrote: I have a relatively old machine that I am trying to boot 9.1 on. The bios will not boot from USB stick. I am using an external CD drive. It starts the boot process fine and gets to the Bootstrap loader message with revision 1.1. Then it puts out the machine, date, time the CD was created and starts the spinner. It spins around about 2 times and stops. The system continues to read from the drive for another couple minutes. Then everything stops. Nothing more happens. The CD is good. I can boot it just fine using the same external drive on another machine. While I could remove the drive and temporarily mount in in the working machine and build it there, I would like to find a way to successfully boot from CD. This will become a remote machine and taking it apart later is not a viable option. ___ 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 Can you boot a different OS (Win, Ububtu, gparted, etc ...) from the same drive on the same machine? Not so far. The drive works fine on other systems. You said in your orginal post The bios will not boot from USB stick. I see no reason why you would think your PC would BOOT from any USB attached devices. Since you have another PC that does boot off of usb cd drive, swap hard drives and use that pc to load FreeBSD to the hard drive. This method will work for you. Yes that works now. But starting this weekend it will be about 100 miles away. That no longer will be practical. ___ 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: Booting Problem
On Wed, 30 Jan 2013, Doug Hardie wrote: On 30 January 2013, at 05:16, Fbsd8 wrote: Doug Hardie wrote: On 29 January 2013, at 07:18, Mario Lobo wrote: On Mon, 28 Jan 2013 15:16:14 -0800 Doug Hardie bc...@lafn.org wrote: I have a relatively old machine that I am trying to boot 9.1 on. The bios will not boot from USB stick. I am using an external CD drive. It starts the boot process fine and gets to the Bootstrap loader message with revision 1.1. Then it puts out the machine, date, time the CD was created and starts the spinner. It spins around about 2 times and stops. The system continues to read from the drive for another couple minutes. Then everything stops. Nothing more happens. The CD is good. I can boot it just fine using the same external drive on another machine. While I could remove the drive and temporarily mount in in the working machine and build it there, I would like to find a way to successfully boot from CD. This will become a remote machine and taking it apart later is not a viable option. ___ 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 Can you boot a different OS (Win, Ububtu, gparted, etc ...) from the same drive on the same machine? Not so far. The drive works fine on other systems. You said in your orginal post The bios will not boot from USB stick. I see no reason why you would think your PC would BOOT from any USB attached devices. Since you have another PC that does boot off of usb cd drive, swap hard drives and use that pc to load FreeBSD to the hard drive. This method will work for you. Yes that works now. But starting this weekend it will be about 100 miles away. That no longer will be practical. The CD will not be of much help then either. The problem started with the root partition being too small. Just repartition to make sure that does not come up for a while. While you have you hands of the machine you should see if you can figure out if it can do a pixe boot. You should also see if you can arrange for a serial console into the system. ___ 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: Booting Problem
On Mon, 28 Jan 2013 15:16:14 -0800 Doug Hardie bc...@lafn.org wrote: I have a relatively old machine that I am trying to boot 9.1 on. The bios will not boot from USB stick. I am using an external CD drive. It starts the boot process fine and gets to the Bootstrap loader message with revision 1.1. Then it puts out the machine, date, time the CD was created and starts the spinner. It spins around about 2 times and stops. The system continues to read from the drive for another couple minutes. Then everything stops. Nothing more happens. The CD is good. I can boot it just fine using the same external drive on another machine. While I could remove the drive and temporarily mount in in the working machine and build it there, I would like to find a way to successfully boot from CD. This will become a remote machine and taking it apart later is not a viable option. ___ 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 Can you boot a different OS (Win, Ububtu, gparted, etc ...) from the same drive on the same machine? -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblows FREE) ___ 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: Booting Problem
On 29 January 2013, at 07:18, Mario Lobo wrote: On Mon, 28 Jan 2013 15:16:14 -0800 Doug Hardie bc...@lafn.org wrote: I have a relatively old machine that I am trying to boot 9.1 on. The bios will not boot from USB stick. I am using an external CD drive. It starts the boot process fine and gets to the Bootstrap loader message with revision 1.1. Then it puts out the machine, date, time the CD was created and starts the spinner. It spins around about 2 times and stops. The system continues to read from the drive for another couple minutes. Then everything stops. Nothing more happens. The CD is good. I can boot it just fine using the same external drive on another machine. While I could remove the drive and temporarily mount in in the working machine and build it there, I would like to find a way to successfully boot from CD. This will become a remote machine and taking it apart later is not a viable option. ___ 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 Can you boot a different OS (Win, Ububtu, gparted, etc ...) from the same drive on the same machine? Not so far. The drive works fine on other systems. ___ 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: Booting Problem
On Tue, 29 Jan 2013, Doug Hardie wrote: On 29 January 2013, at 07:18, Mario Lobo wrote: On Mon, 28 Jan 2013 15:16:14 -0800 Doug Hardie bc...@lafn.org wrote: I have a relatively old machine that I am trying to boot 9.1 on. The bios will not boot from USB stick. I am using an external CD drive. It starts the boot process fine and gets to the Bootstrap loader message with revision 1.1. Then it puts out the machine, date, time the CD was created and starts the spinner. It spins around about 2 times and stops. The system continues to read from the drive for another couple minutes. Then everything stops. Nothing more happens. The CD is good. I can boot it just fine using the same external drive on another machine. While I could remove the drive and temporarily mount in in the working machine and build it there, I would like to find a way to successfully boot from CD. This will become a remote machine and taking it apart later is not a viable option. What is the system you are using? What external devices does it have built-in support for? In the absence of any data - how about trying an external hard drive? Why not remove the hard drive, use another system to put FreeBSD on the drive, and put it back. From that point on you should be able to use the network to upgrade. ___ 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: Should newfs include -S 4096? was Re: boot problem after freebsd-update from 9.1-RC2 to 9.1-RC3
On Fri, 23 Nov 2012, free...@johnea.net wrote: One of the complications was getting old metadata off of the drive. After trying a couple of 'dd' invocations: # overwriting the first sector dd if=/dev/zero of=/dev/ada0 bs=512 count=1 # also tried overwriting the last sector diskinfo ada0 | cut -f4 3907029168 (subtract 34, per WB) (I actually just subtracted the trailing 68) dd if=/dev/zero of=/dev/ada0 seek=3907029100 This would still seem to not delete all of the metadata, since after issuing: gmirror label -b split gm0 /dev/ada0 gmirror load # repartition new mirror gpart create -s MBR mirror/gm0 # ignore mirror/gm0s1 added, but partition is not aligned on 4096 bytes after add gpart add -t freebsd -a 4k mirror/gm0 # create the bsdlabel partitions in slice 1 (s1) gpart create -s BSD mirror/gm0s1 I would see that the old gm0s1a and gm0s1b had reappeared, even though I had not yet issued the 'add -t freebsd-ufs'. I'm not sure if they came back with the 'add -t freebsd' or the 'create -s BSD'. Saved this since yesterday, thinking maybe I could come up with an idea, but so far I can't think what would cause that. It might not hurt to force a retaste after the dd. The only thing that seemed to fix it was: gpart destroy -F /dev/ada0 I also tried at one point: gpart destroy -F ada0 gpart create -s gpt ada0 gpart destroy -F ada0 The thing I wonder about now: Should newfs include -S 4096? I used: newfs -U /dev/mirror/gm0s1a Will this lead to 512 byte sector access to the disk through the file system? Will this impact performance or longevity of the mirror? It's a good question; I have not tried it. ___ 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
Should newfs include -S 4096? was Re: boot problem after freebsd-update from 9.1-RC2 to 9.1-RC3
On 2012-11-20 21:10, Warren Block wrote: On Tue, 20 Nov 2012, free...@johnea.net wrote: On 2012-11-20 14:28, Gary Aitken wrote: On 11/20/12 13:34, free...@johnea.net wrote: freebsd-update upgrade -r 9.1-RC3 ... Not UFS No ada0 No boot Seems like it isn't supposed to work for 9.1-RC2 I previously used binary update to migrate from 9.0 to 9.1, via: freebsd-update upgrade -r 9.1-RC1 freebsd-update install reboot freebsd-update install reboot I'm starting to think having the swap partition in gm0s1a and the booting UFS partition in ada0s1b is the problem: http://forums.freebsd.org/showthread.php?t=31954 The Not UFS error comes immediately on boot. If I boot from rescue media, I can start the gmirror, mount it and chroot into it. The whole install seems fine except for the first stage boot loader finding the UFS partition. A handy bootloader config trick would be greatly appreciated! boot(8) says The automatic boot will attempt to load /boot/loader from partition `a' of either the floppy or the hard disk. You could try setting the correct device path in /boot/boot.config, but I suspect that won't be read until too late. gptboot looks for the first UFS partition. Maybe /boot/boot can be modified to do that also. I ended up booting from rescue media, removing one drive and stopping the gmirror, creating a new gmirror on the removed drive to place the UFS partition first, and performing a dump/restore to transfer the system. Then I was able to boot from the new gmitrror and add the second drive to it. One of the complications was getting old metadata off of the drive. After trying a couple of 'dd' invocations: # overwriting the first sector dd if=/dev/zero of=/dev/ada0 bs=512 count=1 # also tried overwriting the last sector diskinfo ada0 | cut -f4 3907029168 (subtract 34, per WB) (I actually just subtracted the trailing 68) dd if=/dev/zero of=/dev/ada0 seek=3907029100 This would still seem to not delete all of the metadata, since after issuing: gmirror label -b split gm0 /dev/ada0 gmirror load # repartition new mirror gpart create -s MBR mirror/gm0 # ignore mirror/gm0s1 added, but partition is not aligned on 4096 bytes after add gpart add -t freebsd -a 4k mirror/gm0 # create the bsdlabel partitions in slice 1 (s1) gpart create -s BSD mirror/gm0s1 I would see that the old gm0s1a and gm0s1b had reappeared, even though I had not yet issued the 'add -t freebsd-ufs'. I'm not sure if they came back with the 'add -t freebsd' or the 'create -s BSD'. The only thing that seemed to fix it was: gpart destroy -F /dev/ada0 I also tried at one point: gpart destroy -F ada0 gpart create -s gpt ada0 gpart destroy -F ada0 After that I could create the new partitions within the slice, with freebsd-ufs first: # size of ufs partition must be calculated, from 'diskinfo -v /dev/ada0': 2000398934016 # media size in bytes (1.8T) ; 1024*1024*1024 1073741824 ; 2000398934016/1073741824 1863.01668548583984375 # subtract 8G from 1863 = 1855G gpart add -t freebsd-ufs -a 4k -s 1855G mirror/gm0s1 gpart add -t freebsd-swap -a 4k mirror/gm0s1 Everything looks good with 4K alignment, and freebsd-ufs first: gpart show =63 3907029104 mirror/gm0 MBR (1.8T) 63 63 - free - (31k) 126 3907028979 1 freebsd [active] (1.8T) 3907029105 62 - free - (31k) = 0 3907028979 mirror/gm0s1 BSD (1.8T) 0 2- free - (1.0k) 2 3890216960 1 freebsd-ufs (1.8T) 389021696216812016 2 freebsd-swap (8.0G) 3907028978 1- free - (512B) After newfs, I was able to dump/restore to transfer the installed system from ada1 to gm0 (which is 9.1-RC3 now). The thing I wonder about now: Should newfs include -S 4096? I used: newfs -U /dev/mirror/gm0s1a Will this lead to 512 byte sector access to the disk through the file system? Will this impact performance or longevity of the mirror? Thanks again for the sage advice! johnea ___ 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 booting (Was: Re: boot problem after freebsd-update from 9.1-RC2 to 9.1-RC3)
On 11/21/12 05:11, Warren Block wrote: gptboot looks for the first UFS partition. Maybe /boot/boot can be modified to do that also. It's a little more complicated than that Warren. AIUI gptboot first looks (in partition order) for partitions with both the bootme and bootonce attributes set. If it doesn't find any, or if they all failed to boot it then tries booting partitions with just the bootme attribute. It only boots the first UFS partition if no partitions have the bootme attribute set, and IIRC that is for compatibility with the 8.x gptboot which didn't know the boot* attributes. Confusingly, there's no manual page for gptboot to document this. It's sort of implicit in the gpart manual page, in the section on ATTRIBUTES for GPT, but the best way to understand it is to read the code for gptfind in /usr/src/sys/boot/common/gpt.c ___ 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 booting (Was: Re: boot problem after freebsd-update from 9.1-RC2 to 9.1-RC3)
On Wed, 21 Nov 2012, Arthur Chance wrote: On 11/21/12 05:11, Warren Block wrote: gptboot looks for the first UFS partition. Maybe /boot/boot can be modified to do that also. It's a little more complicated than that Warren. AIUI gptboot first looks (in partition order) for partitions with both the bootme and bootonce attributes set. If it doesn't find any, or if they all failed to boot it then tries booting partitions with just the bootme attribute. It only boots the first UFS partition if no partitions have the bootme attribute set, and IIRC that is for compatibility with the 8.x gptboot which didn't know the boot* attributes. Confusingly, there's no manual page for gptboot to document this. It's sort of implicit in the gpart manual page, in the section on ATTRIBUTES for GPT, but the best way to understand it is to read the code for gptfind in /usr/src/sys/boot/common/gpt.c Well, yes. The point is that gptboot doesn't just assume that p2, say, is where the bootable UFS partition must be. I've also noted the lack of a gptboot man page, and it's on my long list of Things That Should Be Done. There was a thread on -doc: http://lists.freebsd.org/pipermail/freebsd-doc/2012-June/020060.html Help would be greatly appreciated. ___ 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: boot problem after freebsd-update from 9.1-RC2 to 9.1-RC3
On 11/20/12 13:34, free...@johnea.net wrote: Hello, I recently installed a 9.1-RC2 system using gmirror with MBR, and swap in first bsdlabel. orsbackup# gpart show =63 3907029104 mirror/gm0 MBR (1.8T) 63 63 - free - (31k) 126 3907028979 1 freebsd [active] (1.8T) 3907029105 62 - free - (31k) = 0 3907028979 mirror/gm0s1 BSD (1.8T) 0 2- free - (1.0k) 216777216 1 freebsd-swap (8.0G) 16777218 3890251760 2 freebsd-ufs (1.8T) 3907028978 1- free - (512B) The drive was setup with the following commands: orsbackup# gpart create -s MBR mirror/gm0 mirror/gm0 created orsbackup# gpart add -t freebsd -a 4k mirror/gm0 # ignored mirror/gm0s1 added, but partition is not aligned on 4096 bytes # create the bsdlabel partitions in slice 1 (s1) orsbackup# gpart create -s BSD mirror/gm0s1 orsbackup# gpart add -t freebsd-swap -a 4k -s 8g mirror/gm0s1 orsbackup# gpart add -t freebsd-ufs -a 4k mirror/gm0s1 # put bootcode on the MBR and mark the first slice active orsbackup# gpart bootcode -b /boot/mbr mirror/gm0 orsbackup# gpart set -a active -i 1 mirror/gm0 # put bootcode on the bsdlabel orsbackup# gpart bootcode -b /boot/boot mirror/gm0s1 The system rebooted several times without issue. This system is a testbed for 9.1 and is not yet deployed as a production server. I thought I'd update to 9.1-RC3, so I ran: freebsd-update upgrade -r 9.1-RC3 freebsd-update install reboot The system won't boot and complains about: Not UFS No ada0 No boot Before I charge ahead with reissuing the gpart bootcode commands I thought I'd: a) make others aware there may be issues in freebsd-update with the 9.1 release candidates b) ask about the best way to resolve this bootloader issue. Thanks you for any pointers in resolving this bootloader issue! johnea Not sure, but this might apply: The freebsd-update tool is used to fetch, install, and rollback binary updates to the FreeBSD base system. Note that updates are only available if they are being built for the FreeBSD release and architecture being used; in particular, the FreeBSD Security Team only builds updates for releases shipped in binary form by the FreeBSD Release Engineering Team, e.g., FreeBSD 7.3-RELEASE and FreeBSD 8.0-RELEASE, but not FreeBSD 6.3-STABLE or FreeBSD 9.0-CURRENT. Seems like it isn't supposed to work for 9.1-RC2 ___ 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: boot problem after freebsd-update from 9.1-RC2 to 9.1-RC3
On 2012-11-20 14:28, Gary Aitken wrote: On 11/20/12 13:34, free...@johnea.net wrote: freebsd-update upgrade -r 9.1-RC3 ... Not UFS No ada0 No boot Seems like it isn't supposed to work for 9.1-RC2 I previously used binary update to migrate from 9.0 to 9.1, via: freebsd-update upgrade -r 9.1-RC1 freebsd-update install reboot freebsd-update install reboot I'm starting to think having the swap partition in gm0s1a and the booting UFS partition in ada0s1b is the problem: http://forums.freebsd.org/showthread.php?t=31954 The Not UFS error comes immediately on boot. If I boot from rescue media, I can start the gmirror, mount it and chroot into it. The whole install seems fine except for the first stage boot loader finding the UFS partition. A handy bootloader config trick would be greatly appreciated! johnea ___ 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: boot problem after freebsd-update from 9.1-RC2 to 9.1-RC3
On Tue, 20 Nov 2012, free...@johnea.net wrote: On 2012-11-20 14:28, Gary Aitken wrote: On 11/20/12 13:34, free...@johnea.net wrote: freebsd-update upgrade -r 9.1-RC3 ... Not UFS No ada0 No boot Seems like it isn't supposed to work for 9.1-RC2 I previously used binary update to migrate from 9.0 to 9.1, via: freebsd-update upgrade -r 9.1-RC1 freebsd-update install reboot freebsd-update install reboot I'm starting to think having the swap partition in gm0s1a and the booting UFS partition in ada0s1b is the problem: http://forums.freebsd.org/showthread.php?t=31954 The Not UFS error comes immediately on boot. If I boot from rescue media, I can start the gmirror, mount it and chroot into it. The whole install seems fine except for the first stage boot loader finding the UFS partition. A handy bootloader config trick would be greatly appreciated! boot(8) says The automatic boot will attempt to load /boot/loader from partition `a' of either the floppy or the hard disk. You could try setting the correct device path in /boot/boot.config, but I suspect that won't be read until too late. gptboot looks for the first UFS partition. Maybe /boot/boot can be modified to do that also. ___ 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: Gimp - problem opening images using URI's
Could you trace gimp using truss utility and upload an output somewhere? On Mon, Oct 22, 2012 at 11:56 PM, Mike Clarke jmc-freeb...@milibyte.co.uk wrote: Gimp has recently become unable to open images using URI's, e.g.- -- curlew:/home/mike% gimp -c http://www.freebsd.org/layout/images/beastie.png; Failed to connect to socket /tmp/fam-mike/fam- (gimp:27650): GLib-GIO-WARNING **: FAMOpen failed, FAMErrno=3 GIMP-Error: Opening 'http://www.freebsd.org/layout/images/beastie.png' failed: Could not open 'http://www.freebsd.org/layout/images/beastie.png' for reading: No such file or directory -- The above is with gimp-app-2.6.12_1,1 compiled from ports with default options running under FreeBSD 9.0-RELEASE, all ports are up to date and there are no missing dependencies. I had similar problems in the past and managed to fix it by adding --without-gvfs to the options in the Makefile but the problem reappeared after a recent upgrade to my ports. The port upgrade didn't touch gimp-app so I assume the problem is caused by some dependency which has been upgraded. I've tried rebuilding gimp-app both with and without my Makefile hack and with and without GVFS in the config options but with no success. The error message above is after rebuilding from a freshly downloaded copy of the port to ensure none of my old edits remained and with the default options in make config. It might be significant that the directory /tmp/fam-mike does not exist. I tried creating it but gimp produced an error Socket directory /tmp/fam-mike has wrong permissions and promptly deleted the directory. Recreating /tmp/fam-mike with permissions 700 got rid of the wrong permissions message but still failed to cure the problem. Google searches haven't come up with anything directly relevant to my problem but do imply that the problem could be related to devel/gamin. Could anyone offer any suggestions on how to go about resolving this? -- Mike Clarke ___ 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 -- Best regards, Alex Alexeev http://twitter.com/afiskon ___ 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: A problem with loader
OK, maybe different way: where is the source code for this loader available? Somehow I'm unable to find it. -- Z. ___ 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: A problem with loader
On Fri, 5 Oct 2012 09:30:56 +, Zbigniew wrote: OK, maybe different way: where is the source code for this loader available? Somehow I'm unable to find it. You're searching for this? /usr/src/sys/boot/i386/loader And the Forth related stuff: /usr/src/sys/boot/forth -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: A problem with loader
2012/10/5, Polytropon free...@edvax.de: You're searching for this? /usr/src/sys/boot/i386/loader And the Forth related stuff: /usr/src/sys/boot/forth Made a quick search in the Internet - maybe too quick indeed. And not really necessary, it seems. Thanks. -- Z. ___ 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: A problem with loader
On Fri, 5 Oct 2012 09:46:13 +, Zbigniew wrote: 2012/10/5, Polytropon free...@edvax.de: You're searching for this? /usr/src/sys/boot/i386/loader And the Forth related stuff: /usr/src/sys/boot/forth Made a quick search in the Internet - maybe too quick indeed. Just make a quick search in the src/ subtree, as I did. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: A problem with loader
2012/10/3, Thomas Mueller muelle...@insightbb.com: installed recently 9.0 - and I've got a little problem: while booting, loader somehow gets incorrect currdevice value, stopping boot process. It does get disk1s6a, but it should be disk1s7a. I can boot system, when I set currdev manually, then type boot. But how can I change it for steady, avoiding this typing each time? Of course, loader won't read its config files, when not having access to root directory. How can I pass the proper value to loader immediately? Maybe the fact, that I'm booting FreeBSD using GRUB, can be of any help? Which GRUB are you using, legacy (0.97) or GRUB2? Legacy GRUB 0.97. Are you sure you specify the partition correctly in GRUB? Partition numbering starts from 0 in GRUB legacy but from 1 in GRUB2. Well, it seems so; it's booting at least to loader's shell, and - besides - it doesn't allow me to select partition 6, as non-existing. But what about any possibility to pass the proper value for currdisk to loader? -- regards, Z. ___ 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: A problem with loader
from Zbigniew zbigniew2...@gmail.com : installed recently 9.0 - and I've got a little problem: while booting, loader somehow gets incorrect currdevice value, stopping boot process. It does get disk1s6a, but it should be disk1s7a. I can boot system, when I set currdev manually, then type boot. But how can I change it for steady, avoiding this typing each time? Of course, loader won't read its config files, when not having access to root directory. How can I pass the proper value to loader immediately? Maybe the fact, that I'm booting FreeBSD using GRUB, can be of any help? -- regards, Zbigniew Which GRUB are you using, legacy (0.97) or GRUB2? Are you sure you specify the partition correctly in GRUB? Partition numbering starts from 0 in GRUB legacy but from 1 in GRUB2. Tom ___ 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: weird problem with 9.0 Release and ed0
Am 11.08.2012 09:58, schrieb Ian Smith: In freebsd-questions Digest, Vol 427, Issue 6, Message: 16 On Fri, 10 Aug 2012 12:39:36 +0200 Christoph P.U. Kukulies k...@kukulies.org wrote: Am 10.08.2012 11:40, schrieb Christoph P.U. Kukulies: Am 10.08.2012 11:28, schrieb Christoph P.U. Kukulies: The problem need not to be confined to 9.0. It stated to develop under 5.1 already. read: started to develop... I'm running a natd gateway machine that was developing strange behaviour such that the outside interface (ed0, BNC connector) that was connected via a small media converter switch to the providers sync line had dropouts. The machine couldn't ping into the Internet and also couldn't be pinged. I first thought it was the switch/media converter, but another (Windows XP) machine that was on the same BNC cable worked flawlessly. That XP box was directly on the outside, not inside nat'd via this one? Yes, on the same BNC cable/interface. --++--80.72.44.x+---[SWITCH/BNCtoTP]-INTERNET-- || | 80.72.44.228 80.72.44.226 | ed0 | ed0 FreeBSD 5.1 XP Box FreeBSD 9.0 xl0 em0 | | --+-172.27.x.x+Intranet So I decided to migrate that 5.1 machine to a 9.0 machine. The situation now is that I have the9.0 machine at the BNC cable and simultanously the old FreeBSD 5.1 gateway on the same BNC cable but through a TP adapter. This was the old machine works fine and I can care about the new machine. Not quite clear .. can you sketch your network configuration? Hope the ascii art doesn't get garbled. Is there a known problem with ed0 cards that have the Realtek 8029 chipset. Do they need some special flags like memory mapping or irq? Long time since I've run anything with 10base2/BNC, but it used to work ok, on an ed0. When I for example boot the 9.0 machine the comping up of the em0 (on mainboard interface results in a highlighted kernel message on the console. The coming up of the ed0 is not flagged this way. And as a result the ed0 interface seems to be dead. Does the outside interface have a static address, or do you use DHCP via the provider's switch/hub/whatever? Show /etc/rc.conf setup. It smells a bit like the interface may not be up soon enough at that time; the ntpd message below could also indicate something like that re ipv6. No DHCP in the game. Everything static. Here some excerpts of dmesg: em0: Intel(R) PRO/1000 Network Connection 7.2.3 port 0x4400-0x441f mem 0x9310-0x9311,0x93124000-0x93124fff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Ethernet address: 00:1c:c0:37:b2:9f ed0: RealTek 8029 port 0x1000-0x101f irq 22 at device 1.0 on pci7 ed0: Ethernet address: 00:e0:7d:7c:2b:4a I also see this: Jul 30 23:03:54 forum ntpd[1711]: unable to create socket on ed0 (20) for fe80:: 2e0:7dff:fe7c:2b4a#123 You should get more / better clues if you boot with verbose messages. Forgot to add this info: ed0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:e0:7d:7c:2b:4a inet 80.72.44.230 netmask 0xfff0 broadcast 80.72.44.239 inet6 fe80::2e0:7dff:fe7c:2b4a%ed0 prefixlen 64 scopeid 0xa nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (10base2/BNC) Must add some more info: My kernel config: cpu I486_CPU cpu I586_CPU cpu I686_CPU ident DIVERT makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=10 options IPDIVERT options IPFIREWALL_DEFAULT_TO_ACCEPT (the rest like in GENERIC). Just to mention: you don't actually need to include FIREWALL* or DIVERT in kernels these days; a GENERIC kernel will work fine, loading modules as needed. Only exception is if you needed FIREWALL_FORWARD, which it appears you don't. Ah, that's good to know. Strange thing: I cannot ping neither the outside interface address nor the inside (172.27.2.115) forum2# egrep 'ifconfig|firewall|natd|gateway|ntpd' /etc/rc.conf ### Basic network and firewall/security options: ### ifconfig_em0= inet 172.27.2.115 netmask 255.255.0.0 ifconfig_lo0=inet 127.0.0.1 # default loopback device configuration. ifconfig_ed0=inet 87.79.34.230 netmask 0xfff0 ntpd_enable=NO natd_enable=YES # Enable natd (if firewall_enable == YES). natd_program=/sbin/natd # path to natd, if you want a different one. natd_interface=ed0# Public interface or IPaddress to use. natd_flags= # Additional
Re: weird problem with 9.0 Release and ed0
In freebsd-questions Digest, Vol 427, Issue 6, Message: 16 On Fri, 10 Aug 2012 12:39:36 +0200 Christoph P.U. Kukulies k...@kukulies.org wrote: Am 10.08.2012 11:40, schrieb Christoph P.U. Kukulies: Am 10.08.2012 11:28, schrieb Christoph P.U. Kukulies: The problem need not to be confined to 9.0. It stated to develop under 5.1 already. read: started to develop... I'm running a natd gateway machine that was developing strange behaviour such that the outside interface (ed0, BNC connector) that was connected via a small media converter switch to the providers sync line had dropouts. The machine couldn't ping into the Internet and also couldn't be pinged. I first thought it was the switch/media converter, but another (Windows XP) machine that was on the same BNC cable worked flawlessly. That XP box was directly on the outside, not inside nat'd via this one? So I decided to migrate that 5.1 machine to a 9.0 machine. The situation now is that I have the9.0 machine at the BNC cable and simultanously the old FreeBSD 5.1 gateway on the same BNC cable but through a TP adapter. This was the old machine works fine and I can care about the new machine. Not quite clear .. can you sketch your network configuration? Is there a known problem with ed0 cards that have the Realtek 8029 chipset. Do they need some special flags like memory mapping or irq? Long time since I've run anything with 10base2/BNC, but it used to work ok, on an ed0. When I for example boot the 9.0 machine the comping up of the em0 (on mainboard interface results in a highlighted kernel message on the console. The coming up of the ed0 is not flagged this way. And as a result the ed0 interface seems to be dead. Does the outside interface have a static address, or do you use DHCP via the provider's switch/hub/whatever? Show /etc/rc.conf setup. It smells a bit like the interface may not be up soon enough at that time; the ntpd message below could also indicate something like that re ipv6. Here some excerpts of dmesg: em0: Intel(R) PRO/1000 Network Connection 7.2.3 port 0x4400-0x441f mem 0x9310-0x9311,0x93124000-0x93124fff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Ethernet address: 00:1c:c0:37:b2:9f ed0: RealTek 8029 port 0x1000-0x101f irq 22 at device 1.0 on pci7 ed0: Ethernet address: 00:e0:7d:7c:2b:4a I also see this: Jul 30 23:03:54 forum ntpd[1711]: unable to create socket on ed0 (20) for fe80:: 2e0:7dff:fe7c:2b4a#123 You should get more / better clues if you boot with verbose messages. Forgot to add this info: ed0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:e0:7d:7c:2b:4a inet 80.72.44.230 netmask 0xfff0 broadcast 80.72.44.239 inet6 fe80::2e0:7dff:fe7c:2b4a%ed0 prefixlen 64 scopeid 0xa nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (10base2/BNC) Must add some more info: My kernel config: cpu I486_CPU cpu I586_CPU cpu I686_CPU ident DIVERT makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=10 options IPDIVERT options IPFIREWALL_DEFAULT_TO_ACCEPT (the rest like in GENERIC). Just to mention: you don't actually need to include FIREWALL* or DIVERT in kernels these days; a GENERIC kernel will work fine, loading modules as needed. Only exception is if you needed FIREWALL_FORWARD, which it appears you don't. Strange thing: I cannot ping neither the outside interface address nor the inside (172.27.2.115) -- Christoph Kukulies Please show output from: # egrep 'ifconfig|firewall|natd|gateway|ntpd' /etc/rc.conf # cat /etc/natd.conf # ipfw show # netstat -finet -rn cheers, Ian ___ 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: weird problem with 9.0 Release and ed0
Am 10.08.2012 11:28, schrieb Christoph P.U. Kukulies: The problem need not to be confined to 9.0. It stated to develop under 5.1 already. read: started to develop... I'm running a natd gateway machine that was developing strange behaviour such that the outside interface (ed0, BNC connector) that was connected via a small media converter switch to the providers sync line had dropouts. The machine couldn't ping into the Internet and also couldn't be pinged. I first thought it was the switch/media converter, but another (Windows XP) machine that was on the same BNC cable worked flawlessly. So I decided to migrate that 5.1 machine to a 9.0 machine. The situation now is that I have the9.0 machine at the BNC cable and simultanously the old FreeBSD 5.1 gateway on the same BNC cable but through a TP adapter. This was the old machine works fine and I can care about the new machine. Is there a known problem with ed0 cards that have the Realtek 8029 chipset. Do they need some special flags like memory mapping or irq? When I for example boot the 9.0 machine the comping up of the em0 (on mainboard interface results in a highlighted kernel message on the console. The coming up of the ed0 is not flagged this way. And as a result the ed0 interface seems to be dead. Here some excerpts of dmesg: em0: Intel(R) PRO/1000 Network Connection 7.2.3 port 0x4400-0x441f mem 0x9310-0x9311,0x93124000-0x93124fff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Ethernet address: 00:1c:c0:37:b2:9f ed0: RealTek 8029 port 0x1000-0x101f irq 22 at device 1.0 on pci7 ed0: Ethernet address: 00:e0:7d:7c:2b:4a I also see this: Jul 30 23:03:54 forum ntpd[1711]: unable to create socket on ed0 (20) for fe80:: 2e0:7dff:fe7c:2b4a#123 Forgot to add this info: ed0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:e0:7d:7c:2b:4a inet 80.72.44.230 netmask 0xfff0 broadcast 80.72.44.239 inet6 fe80::2e0:7dff:fe7c:2b4a%ed0 prefixlen 64 scopeid 0xa nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (10base2/BNC) -- Christoph Kukulies ___ 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: weird problem with 9.0 Release and ed0
Am 10.08.2012 11:40, schrieb Christoph P.U. Kukulies: Am 10.08.2012 11:28, schrieb Christoph P.U. Kukulies: The problem need not to be confined to 9.0. It stated to develop under 5.1 already. read: started to develop... I'm running a natd gateway machine that was developing strange behaviour such that the outside interface (ed0, BNC connector) that was connected via a small media converter switch to the providers sync line had dropouts. The machine couldn't ping into the Internet and also couldn't be pinged. I first thought it was the switch/media converter, but another (Windows XP) machine that was on the same BNC cable worked flawlessly. So I decided to migrate that 5.1 machine to a 9.0 machine. The situation now is that I have the9.0 machine at the BNC cable and simultanously the old FreeBSD 5.1 gateway on the same BNC cable but through a TP adapter. This was the old machine works fine and I can care about the new machine. Is there a known problem with ed0 cards that have the Realtek 8029 chipset. Do they need some special flags like memory mapping or irq? When I for example boot the 9.0 machine the comping up of the em0 (on mainboard interface results in a highlighted kernel message on the console. The coming up of the ed0 is not flagged this way. And as a result the ed0 interface seems to be dead. Here some excerpts of dmesg: em0: Intel(R) PRO/1000 Network Connection 7.2.3 port 0x4400-0x441f mem 0x9310-0x9311,0x93124000-0x93124fff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Ethernet address: 00:1c:c0:37:b2:9f ed0: RealTek 8029 port 0x1000-0x101f irq 22 at device 1.0 on pci7 ed0: Ethernet address: 00:e0:7d:7c:2b:4a I also see this: Jul 30 23:03:54 forum ntpd[1711]: unable to create socket on ed0 (20) for fe80:: 2e0:7dff:fe7c:2b4a#123 Forgot to add this info: ed0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:e0:7d:7c:2b:4a inet 80.72.44.230 netmask 0xfff0 broadcast 80.72.44.239 inet6 fe80::2e0:7dff:fe7c:2b4a%ed0 prefixlen 64 scopeid 0xa nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (10base2/BNC) Must add some more info: My kernel config: cpu I486_CPU cpu I586_CPU cpu I686_CPU ident DIVERT makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=10 options IPDIVERT options IPFIREWALL_DEFAULT_TO_ACCEPT (the rest like in GENERIC). Strange thing: I cannot ping neither the outside interface address nor the inside (172.27.2.115) -- Christoph Kukulies ___ 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: mod_rewrite problem with tilde
David Banning david+dated+1342623098.665...@skytracker.ca wrote:
I am migrating to a new server location which right now
has no domain name, so the ip address is being used.
The ISP gives an address for the apache directory like so;
http://184.154.230.2/~smartst2/
A simple redirect works, such as this one which directs to another
site;
Options +FollowSymLinks
rewriteEngine on
rewriteRule ^test\.html$ http://www.somesite.com/index.php [R=301,L]
but a redirect within the site does not work. I wonder if it has to
do with the tilde ~ character that the ISP has configured.
I presently have the following .htaccess;
RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-l
RewriteRule ^[^/]*\.php$ /
RewriteRule ^[^/]*\.html$ index.php
Which does not work. If anyone is aware of problems using
mod_rewrite with the ~ character or could contribute any pointers
as to how I could gain more information on - for instance -where-
mod_rewrite is -attempting- to redirect (considering my above
.htaccess.
If you access your server with curl -v it will show you
were the response redirects to (if you get a redirect at
all). Checking the Apache logs would be another option,
but it may require fiddling with the log levels first.
Without knowing the URL you use for testing it's hard to
tell where the problem is, but my guess is that you are
matching against a text that contains one or more slashes
which your patterns don't allow.
Fabian
signature.asc
Description: PGP signature
Re: Configuration problem with IPv6 router (cannot forward src)
On 07/06/2012 23:36, Bruce Cran wrote: I'm trying to set up a IPv6 router (running -current) on my home network. My ISP gives me a /128 via PPP and I have a /48 allocation, which I use to give em0 and tun0 public addresses in different subnets (tun0 is assigned the address via ppp.linkup). I've added all the IPv6 settings to rc.conf (ipv6_gateway_enable, ipv6_network_interfaces, rtadvd_enable etc.) and I can ping IPv6 sites from the router. rtadvd can be limited to operate on a specific interface. Try setting rtadvd_interfaces=em0 in /etc/rc.conf The problem is that rtadvd continues advertising the default gateway as tun0's link-local address - and pinging from a machine on the network results in cannot forward src messages on the router (strangely, despite hisaddr being fe80::205:... in ppp.log, the kernel logs the address as fe80:f::205:...). Try setting: ipv6_default_interface=tun0 and possibly also ipv6_defaultrouter=-interface tun0 I use a gif tunnel (IPv6 over IPv4) for my IPv6 connectivity -- no native support for IPv6 in my ADSL router -- so not exactly equivalent but pretty similar in many ways. Is there some extra configuration I've likely missed that's needed when using IPv6 via PPP? Probably. The good news is that once you've got it running the IPv6 support in FreeBSD is rock solid and works like a charm. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Configuration problem with IPv6 router (cannot forward src)
Make sure you are only advertising a /64 addr prefixlen in rtadvd.conf, and not the entire /48. On 6/7/2012 4:36 PM, Bruce Cran wrote: I'm trying to set up a IPv6 router (running -current) on my home network. My ISP gives me a /128 via PPP and I have a /48 allocation, which I use to give em0 and tun0 public addresses in different subnets (tun0 is assigned the address via ppp.linkup). I've added all the IPv6 settings to rc.conf (ipv6_gateway_enable, ipv6_network_interfaces, rtadvd_enable etc.) and I can ping IPv6 sites from the router. The problem is that rtadvd continues advertising the default gateway as tun0's link-local address - and pinging from a machine on the network results in cannot forward src messages on the router (strangely, despite hisaddr being fe80::205:... in ppp.log, the kernel logs the address as fe80:f::205:...). Is there some extra configuration I've likely missed that's needed when using IPv6 via PPP? ___ 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: Configuration problem with IPv6 router (cannot forward src)
On 07/06/2012 23:56, Robert Bonomi wrote: Please provide the output from these two commands: ifconfig -a netstat -nr on both the router and on an 'inside' machine. (identifying which is which:) There is also a question of 'where' the /48 comes from -- and how traffic to those addresses is being routed from the outside world. The /48 came from my ISP, so it should be getting routed correctly. ifconfig -a (with ral0/lo0 removed): em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=4219bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO ether [em0_MAC] inet 192.168.2.1 netmask 0xff00 broadcast 192.168.2.255 inet6 fe80::[em0_MAC]%em0 prefixlen 64 scopeid 0x1 inet6 [prefix]:a::b prefixlen 64 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL media: Ethernet autoselect (1000baseT full-duplex) status: active em1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=4219bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO ether [em1_MAC] inet6 fe80::[em1_MAC]%em1 prefixlen 64 scopeid 0x2 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (100baseTX full-duplex) status: active tun0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST metric 0 mtu 1492 options=8LINKSTATE inet6 fe80::[em0_MAC]%tun0 prefixlen 64 scopeid 0xf inet [MYADDR] -- [HISADDR] netmask 0xff00 inet6 [prefix]:c::b prefixlen 64 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL Opened by PID 1092 Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default[HISADDR] UGS 0 2476 tun0 [MYADDR] link#15UHS 00lo0 [HISADDR] link#15UH 00 tun0 127.0.0.1 link#14UH 00lo0 192.168.2.0/24 link#1 U 0 3985em0 192.168.2.1link#1 UHS 00lo0 Internet6: Destination Gateway Flags Netif Expire ::/96 ::1 UGRSlo0 = default fe80::[em0_MAC]%tun0 UGS tun0 ::1 link#14 UH lo0 :::0.0.0.0/96 ::1 UGRSlo0 [prefix]:c::/64 link#15 U tun0 [prefix]:c::1 link#15 UHS lo0 [prefix]:a::/64 link#1 U em0 [prefix]:a::1 link#1 UHS lo0 fe80::/10 ::1 UGRSlo0 fe80::%em0/64 link#1 U em0 fe80::[em0_MAC]%em0 link#1UHS lo0 fe80::%em1/64 link#2 U em1 fe80::[em1_MAC]%em1 link#2UHS lo0 fe80::%lo0/64 link#14 U lo0 fe80::1%lo0 link#14 UHS lo0 fe80::%tun0/64link#15 US tun0 fe80::[em0_MAC]%tun0 link#15 UHS lo0 ff01::%em0/32 fe80::[em0_MAC]%em0 U em0 ff01::%em1/32 fe80::[em1_MAC]%em1 U em1 ff01::%lo0/32 ::1 U lo0 ff01::%tun0/32fe80::[em0_MAC]%tun0 US tun0 ff02::/16 ::1 UGRSlo0 ff02::%em0/32 fe80::[em0_MAC]%em0 U em0 ff02::%em1/32 fe80::[em1_MAC]%em1 U em1 ff02::%lo0/32 ::1 U lo0 ff02::%tun0/32fe80::[em0_MAC]%tun0 UGS tun0 rtadvd.conf contains: em0:\ :addrs#1:addr=[prefix]:a:::prefixlen#64;tc=ether:raflags=o: rc.conf contains: ifconfig_em0= inet 192.168.2.1 netmask 255.255.255.0 ifconfig_em0_ipv6= inet6 [prefix]:a::b ifconfig_em1=up pf_enable=YES gateway_enable=YES ppp_enable=YES ppp_nat=NO ppp_goscomb_mode=ddial ppp_goscomb_nat=NO ppp_profile=isp ipv6_gateway_enable=YES ipv6_network_interfaces=em0 em1 tun0 dhcpd_enable=YES dhcpd6_enable=NO dhcpd_flags=-q dhcpd6_flags=-q dhcpd_conf=/usr/local/etc/dhcpd.conf dhcpd6_conf=/usr/local/etc/dhcpd6.conf dhcpd_ifaces=em0 dhcpd6_ifaces=em0 dhcpd_withumask=022 dhcpd6_withumask=022 dhcpd_chuser_enable=YES dhcpd6_chuser_enable=YES dhcpd_withuser=dhcpd dhcpd6_withuser=dhcpd dhcpd_withgroup=dhcpd dhcpd6_withgroup=dhcpd dhcpd_chroot_enable=YES dhcpd6_chroot_enable=YES dhcpd_devfs_enable=YES dhcpd6_devfs_enable=YES dhcpd_rootdir=/var/db/dhcpd dhcpd6_rootdir=/var/db/dhcpd6 rtadvd_enable=NO rtadvd_interfaces=em0 I've tried configuring a machine with a static configuration, bypassing any issues with rtadvd/dhcpd6 so I'm fairly sure the problem is on the router. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list
Re: Configuration problem with IPv6 router (cannot forward src)
On 08/06/2012 06:59, Matthew Seaman wrote: Probably. The good news is that once you've got it running the IPv6 support in FreeBSD is rock solid and works like a charm. It turns out that PF was being too helpful and trying to NAT for both IPv4 and IPv6 - adding 'inet' to the nat on $ext_if... line fixed it. -- Bruce Cran ___ 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: Configuration problem with IPv6 router (cannot forward src)
From: Bruce Cran br...@cran.org.uk I'm trying to set up a IPv6 router (running -current) on my home network. My ISP gives me a /128 via PPP and I have a /48 allocation, which I use to give em0 and tun0 public addresses in different subnets (tun0 is assigned the address via ppp.linkup). I've added all the IPv6 settings to rc.conf (ipv6_gateway_enable, ipv6_network_interfaces, rtadvd_enable etc.) and I can ping IPv6 sites from the router. The problem is that rtadvd continues advertising the default gateway as tun0's link-local address - and pinging from a machine on the network results in cannot forward src messages on the router (strangely, despite hisaddr being fe80::205:... in ppp.log, the kernel logs the address as fe80:f::205:...). Is there some extra configuration I've likely missed that's needed when using IPv6 via PPP? Please provide the output from these two commands: ifconfig -a netstat -nr on both the router and on an 'inside' machine. (identifying which is which :) There is also a question of 'where' the /48 comes from -- and how traffic to those addresses is being routed from the outside world. ___ 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: buildworld problem
On Sat, 19 May 2012 11:18:37 -0500 CyberLeo Kitsana cyber...@cyberleo.net wrote: On 05/19/2012 03:29 AM, Andriy Babiy wrote: Makefile.inc1, line 160: CPUTYPE global should be set with ?=. ... In make.conf I have CPUTYPE=nocona As it says, you need CPUTYPE?=nocona instead of CPUTYPE=nocona in /etc/make.conf or /etc/src.conf; otherwise the build process chokes while building the 32-bit compatibility stuff, since it cannot override your 64-bit CPU selection with a 32-bit one. You are right. Thank you. ___ 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: buildworld problem
On 05/18/2012 09:17 PM, Andriy Babiy wrote: FreeBSD myhost 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Fri Mar 23 20:00:59 PDT 2012 root@myhost:/usr/obj/usr/src/sys/GENERIC amd64 root#cd /usr/obj root#chflags -R noschg * root#rm -rf * root#make buildworld ... cd /usr/src; MACHINE=i386 MACHINE_ARCH=i386 MACHINE_CPU=i686 mmx sse sse2 LD=ld -m elf_i386_fbsd -Y P,/usr/obj/usr/src/lib32/usr/lib32 AS=as --32 MAKEOBJDIRPREFIX=/usr/obj/lib32 I may be going over my head on this one:-) However to my understanding it seems, it is trying to build 32 bit on a amd 64bit install? ___ 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: buildworld problem
FreeBSD myhost 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Fri Mar 23 20:00:59 PDT 2012 root@myhost:/usr/obj/usr/src/sys/GENERIC amd64 root#cd /usr/obj root#chflags -R noschg * root#rm -rf * root#make buildworld ... cd /usr/src; MACHINE=i386 MACHINE_ARCH=i386 MACHINE_CPU=i686 mmx sse sse2 LD=ld -m elf_i386_fbsd -Y P,/usr/obj/usr/src/lib32/usr/lib32 AS=as --32 MAKEOBJDIRPREFIX=/usr/obj/lib32 I may be going over my head on this one:-) However to my understanding it seems, it is trying to build 32 bit on a amd 64bit install? Since 7.0 I upgraded this machine via buildworld. It was always amd64. As you see in uname output, I upgraded it from 8.X to 9.0 with no problem. Time/date is in sync. I don't see any problems in the system I am running, but I got latest code changes for SSL and wanted to do as usual per instructions. On i386 machine everything worked fine, and I don't suspect the code changes are causing it; there must be something simple I miss. In make.conf I have CPUTYPE=nocona and perl version, and obviously clang related definitions. In the error above I see -DCOMPAT_32 string which might be the case for building 32 compatibility libraries for amd64, but it still doesn't explain what fails and why. Any ideas? Thank you. ___ 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: buildworld problem
On 05/18/2012 09:17 PM, Andriy Babiy wrote:
Makefile.inc1, line 160: CPUTYPE global should be set with ?=
I think the problem is the wrong cpu type define. . I took a
glance at the code in the makefile.inc1 to see what would set that
error off and i found this in the makefile.inc1
if cpu type does not equal target_cputype then throw that error.
.if ${_CPUTYPE} != ${_TARGET_CPUTYPE}
.error CPUTYPE global should be set with ?=.
___
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: buildworld problem
On 5/19/2012 3:11 AM, Edward M wrote: Try 'env -i make buildworld' after cleaning obj. ___ 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: buildworld problem
On 05/19/2012 03:29 AM, Andriy Babiy wrote: Makefile.inc1, line 160: CPUTYPE global should be set with ?=. ... In make.conf I have CPUTYPE=nocona As it says, you need CPUTYPE?=nocona instead of CPUTYPE=nocona in /etc/make.conf or /etc/src.conf; otherwise the build process chokes while building the 32-bit compatibility stuff, since it cannot override your 64-bit CPU selection with a 32-bit one. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net cyber...@cyberleo.net Furry Peace! - http://.fur.com/peace/ ___ 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: buildworld problem
On 05/19/2012 09:18 AM, CyberLeo Kitsana wrote: As it says, you need CPUTYPE?=nocona instead of CPUTYPE=nocona in /etc/make.conf or /etc/src.conf; otherwise the build process chokes while building the 32-bit compatibility stuff, since it cannot override your 64-bit CPU selection with a 32-bit one. Just learned something new:-) had a look in share/examples/etc/make.conf file and i noticed this # (?= allows to buildworld for a different CPUTYPE.) ___ 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: FreeBSD problem reports - bin/167156
On 25/04/2012 22:54, Taras Marusin wrote: Hello! How can I track the solution to this problem? T.Marusin -- Forwarded message -- From:freebsd-gnats-sub...@freebsd.org Date: 2012/4/21 Subject: Re: bin/167156: looping process mksnap_ffs when run in a chroot environment named. CPU 100% To: Taras Marusinmtv.l...@gmail.com Thank you very much for your problem report. It has the internal identification `bin/167156'. The individual assigned to look at your report is: freebsd-bugs. You can access the state of your problem report at any time via this link: http://www.freebsd.org/cgi/query-pr.cgi?pr=167156 First as the submitter you should get emailed copies of any follow ups added to the report. Second the link at the end there will show all responses submitted to the problem report. You can check that page any time you want. ___ 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: Re[4]: Problem with vlans on igb (was: fsck problem FreeBSD 8.3)
Well, you see me glad that this fixes your problems. You might want to see with Jack Vogel who maintains the Intel drivers, if you can track down the issue and perhaps even find a fix for it. Taking the liberty of CCing you Jack. 2012/4/18 Eugen Konkov kes-...@yandex.ru: Hi, Damien. With this configuration works without reboots ifconfig_igb0=-rxcsum -txcsum -lro -tso up ifconfig_igb1=-rxcsum -txcsum -lro -tso up ifconfig_igb2=-rxcsum -txcsum -lro -tso -vlanhwtag up ifconfig_igb3=-rxcsum -txcsum -lro -tso up igb0 has only one vlan igb1 has two vlans igb2 has 16 vlans igb3 has 4 vlans if igb2 has vlanhwtag enabled then server starts to reboot DF Yes, I suggest you try with -vlanhwtag as well. DF If that stops your unwanted reboots, you may want to remove it and see DF if the situation changes. DF 2012/4/12 Коньков Евгений kes-...@yandex.ru: Now i350 is configured as: /etc/rc.conf ## TCP/IP ifconfig_igb0=-rxcsum -txcsum -lro -tso up ifconfig_igb1=-rxcsum -txcsum -lro -tso up ifconfig_igb2=-rxcsum -txcsum -lro -tso up ifconfig_igb3=-rxcsum -txcsum -lro -tso up # ifconfig -m igb1 igb1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=400b8VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO capabilities=505bbRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,LRO,VLAN_HWFILTER,VLAN_HWTSO ether a0:36:9f:00:66:a5 media: Ethernet autoselect (1000baseT full-duplex) status: active supported media: media autoselect media 1000baseT media 1000baseT mediaopt full-duplex media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP #pciconf -lv igb0@pci0:1:0:0: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet Do I need to disable VLAN_HWCSUM, VLAN_HWFILTER,VLAN_HWTSO also? PS. I will try to disable those after the holidays DF Try disabling hardware VLAN tagging like so, I know we had problems a DF few years back with it. DF in /etc/rc.conf : DF ifconfig_igb2= -vlanhwtag -tso -lro up DF 2012/4/11 KES kes-...@yandex.ua: Пересылаемое сообщение 11.04.2012, 13:14, KES kes-...@yandex.ua: 10.04.2012, 08:50, Da Rock freebsd-questi...@herveybayaustralia.com.au: On 04/10/12 05:02, Коньков Евгений wrote: Yes, I have tested. and on this hardware on this OS it works from Fri Feb 24 17:07:48 UTC 2012 but last two days: reboot ~ Mon Apr 9 19:50 reboot ~ Mon Apr 9 18:30 reboot ~ Sun Apr 8 20:55 reboot ~ Sun Apr 8 20:00 reboot ~ Sun Apr 8 19:49 reboot ~ Sun Apr 8 17:43 reboot ~ Sun Apr 8 10:58 reboot ~ Sat Apr 7 21:13 reboot ~ Sat Apr 7 16:37 reboot ~ Sat Apr 7 16:07 I remembered. One thing changed. I add vlans to igb2, but no traffic flow on that devices yet. Perhaps you should test removing the vlans and see if things improve? I have removed vlans, two day server works without reboots Before this I have use: igb0, igb1, igb3 igb0@pci0:1:0:0: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb1@pci0:1:0:1: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb2@pci0:1:0:2: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb3@pci0:1:0:3: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet ifconfig_vlan100=inet 192.168.0.1 netmask 255.255.255.0 vlan 100 vlandev igb2 #nALL ifconfig_vlan101=inet 192.168.1.1 netmask 255.255.255.0 vlan 101 vlandev igb2 #n2 p24 ifconfig_vlan102=inet 192.168.2.1 netmask 255.255.255.0 vlan 102 vlandev igb2 #n1 p23 ifconfig_vlan103=inet 192.168.3.1 netmask 255.255.255.0 vlan 103 vlandev igb2 #n3 p22 ifconfig_vlan104=inet 192.168.4.1 netmask 255.255.255.0 vlan 104 vlandev igb2 #n7,9 p21 ifconfig_vlan105=inet 192.168.5.1 netmask 255.255.255.0 vlan 105 vlandev igb2 #n11 p20 ifconfig_vlan106=inet 192.168.6.1 netmask 255.255.255.0
Re[4]: Problem with vlans on igb (was: fsck problem FreeBSD 8.3)
Hi, Damien. With this configuration works without reboots ifconfig_igb0=-rxcsum -txcsum -lro -tso up ifconfig_igb1=-rxcsum -txcsum -lro -tso up ifconfig_igb2=-rxcsum -txcsum -lro -tso -vlanhwtag up ifconfig_igb3=-rxcsum -txcsum -lro -tso up igb0 has only one vlan igb1 has two vlans igb2 has 16 vlans igb3 has 4 vlans if igb2 has vlanhwtag enabled then server starts to reboot DF Yes, I suggest you try with -vlanhwtag as well. DF If that stops your unwanted reboots, you may want to remove it and see DF if the situation changes. DF 2012/4/12 Коньков Евгений kes-...@yandex.ru: Now i350 is configured as: /etc/rc.conf ## TCP/IP ifconfig_igb0=-rxcsum -txcsum -lro -tso up ifconfig_igb1=-rxcsum -txcsum -lro -tso up ifconfig_igb2=-rxcsum -txcsum -lro -tso up ifconfig_igb3=-rxcsum -txcsum -lro -tso up # ifconfig -m igb1 igb1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=400b8VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO capabilities=505bbRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,LRO,VLAN_HWFILTER,VLAN_HWTSO ether a0:36:9f:00:66:a5 media: Ethernet autoselect (1000baseT full-duplex) status: active supported media: media autoselect media 1000baseT media 1000baseT mediaopt full-duplex media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP #pciconf -lv igb0@pci0:1:0:0: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet Do I need to disable VLAN_HWCSUM, VLAN_HWFILTER,VLAN_HWTSO also? PS. I will try to disable those after the holidays DF Try disabling hardware VLAN tagging like so, I know we had problems a DF few years back with it. DF in /etc/rc.conf : DF ifconfig_igb2= -vlanhwtag -tso -lro up DF 2012/4/11 KES kes-...@yandex.ua: Пересылаемое сообщение 11.04.2012, 13:14, KES kes-...@yandex.ua: 10.04.2012, 08:50, Da Rock freebsd-questi...@herveybayaustralia.com.au: On 04/10/12 05:02, Коньков Евгений wrote: Yes, I have tested. and on this hardware on this OS it works from Fri Feb 24 17:07:48 UTC 2012 but last two days: reboot ~ Mon Apr 9 19:50 reboot ~ Mon Apr 9 18:30 reboot ~ Sun Apr 8 20:55 reboot ~ Sun Apr 8 20:00 reboot ~ Sun Apr 8 19:49 reboot ~ Sun Apr 8 17:43 reboot ~ Sun Apr 8 10:58 reboot ~ Sat Apr 7 21:13 reboot ~ Sat Apr 7 16:37 reboot ~ Sat Apr 7 16:07 I remembered. One thing changed. I add vlans to igb2, but no traffic flow on that devices yet. Perhaps you should test removing the vlans and see if things improve? I have removed vlans, two day server works without reboots Before this I have use: igb0, igb1, igb3 igb0@pci0:1:0:0: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb1@pci0:1:0:1: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb2@pci0:1:0:2: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb3@pci0:1:0:3: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet ifconfig_vlan100=inet 192.168.0.1 netmask 255.255.255.0 vlan 100 vlandev igb2 #nALL ifconfig_vlan101=inet 192.168.1.1 netmask 255.255.255.0 vlan 101 vlandev igb2 #n2 p24 ifconfig_vlan102=inet 192.168.2.1 netmask 255.255.255.0 vlan 102 vlandev igb2 #n1 p23 ifconfig_vlan103=inet 192.168.3.1 netmask 255.255.255.0 vlan 103 vlandev igb2 #n3 p22 ifconfig_vlan104=inet 192.168.4.1 netmask 255.255.255.0 vlan 104 vlandev igb2 #n7,9 p21 ifconfig_vlan105=inet 192.168.5.1 netmask 255.255.255.0 vlan 105 vlandev igb2 #n11 p20 ifconfig_vlan106=inet 192.168.6.1 netmask 255.255.255.0 vlan 106 vlandev igb2 #n13 p19 ifconfig_vlan107=inet 192.168.7.1 netmask 255.255.255.0 vlan 107 vlandev igb2 #n223 p18 ifconfig_vlan108=inet 192.168.8.1 netmask 255.255.255.0 vlan 108 vlandev igb2 #n225 p17 ifconfig_vlan109=inet 192.168.9.1 netmask 255.255.255.0 vlan 109
Re[4]: Problem with vlans on igb (was: fsck problem FreeBSD 8.3)
Здравствуйте, Damien. Вы писали 13 апреля 2012 г., 4:42:31: DF Yes, I suggest you try with -vlanhwtag as well. DF If that stops your unwanted reboots, you may want to remove it and see DF if the situation changes. igb0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=400b8VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO ether a0:36:9f:00:66:a4 media: Ethernet autoselect (1000baseT full-duplex) status: active igb1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=400b8VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO ether a0:36:9f:00:66:a5 media: Ethernet autoselect (1000baseT full-duplex) status: active igb2: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=400b8VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO ether a0:36:9f:00:66:a6 media: Ethernet autoselect (1000baseT full-duplex) status: active igb3: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=400b8VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO ether a0:36:9f:00:66:a7 media: Ethernet autoselect (1000baseT full-duplex) status: active vlan407: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether a0:36:9f:00:66:a4 inet netmask 0xfff8 broadcast media: Ethernet autoselect (1000baseT full-duplex) status: active vlan: 407 parent interface: igb0 vlan408: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether a0:36:9f:00:66:a5 inet x netmask 0xfff8 broadcast xxx media: Ethernet autoselect (1000baseT full-duplex) status: active vlan: 408 parent interface: igb1 vlan492: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether a0:36:9f:00:66:a5 inet netmask 0xfff8 broadcast x media: Ethernet autoselect (1000baseT full-duplex) status: active vlan: 492 parent interface: igb1 vlan70: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether a0:36:9f:00:66:a7 inet netmask 0xfe00 broadcast xx media: Ethernet autoselect (1000baseT full-duplex) status: active vlan: 70 parent interface: igb3 vlan71: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether a0:36:9f:00:66:a7 inet xxx netmask 0xfe00 broadcast xxx media: Ethernet autoselect (1000baseT full-duplex) status: active vlan: 71 parent interface: igb3 vlan72: flags=8002BROADCAST,MULTICAST metric 0 mtu 1500 ether 00:00:00:00:00:00 vlan: 0 parent interface: none vlan73: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether a0:36:9f:00:66:a7 inet x netmask 0xfe00 broadcast x media: Ethernet autoselect (1000baseT full-duplex) status: active vlan: 73 parent interface: igb3 vlan74: flags=8002BROADCAST,MULTICAST metric 0 mtu 1500 ether 00:00:00:00:00:00 vlan: 0 parent interface: none vlan75: flags=8002BROADCAST,MULTICAST metric 0 mtu 1500 ether 00:00:00:00:00:00 vlan: 0 parent interface: none vlan76: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether a0:36:9f:00:66:a7 inet xxx netmask 0xfe00 broadcast xxx media: Ethernet autoselect (1000baseT full-duplex) status: active vlan: 76 parent interface: igb3 vlan100: flags=8803UP,BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: none vlan101: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether a0:36:9f:00:66:a6 inet xx netmask 0xff00 broadcast xxx media: Ethernet autoselect (1000baseT full-duplex) status: active vlan: 101 parent interface: igb2 vlan102: flags=8803UP,BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: none vlan103: flags=8803UP,BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: none vlan104: flags=8803UP,BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: none vlan105: flags=8803UP,BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: none vlan106: flags=8803UP,BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: none vlan107: flags=8803UP,BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: none vlan108:
Re[2]: Problem with vlans on igb (was: fsck problem FreeBSD 8.3)
Now i350 is configured as: /etc/rc.conf ## TCP/IP ifconfig_igb0=-rxcsum -txcsum -lro -tso up ifconfig_igb1=-rxcsum -txcsum -lro -tso up ifconfig_igb2=-rxcsum -txcsum -lro -tso up ifconfig_igb3=-rxcsum -txcsum -lro -tso up # ifconfig -m igb1 igb1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=400b8VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO capabilities=505bbRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,LRO,VLAN_HWFILTER,VLAN_HWTSO ether a0:36:9f:00:66:a5 media: Ethernet autoselect (1000baseT full-duplex) status: active supported media: media autoselect media 1000baseT media 1000baseT mediaopt full-duplex media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP #pciconf -lv igb0@pci0:1:0:0:class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet Do I need to disable VLAN_HWCSUM, VLAN_HWFILTER,VLAN_HWTSO also? PS. I will try to disable those after the holidays DF Try disabling hardware VLAN tagging like so, I know we had problems a DF few years back with it. DF in /etc/rc.conf : DF ifconfig_igb2= -vlanhwtag -tso -lro up DF 2012/4/11 KES kes-...@yandex.ua: Пересылаемое сообщение 11.04.2012, 13:14, KES kes-...@yandex.ua: 10.04.2012, 08:50, Da Rock freebsd-questi...@herveybayaustralia.com.au: On 04/10/12 05:02, Коньков Евгений wrote: Yes, I have tested. and on this hardware on this OS it works from Fri Feb 24 17:07:48 UTC 2012 but last two days: reboot ~ Mon Apr 9 19:50 reboot ~ Mon Apr 9 18:30 reboot ~ Sun Apr 8 20:55 reboot ~ Sun Apr 8 20:00 reboot ~ Sun Apr 8 19:49 reboot ~ Sun Apr 8 17:43 reboot ~ Sun Apr 8 10:58 reboot ~ Sat Apr 7 21:13 reboot ~ Sat Apr 7 16:37 reboot ~ Sat Apr 7 16:07 I remembered. One thing changed. I add vlans to igb2, but no traffic flow on that devices yet. Perhaps you should test removing the vlans and see if things improve? I have removed vlans, two day server works without reboots Before this I have use: igb0, igb1, igb3 igb0@pci0:1:0:0: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb1@pci0:1:0:1: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb2@pci0:1:0:2: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb3@pci0:1:0:3: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet ifconfig_vlan100=inet 192.168.0.1 netmask 255.255.255.0 vlan 100 vlandev igb2 #nALL ifconfig_vlan101=inet 192.168.1.1 netmask 255.255.255.0 vlan 101 vlandev igb2 #n2 p24 ifconfig_vlan102=inet 192.168.2.1 netmask 255.255.255.0 vlan 102 vlandev igb2 #n1 p23 ifconfig_vlan103=inet 192.168.3.1 netmask 255.255.255.0 vlan 103 vlandev igb2 #n3 p22 ifconfig_vlan104=inet 192.168.4.1 netmask 255.255.255.0 vlan 104 vlandev igb2 #n7,9 p21 ifconfig_vlan105=inet 192.168.5.1 netmask 255.255.255.0 vlan 105 vlandev igb2 #n11 p20 ifconfig_vlan106=inet 192.168.6.1 netmask 255.255.255.0 vlan 106 vlandev igb2 #n13 p19 ifconfig_vlan107=inet 192.168.7.1 netmask 255.255.255.0 vlan 107 vlandev igb2 #n223 p18 ifconfig_vlan108=inet 192.168.8.1 netmask 255.255.255.0 vlan 108 vlandev igb2 #n225 p17 ifconfig_vlan109=inet 192.168.9.1 netmask 255.255.255.0 vlan 109 vlandev igb2 #n221 p16 ifconfig_vlan110=inet 192.168.10.1 netmask 255.255.255.0 vlan 110 vlandev igb2 #n229 p15 ifconfig_vlan111=inet 192.168.11.1 netmask 255.255.255.0 vlan 111 vlandev igb2 #n233 p14 ifconfig_vlan112=inet 192.168.12.1 netmask 255.255.255.0 vlan 112 vlandev igb2 #n231 p13 ifconfig_vlan113=inet 192.168.13.1 netmask 255.255.255.0 vlan 113 vlandev igb2 #n237 p12 ifconfig_vlan114=inet 192.168.14.1 netmask 255.255.255.0 vlan 114 vlandev igb2 #n424 p11 ifconfig_vlan115=inet 192.168.15.1 netmask 255.255.255.0 vlan 115 vlandev igb2 # PAP Nothing logged in
Re: Re[2]: Problem with vlans on igb (was: fsck problem FreeBSD 8.3)
Yes, I suggest you try with -vlanhwtag as well. If that stops your unwanted reboots, you may want to remove it and see if the situation changes. 2012/4/12 Коньков Евгений kes-...@yandex.ru: Now i350 is configured as: /etc/rc.conf ## TCP/IP ifconfig_igb0=-rxcsum -txcsum -lro -tso up ifconfig_igb1=-rxcsum -txcsum -lro -tso up ifconfig_igb2=-rxcsum -txcsum -lro -tso up ifconfig_igb3=-rxcsum -txcsum -lro -tso up # ifconfig -m igb1 igb1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=400b8VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO capabilities=505bbRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,LRO,VLAN_HWFILTER,VLAN_HWTSO ether a0:36:9f:00:66:a5 media: Ethernet autoselect (1000baseT full-duplex) status: active supported media: media autoselect media 1000baseT media 1000baseT mediaopt full-duplex media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP #pciconf -lv igb0@pci0:1:0:0: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet Do I need to disable VLAN_HWCSUM, VLAN_HWFILTER,VLAN_HWTSO also? PS. I will try to disable those after the holidays DF Try disabling hardware VLAN tagging like so, I know we had problems a DF few years back with it. DF in /etc/rc.conf : DF ifconfig_igb2= -vlanhwtag -tso -lro up DF 2012/4/11 KES kes-...@yandex.ua: Пересылаемое сообщение 11.04.2012, 13:14, KES kes-...@yandex.ua: 10.04.2012, 08:50, Da Rock freebsd-questi...@herveybayaustralia.com.au: On 04/10/12 05:02, Коньков Евгений wrote: Yes, I have tested. and on this hardware on this OS it works from Fri Feb 24 17:07:48 UTC 2012 but last two days: reboot ~ Mon Apr 9 19:50 reboot ~ Mon Apr 9 18:30 reboot ~ Sun Apr 8 20:55 reboot ~ Sun Apr 8 20:00 reboot ~ Sun Apr 8 19:49 reboot ~ Sun Apr 8 17:43 reboot ~ Sun Apr 8 10:58 reboot ~ Sat Apr 7 21:13 reboot ~ Sat Apr 7 16:37 reboot ~ Sat Apr 7 16:07 I remembered. One thing changed. I add vlans to igb2, but no traffic flow on that devices yet. Perhaps you should test removing the vlans and see if things improve? I have removed vlans, two day server works without reboots Before this I have use: igb0, igb1, igb3 igb0@pci0:1:0:0: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb1@pci0:1:0:1: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb2@pci0:1:0:2: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb3@pci0:1:0:3: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet ifconfig_vlan100=inet 192.168.0.1 netmask 255.255.255.0 vlan 100 vlandev igb2 #nALL ifconfig_vlan101=inet 192.168.1.1 netmask 255.255.255.0 vlan 101 vlandev igb2 #n2 p24 ifconfig_vlan102=inet 192.168.2.1 netmask 255.255.255.0 vlan 102 vlandev igb2 #n1 p23 ifconfig_vlan103=inet 192.168.3.1 netmask 255.255.255.0 vlan 103 vlandev igb2 #n3 p22 ifconfig_vlan104=inet 192.168.4.1 netmask 255.255.255.0 vlan 104 vlandev igb2 #n7,9 p21 ifconfig_vlan105=inet 192.168.5.1 netmask 255.255.255.0 vlan 105 vlandev igb2 #n11 p20 ifconfig_vlan106=inet 192.168.6.1 netmask 255.255.255.0 vlan 106 vlandev igb2 #n13 p19 ifconfig_vlan107=inet 192.168.7.1 netmask 255.255.255.0 vlan 107 vlandev igb2 #n223 p18 ifconfig_vlan108=inet 192.168.8.1 netmask 255.255.255.0 vlan 108 vlandev igb2 #n225 p17 ifconfig_vlan109=inet 192.168.9.1 netmask 255.255.255.0 vlan 109 vlandev igb2 #n221 p16 ifconfig_vlan110=inet 192.168.10.1 netmask 255.255.255.0 vlan 110 vlandev igb2 #n229 p15 ifconfig_vlan111=inet 192.168.11.1 netmask 255.255.255.0 vlan 111 vlandev igb2 #n233 p14 ifconfig_vlan112=inet 192.168.12.1 netmask 255.255.255.0 vlan 112 vlandev igb2 #n231 p13 ifconfig_vlan113=inet 192.168.13.1 netmask 255.255.255.0 vlan 113 vlandev igb2 #n237 p12
Re: fsck problem FreeBSD 8.3
12.04.2012 00:05, Коньков Евгений пишет: Здравствуйте, Eugene. Вы писали 10 апреля 2012 г., 0:39:52: EG 10.04.2012 01:36, Коньков Евгений пишет: Hi. Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST FSCK Apr 9 19:51:58 fsck: Apr 9 19:51:58 fsck: Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. Apr 9 19:51:58 fsck: /dev/ad8s1e: CANNOT SET FS_NEEDSFSCK FLAG Apr 9 20:09:22 kernel: running manually: # fsck -y /dev/ad8s1e ** /dev/ad8s1e (NO WRITE) EG You cannot run fsck on mounted filesystem, unmount it first. Why not? fsck can do its job at background, on mounted FS. It is run in special mode then, you run fsck not that way. So I also can run it on mounted FS. NO WRITE signals you that it will not be able to fix any problem it encounters. in this case (as I have showed) it do not find any errors. And if it finds any error on mounted live file system, that would not mean the error really exists. Do NOT run fsck on mounted file system, period. In any case I have run fsck on this FS when it was dismounted. There is no any errors. So, you need not bother, your file system has been already fixed. I think here is only one problem. problem to 'RUN FAST FSCK' No need to, already. Eugene Grosbein ___ 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: fsck problem FreeBSD 8.3
Nothing logged in /var/log/* or crashes that exist in /var/crash would indicate to me some sort of hardware related problem. Have you tested your hardware lately and know that it is in operational order? ~Paul On Mon, Apr 09, 2012 at 09:36:54PM +0300, ??? ??? wrote: Hi. Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST FSCK Apr 9 19:51:58 fsck: Apr 9 19:51:58 fsck: Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. Apr 9 19:51:58 fsck: /dev/ad8s1e: CANNOT SET FS_NEEDSFSCK FLAG Apr 9 20:09:22 kernel: running manually: # fsck -y /dev/ad8s1e ** /dev/ad8s1e (NO WRITE) ** Last Mounted on /tmp ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 99 files, 10 used, 506477 free (45 frags, 63304 blocks, 0.0% fragmentation) Server reboot two or three time per day # uname -a FreeBSD flux 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #3 r231881: Fri Feb 24 17:07:48 UTC 2012 adm@flux:/usr/obj/usr/src/sys/KES_KERN_v8 amd64 before this it works about month without problems /var/crash - empty, in /var/log/messages there is no any messages before crash. Can any help to fix problem? ___ freebsd-...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org This message may contain confidential or privileged information. If you are not the intended recipient, please advise us immediately and delete this message. See http://www.datapipe.com/legal/email_disclaimer/ for further information on confidentiality and the risks of non-secure electronic communication. If you cannot access these links, please notify us by reply message and we will send the contents to you. ___ 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: fsck problem FreeBSD 8.3
10.04.2012 01:36, Коньков Евгений пишет: Hi. Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST FSCK Apr 9 19:51:58 fsck: Apr 9 19:51:58 fsck: Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. Apr 9 19:51:58 fsck: /dev/ad8s1e: CANNOT SET FS_NEEDSFSCK FLAG Apr 9 20:09:22 kernel: running manually: # fsck -y /dev/ad8s1e ** /dev/ad8s1e (NO WRITE) You cannot run fsck on mounted filesystem, unmount it first. ___ 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: fsck problem FreeBSD 8.3
On 04/10/12 05:02, Коньков Евгений wrote: Yes, I have tested. and on this hardware on this OS it works from Fri Feb 24 17:07:48 UTC 2012 but last two days: reboot ~ Mon Apr 9 19:50 reboot ~ Mon Apr 9 18:30 reboot ~ Sun Apr 8 20:55 reboot ~ Sun Apr 8 20:00 reboot ~ Sun Apr 8 19:49 reboot ~ Sun Apr 8 17:43 reboot ~ Sun Apr 8 10:58 reboot ~ Sat Apr 7 21:13 reboot ~ Sat Apr 7 16:37 reboot ~ Sat Apr 7 16:07 I remembered. One thing changed. I add vlans to igb2, but no traffic flow on that devices yet. Perhaps you should test removing the vlans and see if things improve? Before this I have use: igb0, igb1, igb3 igb0@pci0:1:0:0:class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb1@pci0:1:0:1:class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb2@pci0:1:0:2:class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb3@pci0:1:0:3:class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet ifconfig_vlan100=inet 192.168.0.1 netmask 255.255.255.0 vlan 100 vlandev igb2 #nALL ifconfig_vlan101=inet 192.168.1.1 netmask 255.255.255.0 vlan 101 vlandev igb2 #n2 p24 ifconfig_vlan102=inet 192.168.2.1 netmask 255.255.255.0 vlan 102 vlandev igb2 #n1 p23 ifconfig_vlan103=inet 192.168.3.1 netmask 255.255.255.0 vlan 103 vlandev igb2 #n3 p22 ifconfig_vlan104=inet 192.168.4.1 netmask 255.255.255.0 vlan 104 vlandev igb2 #n7,9 p21 ifconfig_vlan105=inet 192.168.5.1 netmask 255.255.255.0 vlan 105 vlandev igb2 #n11 p20 ifconfig_vlan106=inet 192.168.6.1 netmask 255.255.255.0 vlan 106 vlandev igb2 #n13 p19 ifconfig_vlan107=inet 192.168.7.1 netmask 255.255.255.0 vlan 107 vlandev igb2 #n223 p18 ifconfig_vlan108=inet 192.168.8.1 netmask 255.255.255.0 vlan 108 vlandev igb2 #n225 p17 ifconfig_vlan109=inet 192.168.9.1 netmask 255.255.255.0 vlan 109 vlandev igb2 #n221 p16 ifconfig_vlan110=inet 192.168.10.1 netmask 255.255.255.0 vlan 110 vlandev igb2 #n229 p15 ifconfig_vlan111=inet 192.168.11.1 netmask 255.255.255.0 vlan 111 vlandev igb2 #n233 p14 ifconfig_vlan112=inet 192.168.12.1 netmask 255.255.255.0 vlan 112 vlandev igb2 #n231 p13 ifconfig_vlan113=inet 192.168.13.1 netmask 255.255.255.0 vlan 113 vlandev igb2 #n237 p12 ifconfig_vlan114=inet 192.168.14.1 netmask 255.255.255.0 vlan 114 vlandev igb2 #n424 p11 ifconfig_vlan115=inet 192.168.15.1 netmask 255.255.255.0 vlan 115 vlandev igb2 # PAP Nothing logged in /var/log/* or crashes that exist in /var/crash PAP would indicate to me some sort of hardware related problem. PAP Have you tested your hardware lately and know that it is in operational order? PAP ~Paul PAP On Mon, Apr 09, 2012 at 09:36:54PM +0300, ??? ??? wrote: Hi. Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST FSCK Apr 9 19:51:58 fsck: Apr 9 19:51:58 fsck: Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. Apr 9 19:51:58 fsck: /dev/ad8s1e: CANNOT SET FS_NEEDSFSCK FLAG Apr 9 20:09:22 kernel: running manually: # fsck -y /dev/ad8s1e ** /dev/ad8s1e (NO WRITE) ** Last Mounted on /tmp ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 99 files, 10 used, 506477 free (45 frags, 63304 blocks, 0.0% fragmentation) Server reboot two or three time per day # uname -a FreeBSD flux 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #3 r231881: Fri Feb 24 17:07:48 UTC 2012 adm@flux:/usr/obj/usr/src/sys/KES_KERN_v8 amd64 before this it works about month without problems /var/crash - empty, in /var/log/messages there is no any messages before crash. Can any help to fix problem? ___ 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: Wireless Problem
On Fri, 10 Feb 2012 22:58:22 +0100 zaklinaczcipek128 articulated: Hi, I'm struggling with my wireless cards couple days and I can't figure out what's wrong. Following I'm under FreeBSD 9.0 RELEASE and ever since I've used it I can't connect to any wireless network. I've got Atheros NIC and under every other OS it works fine, even earlier when I were under FreeBSD 7.2 it worked well, but now I got weird issues. I read a lot of it. I followed handbook with no success. I can connect to the network (no difference if it secured or not) i get IP from DHCP but I can't even ping my router. All drivers are loaded, my /etc/wpa_supplicant.conf is all right, I even add a line to the /etc/resolve.conf. I've reinstalled FreeBSD 9.0 and first thing I wanted to check was my wireless and unfortunately, it's the same, not working, same problem. Does the FreeBSD9.0 has any hidden firewall which block my ping ? My router is find. Firstly, I thought I was a bug then I bought another NIC with Realtek 8187 chipset and things look the same. Both cards can scan networks with results, and they seem to work proper so any ideas what can be wrong ? It might have been nice if you had given your router information. Anyway, did you happen to assign a specific IP to your machine in the routers configuration? Usually something like: http//192.168.1.0 or 192.168.1.1 or something like that will get you into the router's configuration screen. I am assuming that the router is assigning you IP and not your PC. You might try shutting down everything, including the router, possibly even zeroing out the router (probably totally unnecessary) and restarting the router then a minute later the rest of your network. See what happens then. Did you check the /etc/hosts file for any errant entries? -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ It is always easier to blame others than to accept responsibility. ___ 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: Wireless Problem
On Fri, Feb 10, 2012 at 1:58 PM, zaklinaczcipek128 zaklinaczcipek...@o2.plwrote: Hi, I'm struggling with my wireless cards couple days and I can't figure out what's wrong. Following I'm under FreeBSD 9.0 RELEASE and ever since I've used it I can't connect to any wireless network. I've got Atheros NIC and under every other OS it works fine, even earlier when I were under FreeBSD 7.2 it worked well, but now I got weird issues. I read a lot of it. I followed handbook with no success. I can connect to the network (no difference if it secured or not) i get IP from DHCP but I can't even ping my router. All drivers are loaded, my /etc/wpa_supplicant.conf is all right, I even add a line to the /etc/resolve.conf. I've reinstalled FreeBSD 9.0 and first thing I wanted to check was my wireless and unfortunately, it's the same, not working, same problem. Does the FreeBSD9.0 has any hidden firewall which block my ping ? My router is find. Firstly, I thought I was a bug then I bought another NIC with Realtek 8187 chipset and things look the same. Both cards can scan networks with results, and they seem to work proper so any ideas what can be wrong ? ___ 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 Hi, I think if you're getting IP from DHCP then it's a routing issue. ie, # netstat -r # route add default 192.168.0.1 -- Waitman Gobble San Jose California USA ___ 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[2]: problem to kill -KILL process
Здравствуйте, Frank.
Вы писали 21 января 2012 г., 11:24:59:
FS On Fri, Jan 20, 2012 at 11:24:21PM +0200, ??? ??? wrote:
Hi
# ps ax|grep rad
45471 ?? TLs 263:35.44 /usr/local/sbin/radiusd
26473 1 S+ 0:00.00 grep rad
flux# date
Fri Jan 20 23:20:28 UTC 2012
flux# kill -KILL 45471
flux# date
Fri Jan 20 23:20:41 UTC 2012
flux# kill -KILL 45471
flux# date
Fri Jan 20 23:20:54 UTC 2012
flux# kill -KILL 45471
top
9 root16- 0K 8K syncer 2 7:12 0.00% syncer
45471 freeradius 20 -20 311M 283M STOP0 3:38 0.00% {radiusd}
49114 root210 10460K 4240K select 0 2:43 0.00% zebra
How to kill process without reboot?
FS Doesn't radius have a script in /usr/local/etc/rc.d?
FS If so use that to stop it rather than KILLing it. E.g:
FS # /usr/local/etc/rc.d/radiusd stop
despite on it uses standart rc.subr, which says:
# stopif ${pidfile}
# rc_pid=$(check_pidfile $pidfile $command)
# else
# rc_pid=$(check_process $command)
# kill $sig_stop $rc_pid
# wait_for_pids $rc_pid
# ($sig_stop defaults to TERM.)
in other words: kill -TERM 45471 in my case
FS or something like that.
man kill
..
Some of the more commonly used signals:
..
9 KILL (non-catchable, non-ignorable kill)
Standart tool do not do its job. It can not stop/kill processes.
--
С уважением,
Коньков mailto:kes-...@yandex.ru
___
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: disk problem(s)
2012-01-14 10:34, Polytropon skrev: On Sat, 14 Jan 2012 10:12:48 +0100, Bernt Hansson wrote: 2012-01-14 09:22, Polytropon skrev: How many subdirectories are there? ls | wc -l 32765 Seems that you have reached LINK_MAX of 32767 (according to /usr/src/sys/sys/syslimits.h). The difference of 2, I assume, is one for . and one for .. hidden entries. Could you, for example, try removing one and then creating a new one (assumption: success), followed by another try to create one (assumption: fail)? That is a nono I'll have to pop in another disk. As the voice from the GPS navigation system tends to say: You have reached your destination. :-) This time it didn't say that, it said You have reached your target destination of 32767. Re-arranging the content of the disk could be an option, It's not an option, the database will get confused and not be able to retrive the articles. but if you're using that disk as some kind of WORM medium (e. g. backup disk), I understand the nono. It's not a backupdisk. And it seems like all the articles is gone now. Oh well some other storage strategy is needed ___ 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: fstab problem
2012-01-14 11:00, per...@pluto.rain.com skrev: Bernt Hanssonb...@bananmonarki.se wrote: This is an old machine (1997), not sure it will boot from usb. I'll check. If it can boot from floppy, Plop will boot it from USB. http://www.plop.at/en/bootmanagers.html Thank you. I'll have a look at it. ___ 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: disk problem(s)
On Sat, 14 Jan 2012 08:45:20 +0100, Bernt Hansson wrote: Hello list! 7.3-RELEASE FreeBSD 7.3-RELEASE #0: Sun Mar 21 06:15:01 UTC 2010 r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 Whenever a program tries to make a directory on this slice it gets this error It's a partition, not a slice. Partitions carry file systems, slices carry partitions. :-) mkdir: spool/text/test: Too many links So the problem seems to be related to directories, not to any files (inodes) per se. This is the slice /dev/ad4s4d202G 37G149G20%/news/spool/text The partition; ad4s4 would be the slice. :-) One can create a file without problems just not directories. Checked sysctl but don't know what to look for. A boot in the right end would be helpful. I would suggest to find out the reason, therefore a short search though the src/ subtree reveals that this message provided by mkdir is: #if defined (EMLINK) ENTRY(EMLINK, EMLINK, Too many links), #endif As the mkdir program uses the mkdir() call, we find man 2 mkdir with the error description for EMLINK: The new directory cannot be created because the parent directory contains too many subdirectories. How many subdirectories are there? Could you, for example, try removing one and then creating a new one (assumption: success), followed by another try to create one (assumption: fail)? Detail: The mkdir() function can be found (for UFS2) in the file /usr/src/sys/gnu/fs/ext2fs/ext2_vnops.c at line (sources of 8.2-STABLE i386 here). If you examine what mkdir() does, you'll see that the too many links is true when LINK_MAX is exceeded. Per /usr/src/sys/gnu/fs/ext2fs/ext2_fs.h we can determine that #define EXT2_LINK_MAX 32000 is defined. Can you check if 32000 is the amount of directories created? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: disk problem(s)
On Sat, 14 Jan 2012 09:22:36 +0100, Polytropon wrote:
The mkdir() function can be found (for UFS2) in the
file /usr/src/sys/gnu/fs/ext2fs/ext2_vnops.c at
line (sources of 8.2-STABLE i386 here). If
you examine what mkdir() does, you'll see that
the too many links is true when LINK_MAX is
exceeded. Per /usr/src/sys/gnu/fs/ext2fs/ext2_fs.h
we can determine that
#define EXT2_LINK_MAX 32000
is defined. Can you check if 32000 is the amount
of directories created?
Shit, what have I done... of course the files
mentioned here do correspond to ext2 (Linux stuff),
and _not_ to UFS2.
The answer is in /usr/src/sys/sys/syslimits.h where
we find the following definition:
#define LINK_MAX 32767 /* max file link count */
Can you check _that_ number against the amount of
directories created?
By the way, in cases like this it's helpful if you
provide the _command_ that you tried and the current
directory from _where_ you've tried it.
Also see /usr/src/sys/ufs/ufs/ufs_vnops.c, lines 1748
and onward, to see the UFS mkdir() system call acting
with
if ((nlink_t)dp-i_nlink = LINK_MAX) {
error = EMLINK;
goto out;
}
when the LINK_MAX limit is reached.
Sorry for the confusion.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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: disk problem(s)
2012-01-14 09:22, Polytropon skrev: How many subdirectories are there? ls | wc -l 32765 Could you, for example, try removing one and then creating a new one (assumption: success), followed by another try to create one (assumption: fail)? That is a nono I'll have to pop in another disk. Detail: The mkdir() function can be found (for UFS2) in the file /usr/src/sys/gnu/fs/ext2fs/ext2_vnops.c at line (sources of 8.2-STABLE i386 here). If you examine what mkdir() does, you'll see that the too many links is true when LINK_MAX is exceeded. Per /usr/src/sys/gnu/fs/ext2fs/ext2_fs.h we can determine that #define EXT2_LINK_MAX 32000 is defined. Can you check if 32000 is the amount of directories created? ___ 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: disk problem(s)
On Sat, 14 Jan 2012 10:12:48 +0100, Bernt Hansson wrote: 2012-01-14 09:22, Polytropon skrev: How many subdirectories are there? ls | wc -l 32765 Seems that you have reached LINK_MAX of 32767 (according to /usr/src/sys/sys/syslimits.h). The difference of 2, I assume, is one for . and one for .. hidden entries. Could you, for example, try removing one and then creating a new one (assumption: success), followed by another try to create one (assumption: fail)? That is a nono I'll have to pop in another disk. As the voice from the GPS navigation system tends to say: You have reached your destination. :-) Re-arranging the content of the disk could be an option, but if you're using that disk as some kind of WORM medium (e. g. backup disk), I understand the nono. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: disk problem(s)
Bernt Hansson writes: 2012-01-14 09:22, Polytropon skrev: How many subdirectories are there? ls | wc -l 32765 ... plus . and .. = 32767. Suggestion: I don't know the content, or the core, but is there a way to use a further level of sub-directories? E.g.: Papa Quebec Romeo becomes P/Papa Q/Quebec R/Romeo Robert Huff ___ 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: fstab problem
Use /dev/ad0s1a instead of /ad0s1a. Frank Am 13.01.2012 11:01, schrieb Bernt Hansson: Hello list! I've moved /etc/fstab to /etc/fstab.org When booting I get prompted with mountroot Ok. I type ufs:ad0s1a The crap boot up. But I can't get the filesystem to become R/W Tried /sbin/mount -o rw /ad0s1a / /sbin/mount -o rw,force /ad0s1a / /sbin/mount -o force /ad0s1a / But /sbin/mount only shows ro. Don't really know what to do, except reinstall and that's a noop. ___ 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 ___ 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: fstab problem
On 13/01/2012 10:01, Bernt Hansson wrote: Hello list! I've moved /etc/fstab to /etc/fstab.org When booting I get prompted with mountroot Ok. I type ufs:ad0s1a The crap boot up. But I can't get the filesystem to become R/W Tried /sbin/mount -o rw /ad0s1a / /sbin/mount -o rw,force /ad0s1a / /sbin/mount -o force /ad0s1a / But /sbin/mount only shows ro. Don't really know what to do, except reinstall and that's a noop. fsck /dev/ad0s1a /sbin/mount -u -o rw /dev/ad0s1a / You should then be able to recover /etc/fstab, fix any problems within it and then on exit, the system should continue with a normal multi-user bootup. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: fstab problem
El día Friday, January 13, 2012 a las 11:01:40AM +0100, Bernt Hansson escribió: Hello list! I've moved /etc/fstab to /etc/fstab.org When booting I get prompted with mountroot Ok. I type ufs:ad0s1a The crap boot up. But I can't get the filesystem to become R/W Tried /sbin/mount -o rw /ad0s1a / /sbin/mount -o rw,force /ad0s1a / /sbin/mount -o force /ad0s1a / But /sbin/mount only shows ro. Don't really know what to do, except reinstall and that's a noop. As a last resort, you could boot an USB livefs, mount the disk to /mnt and do the change back in the root fs; matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ ___ 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: fstab problem
Bernt Hansson b...@bananmonarki.se wrote: This is an old machine (1997), not sure it will boot from usb. I'll check. If it can boot from floppy, Plop will boot it from USB. http://www.plop.at/en/bootmanagers.html ___ 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: acpi problem on dell latitude d830
Ouyang Xueyu free...@suiyuan.de writes: Hello! I`ve just installed freebsd 8.2 i386 stable on a Dell Latitude D830. I`m using gnome 2 with HAL and DBUS successfully. My notebook is not able to go into sleeping mode, it doesn`t work when I use acpiconf -s 3 or acpiconf -s 4. Mode S3 gets it into sleep mode, but it freezes after wake-up with a distorted screen. In mode S4 (suspend-to-disk) it isn`t even able to get into sleeping mode. I want to initiate S4 state by closing the lid. I have a Latitude D630, which is basically the smaller brother of the D830. When it ran FreeBSD I had success in getting the D630 to sleep (s3) and resume. This was a while ago on 8-STABLE with amd64. At least back then, you would need an amd64 install to get this working (something with acpi being better in amd64 then it was in i386). I am not sure that is still the case, but I would not be surprised if it is. However, before you run off and reinstall: (again back then) both the bge and wpi driver (i.e. LAN and WLAN) did not work properly after resuming. This basically made sleeping the laptop useless. I'm not sure this is such good news, but I hope it is informative. If you manage to get it working let me know. Regards, -- - Frank ___ 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: Re[2]: Problem with jail network
Le 30 nov. 2011 à 18:38, Коньков Евгений a écrit : Здравствуйте, bsd. Вы писали 30 ноября 2011 г., 19:29:34: b Le 30 nov. 2011 а 17:17, Damien Fleuriot a йcrit : On 11/30/11 5:05 PM, bsd wrote: Hi, I have been configuring a jail system using the howto provided here : http://www.freebsd.org/doc/handbook/jails-application.html The is now correctly starting, but I can't seem to use the network stack. root@master 16:52:55 ~ - jls JID IP Address Hostname Path 1 xx.216.yy.150 n0.no.no/jail/j/n0 But I can't ping neither outside of the jail, nor inside of It. I am a bit confused because I don't know if I have to configure the IP using an alias on the main Eth interface, or do something else. ifconfig_bce0_alias0=inetxx.216.yy.150/32 This last command seems to have frozen my system. Confirm that the MISSING SPACE between your inet and xxx.216... statements is only a typo and NOT present in your actual rc.conf b This is confirmed. b I have the equivalent of : b ifconfig_bce0_alias0=inet 1.2.3.4/32 in this case I write full netmask: inet 1.2.3.4 netmask 255.255.255.255 It works fine Ok, I'll try that with netmask 255.255.255.255 instead of /32 And use the mentionned parameters with raw socket. Thx -- С уважением, Коньков mailto:kes-...@yandex.ru –– - Grégory Bernard Director - --- www.osnet.eu --- -- Your provider of OpenSource appliances -- –– OSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetO ___ 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: Re[2]: Problem with jail network
On Wed, 30 Nov 2011 20:19:56 +0100, bsd wrote: Le 30 nov. 2011 à 18:38, Коньков Евгений a écrit : Здравствуйте, bsd. Вы писали 30 ноября 2011 г., 19:29:34: b Le 30 nov. 2011 а 17:17, Damien Fleuriot a йcrit : On 11/30/11 5:05 PM, bsd wrote: Hi, I have been configuring a jail system using the howto provided here : http://www.freebsd.org/doc/handbook/jails-application.html The is now correctly starting, but I can't seem to use the network stack. root@master 16:52:55 ~ - jls JID IP Address Hostname Path 1 xx.216.yy.150 n0.no.no/jail/j/n0 But I can't ping neither outside of the jail, nor inside of It. I am a bit confused because I don't know if I have to configure the IP using an alias on the main Eth interface, or do something else. ifconfig_bce0_alias0=inetxx.216.yy.150/32 This last command seems to have frozen my system. Confirm that the MISSING SPACE between your inet and xxx.216... statements is only a typo and NOT present in your actual rc.conf b This is confirmed. b I have the equivalent of : b ifconfig_bce0_alias0=inet 1.2.3.4/32 in this case I write full netmask: inet 1.2.3.4 netmask 255.255.255.255 It works fine Ok, I'll try that with netmask 255.255.255.255 instead of /32 The hex notation should also be valid: ifconfig_bce0_alias0=inet 1.2.3.4 netmask 0xff00 -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: Re[2]: Problem with jail network
On 30 Nov 2011, at 20:28, Polytropon free...@edvax.de wrote: On Wed, 30 Nov 2011 20:19:56 +0100, bsd wrote: Le 30 nov. 2011 à 18:38, Коньков Евгений a écrit : Здравствуйте, bsd. Вы писали 30 ноября 2011 г., 19:29:34: b Le 30 nov. 2011 а 17:17, Damien Fleuriot a йcrit : On 11/30/11 5:05 PM, bsd wrote: Hi, I have been configuring a jail system using the howto provided here : http://www.freebsd.org/doc/handbook/jails-application.html The is now correctly starting, but I can't seem to use the network stack. root@master 16:52:55 ~ - jls JID IP Address Hostname Path 1 xx.216.yy.150 n0.no.no/jail/j/n0 But I can't ping neither outside of the jail, nor inside of It. I am a bit confused because I don't know if I have to configure the IP using an alias on the main Eth interface, or do something else. ifconfig_bce0_alias0=inetxx.216.yy.150/32 This last command seems to have frozen my system. Confirm that the MISSING SPACE between your inet and xxx.216... statements is only a typo and NOT present in your actual rc.conf b This is confirmed. b I have the equivalent of : b ifconfig_bce0_alias0=inet 1.2.3.4/32 in this case I write full netmask: inet 1.2.3.4 netmask 255.255.255.255 It works fine Ok, I'll try that with netmask 255.255.255.255 instead of /32 The hex notation should also be valid: ifconfig_bce0_alias0=inet 1.2.3.4 netmask 0xff00 Careful you've given him /24 instead of the /32 he seems to be using. ___ 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: network problem on 8.2 stable
On Fri, 18 Nov 2011, Xihong Yin wrote: I set the adapter up. Here is the output of 'dhclient em0' DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPACK from 192.168.3.1 bound to 192.168.3.41 -- renewal in 1800 seconds. 'ifconfig em0' output is em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=219bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC ether 00:26:b9:9d:30:dc inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 media: Ethernet autoselect (100baseTX full-duplex) status: active 'netstat -r' show there is no default route Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire 0.0.0.0link#1 U 00em0 localhost link#14UH 0 28lo0 But I can set the adapter manually by $ifconfig em0 inet 192.168.3.41/24 and it works. The question is why dhclient can't get the ip address even a lease is obtained. New to me. Does the machine have any unusual settings, like a non-default securelevel? ___ 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: network problem on 8.2 stable
I set the adapter up. Here is the output of 'dhclient em0' DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPACK from 192.168.3.1 bound to 192.168.3.41 -- renewal in 1800 seconds. 'ifconfig em0' output is em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=219bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC ether 00:26:b9:9d:30:dc inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 media: Ethernet autoselect (100baseTX full-duplex) status: active 'netstat -r' show there is no default route Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire 0.0.0.0link#1 U 00em0 localhost link#14UH 0 28lo0 But I can set the adapter manually by $ifconfig em0 inet 192.168.3.41/24 and it works. The question is why dhclient can't get the ip address even a lease is obtained. Thanks, On Thu, 17 Nov 2011, Warren Block wrote: On Thu, 17 Nov 2011, Xihong Yin wrote: Hi, I upgraded from 8.0 stable to 8.2 stable today. Now I can't connect to the network through the network adapter. I've set DCHP and SYNCDHCP in /etc/rc.conf and it worked in 8.0. It seems the dhclient problem. The ip address can't be obtained. When I run 'dhclient em0' manually, it shows that an ip address is leased. But actually it is not. The 'ifconfig em0' always shows an address of 0.0.0.0 with active status. $dhclient em0 DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPACK from 192.168.3.1 bound to 192.168.3.39 -- renewal in 43200 seconds But $ifconfig em0 em0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 options=389bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC ether 6c:62:6d:03:16:31 inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (10baseT/UTP half-duplex) status: active Any help would be appreciated. The interface is down: no UP in the flags. What happens if you just do it manually: ifconfig em0 up ___ 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 ___ 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: network problem on 8.2 stable
New to me. Does the machine have any unusual settings, like a non-default securelevel? No. There are no unusual security settings. On Fri, 18 Nov 2011, Warren Block wrote: On Fri, 18 Nov 2011, Xihong Yin wrote: I set the adapter up. Here is the output of 'dhclient em0' DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPACK from 192.168.3.1 bound to 192.168.3.41 -- renewal in 1800 seconds. 'ifconfig em0' output is em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=219bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC ether 00:26:b9:9d:30:dc inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 media: Ethernet autoselect (100baseTX full-duplex) status: active 'netstat -r' show there is no default route Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire 0.0.0.0link#1 U 00em0 localhost link#14UH 0 28lo0 But I can set the adapter manually by $ifconfig em0 inet 192.168.3.41/24 and it works. The question is why dhclient can't get the ip address even a lease is obtained. New to me. Does the machine have any unusual settings, like a non-default securelevel? ___ 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: network problem on 8.2 stable
On 11/17/11 17:56, Xihong Yin wrote: The ip address can't be obtained. Have you tried rebooting FreeBSD and letting it obtain the IP itself? On some OSes that has actually worked. ___ 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: network problem on 8.2 stable
I did reboot. It is the same thing. On Thu, 17 Nov 2011, Edward Martinez wrote: On 11/17/11 17:56, Xihong Yin wrote: The ip address can't be obtained. Have you tried rebooting FreeBSD and letting it obtain the IP itself? On some OSes that has actually worked. ___ 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: network problem on 8.2 stable
On 11/17/11 18:41, Xihong Yin wrote: I did reboot. It is the same thing. On Thu, 17 Nov 2011, Edward Martinez wrote: On 11/17/11 17:56, Xihong Yin wrote: The ip address can't be obtained. Have you tried rebooting FreeBSD and letting it obtain the IP itself? On some OSes that has actually worked. Did you try configure the nic with sysinstall? I think FreeBSD 8.2 has a updated em driver. You may need to download the newest FreeBSD em driver from intel. http://downloadcenter.intel.com/Detail_Desc.aspx?agr=YDwnldID=17509keyword=%22em%22DownloadType=DriversOSFullname=FreeBSD*lang=eng ___ 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: network problem on 8.2 stable
I think the driver that comes with 8.2 stable just works fine. When I manually run dhclient em0, it says ip address obtained. but ifconfig em0 shows ip address of 0.0.0.0. And there is no default route in the 'netstat -r' output. On Thu, 17 Nov 2011, Edward Martinez wrote: On 11/17/11 18:41, Xihong Yin wrote: I did reboot. It is the same thing. On Thu, 17 Nov 2011, Edward Martinez wrote: On 11/17/11 17:56, Xihong Yin wrote: The ip address can't be obtained. Have you tried rebooting FreeBSD and letting it obtain the IP itself? On some OSes that has actually worked. Did you try configure the nic with sysinstall? I think FreeBSD 8.2 has a updated em driver. You may need to download the newest FreeBSD em driver from intel. http://downloadcenter.intel.com/Detail_Desc.aspx?agr=YDwnldID=17509keyword=%22em%22DownloadType=DriversOSFullname=FreeBSD*lang=eng ___ 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: network problem on 8.2 stable
On Thu, 17 Nov 2011, Xihong Yin wrote: Hi, I upgraded from 8.0 stable to 8.2 stable today. Now I can't connect to the network through the network adapter. I've set DCHP and SYNCDHCP in /etc/rc.conf and it worked in 8.0. It seems the dhclient problem. The ip address can't be obtained. When I run 'dhclient em0' manually, it shows that an ip address is leased. But actually it is not. The 'ifconfig em0' always shows an address of 0.0.0.0 with active status. $dhclient em0 DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPACK from 192.168.3.1 bound to 192.168.3.39 -- renewal in 43200 seconds But $ifconfig em0 em0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 options=389bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC ether 6c:62:6d:03:16:31 inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (10baseT/UTP half-duplex) status: active Any help would be appreciated. The interface is down: no UP in the flags. What happens if you just do it manually: ifconfig em0 up ___ 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: Urgent!. Problem with / etc / rc.conf
On 06/11/2011 04:10, Zantgo wrote: Without wanting to erase all contents of / etc / rc.conf, by running echo slim_enable = YES / etc / rc.conf. Please help!. You could have used the following: echo slim_enable = YES /etc/rc.conf The appends the line instead of replacing the existing contents. -- Bruce Cran ___ 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: Urgent!. Problem with / etc / rc.conf
Le Sun, 6 Nov 2011 01:52:36 -0300, Zantgo zan...@gmail.com a écrit : Hello, Two other things, use rather than to append to the file (better yet, learn vi, it's much safer), and always backup any changes from default you make to config files. I keep them all on pastebin.com for convenience, but you can keep them anywhere, even scribbled on a postit note stuck to the front of the server in question (what I used to do). Rob I gave up, and now reinstall everything again :( You really don't need to reinstall. All the default rc.conf settings are in /etc/default/rc.conf You may also use sysinstall(8), Configure|Do post-install configuration (networking) and Keymap. It will update rc.conf Regards. ___ 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: Urgent!. Problem with / etc / rc.conf
From: Zantgo zan...@gmail.com To: Robert Simmons rsimmo...@gmail.com Cc: freebsd-questions@FreeBSD.org freebsd-questions@freebsd.org Sent: Sunday, November 6, 2011 12:52 AM Subject: Re: Urgent!. Problem with / etc / rc.conf El 06-11-2011, a las 1:29, Robert Simmons rsimmo...@gmail.com escribió: On Sun, Nov 6, 2011 at 12:10 AM, Zantgo zan...@gmail.com wrote: Without wanting to erase all contents of / etc / rc.conf, by running echo slim_enable = YES / etc / rc.conf. Please help!. Well, the absolute basics would be: hostname=YourHostNameHere ifconfig_NameOfNicCardDeviceHere=inet IPADDRESS netmask NETMASK defaultrouter=IPOfGateway/Router You may also have had: sshd_enable=YES You can also look at dmesg -a and get a grasp over what other services you had started. Two other things, use rather than to append to the file (better yet, learn vi, it's much safer), and always backup any changes from default you make to config files. I keep them all on pastebin.com for convenience, but you can keep them anywhere, even scribbled on a postit note stuck to the front of the server in question (what I used to do). Rob I gave up, and now reinstall everything again :( ___ 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 Wow, to reinstall everything is like throwing the baby out with the bath water. Rather drastic. There are some simple steps you could have taken to get things back to normal but without knowing what you had in your original rc.conf file that's probably oversimplifying things. I keep a little script in my /root/bin folder to backup my config files periodically to another server. This is something you should look into. We all make mistakes and when we do, a backup copy can make the difference between oh wow and oh f***. ___ 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
