strange network problem with multiple interfaces
hi, I just installed stock FreeBSD 9.0 on a PowerEdge server with two network cards: bce0 is directly connected to isp's gateway bce1~3 are connected to the inside port of a router configured as 192.168.1.0/24 network with 192.168.1.1 as gateway If the ENTIRE content of /etc/rc.conf is: hostname=test.com ifconfig_bce0=inet 1.2.3.4 netmask 255.255.255.0 defaultrouter=1.2.3.1 #the above numbers are supplied by isp ifconfig_bce1=inet 192.168.1.4 netmask 255.255.255.0 static_routes=interface1 route_interface1=-net 192.168.1.0/24 192.168.1.1 then the machine can do all public network activities without problem, but doesn't appear to be able to connect to the router at all. In fact, if I do: tcpdmp -l -i eth1 host 192.168.1.1 and then do telnet 192.168.1.1 443, there are two wierd results: 1. the tcpdump catches nothing 2. the telnet window got the following result: Trying 192.168.1.1... telnet: connect to address 192.168.1.1: Operation not permitted telnet: Unable to connect to remote host routing table is the following: #netstat -rn DestinationGatewayFlagsRefs Use Netif Expire default1.2.3.1 UGS 0 193 bce0 1.2.3.0/24 link#1 U 00 bce0 1.2.3.4 link#1 UHS 00lo0 127.0.0.1 link#5UH 00lo0 192.168.1.0/24 192.168.1.1UGS 01 bce1 192.168.1.4 link#2 UHS 01lo0 No firewall is configured. Also unless there is a known relevant bug of the stock 9.0, we want to stick to this version for the moment due to some other concern. Could someone help to enlighten what I did wrong? 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
Problem upgrading to 9.1-Release
I have upgraded my development system to 9.1 without any problems. This system maintains kernel source and I build a new kernel with a couple extra options there. The other systems mount /usr/src and /usr/obj from it and do the install. The first one to be upgraded had no problem with make installkernel. Rebooted and ran mergemaster -p just fine. However make installworld dies within a couple seconds with the following error: install -o root -g wheel -m 444 libc_pic.a /usr/lib gencat be_BY.UTF-8.cat /usr/src/lib/libc/nls/be_BY.UTF-8.msg gencat: No such file or directory *** [be_BY.UTF-8.cat] Error code 1 /usr/bin/gencat exists. However, ktrace of the make shows: 3347 make CALL execve(0xbfbfd1c8,0x28c35f14,0x28421180) 3347 make NAMI /usr/obj/usr/src/tmp/legacy/usr/sbin/gencat 3347 make RET execve -1 errno 2 No such file or directory 3347 make CALL execve(0xbfbfd1c8,0x28c35f14,0x28421180) 3347 make NAMI /usr/obj/usr/src/tmp/legacy/usr/bin/gencat 3347 make RET execve -1 errno 2 No such file or directory 3347 make CALL execve(0xbfbfd1c8,0x28c35f14,0x28421180) 3347 make NAMI /usr/obj/usr/src/tmp/legacy/usr/games/gencat 3347 make RET execve -1 errno 2 No such file or directory 3347 make CALL execve(0xbfbfd1c8,0x28c35f14,0x28421180) 3347 make NAMI /usr/obj/usr/src/tmp/usr/sbin/gencat 3347 make RET execve -1 errno 2 No such file or directory 3347 make CALL execve(0xbfbfd1c8,0x28c35f14,0x28421180) 3347 make NAMI /usr/obj/usr/src/tmp/usr/bin/gencat 3347 make RET execve -1 errno 2 No such file or directory 3347 make CALL execve(0xbfbfd1c8,0x28c35f14,0x28421180) 3347 make NAMI /usr/obj/usr/src/tmp/usr/games/gencat 3347 make RET execve -1 errno 2 No such file or directory 3347 make CALL execve(0xbfbfd1c8,0x28c35f14,0x28421180) 3347 make NAMI /tmp/install.CuIzLuBX/gencat 3347 make RET execve -1 errno 2 No such file or directory 3347 make CALL write(0x2,0x28c48c00,0x6) 3347 make GIO fd 2 wrote 6 bytes gencat Obviously its not in any of those places. How can I fix this? ___ 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: problem after installkernel going from 9.0 to CURRENT
On 12/30/2012 7:11 PM, Robert Huff wrote: It indicates that the / partition cannot be mounted to continue booting. Maybe you can interrupt at the boot loader and examine the mount source for /, or manually set it to be ada0p1? I'll try that. OK - I'm at the part of loader2(?) where it shows: OK and wants something of the form disk partitionpath to bootable kernel However, the sample format for the partition is 0:ad(0,a) How do I specify a GPT partition? 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
problem after installkernel going from 9.0 to CURRENT
Situation: One of my boxes failed, and for various reasons it became easier to just scrub and rebuild it. 1) Using BSDinstall, I created the first disk: ada0p1 freebsd-boot128k ada0p2 freebsd-swap4g ada0p3 freebsd-ufs 25g 2) Installed off the CD, got it up and running, everything was good. 3) Like it's predecessor, this wants to run CURRENT. Used csup (tag=.) to update the source tree as of midnight last night. 4) Built world - OK. Build kernel - OK. Ran mergemaster - OK. Installed kernel - OK. 5) On rebooting, the loader(??) claims to not be able to find a bootable partition - i.e. I get a screen that ends in mountpoint . Providing the presumptive value by hand returns error 19. 6) Boot using installation CD and use gpart show to double check device names and partitions; everything looks good. 7) Try normal booting again, no go. This is my first time installing to a GPT partitioned system, and I have (obviously) failed to grok something. I checked src/UPDATING and found nothing which covered this. What is it, and how do I fix it? Respectfully, 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: problem after installkernel going from 9.0 to CURRENT
On Sun, 30 Dec 2012 17:26:40 -0500, Robert Huff wrote: Used csup (tag=.) to update the source tree as of midnight last night. This seems to be discouraged today. Instead svn should be used. 5) On rebooting, the loader(??) claims to not be able to find a bootable partition - i.e. I get a screen that ends in mountpoint . Are you sure this isn't the mountroot prompt? It indicates that the / partition cannot be mounted to continue booting. Maybe you can interrupt at the boot loader and examine the mount source for /, or manually set it to be ada0p1? Providing the presumptive value by hand returns error 19. No root partition, probably. :-) This is my first time installing to a GPT partitioned system, and I have (obviously) failed to grok something. I checked src/UPDATING and found nothing which covered this. That's why _I_ prefer old-fashioned MBR partitioning with sysinstall which has never failed me. :-) -- 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: problem after installkernel going from 9.0 to CURRENT
On 12/30/2012 6:24 PM, Polytropon wrote: Used csup (tag=.) to update the source tree as of midnight last night. This seems to be discouraged today. Instead svn should be used. I'm using this for ports, will convert for source ... probably in the next round after I deal with this. 5) On rebooting, the loader(??) claims to not be able to find a bootable partition - i.e. I get a screen that ends in mountpoint . Are you sure this isn't the mountroot prompt? Right you are; sorry, typing from memory on a different system. It indicates that the / partition cannot be mounted to continue booting. Maybe you can interrupt at the boot loader and examine the mount source for /, or manually set it to be ada0p1? I'll try that. Providing the presumptive value by hand returns error 19. No root partition, probably. :-) Duh. :-) That's why _I_ prefer old-fashioned MBR partitioning with sysinstall which has never failed me. :-) There's something to be said for that. On the other hand, GPT is the rising tide and one has to learn to swim sometimes. 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: portmaster + unknown dependency problem
On 20.11.2012 20:47, Laszlo Nagy wrote: I have a 8.2-STABLE system. Last port upgrade was about a year ago. (I know, this is bad.) I was trying to update all ports, by following the UPDATING file. As it turned out, some ports has been deprecated/deleted. I have a problem in particular with the py-bittornado-core port. I do not need it. So I have deleted it: # pkg_info | grep bittornado # Clearly, it is not installed. However, when I write in this command: # portmaster -a Then I get this error: === The net-p2p/py-bittornado-core port has been deleted: Has expired: Depends on the deprecated wx 2.4 === Aborting update Well, here is the question: why does it want to build a port that does not even exist in the ports tree? It was really deleted, there is no such thing as /usr/ports/net-p2p/py-bittornado-core . I have also tried to do this: # portmaster -a -x py-bittornado-core but it has exactly the same problem. Is this a stale dependency to a nonexistent port? How can I overcome this problem? Thanks, Laszlo ___ 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 make pkg_info | grep *bittornado* When it found this package, you can think about to delete it. When you have delete it or doesnt found it, make a portmaster --check-depends to solve depends. ___ 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: shell script problem
In freebsd-questions Digest, Vol 447, Issue 1, Message: 13 On Sun, 23 Dec 2012 18:48:12 +0100 Dh?nin Jean-Jacques dhe...@gmail.com 2012/12/23 Polytropon free...@edvax.de #!/bin/sh cat foo.txt | while read LINE1 do cat bar.txt | while read LINE2 do if [ $LINE1 = $LINE2 ]; then sw=1 echo Current value of sw is : $sw * ps -l | grep $$ * # see subshell here Yes indeed. break fi done * echo Process: $$* # And the parent Yep. echo Value of sw is : $sw if [ $sw = 0 ]; then echo DO SOMETHING! fi sw=0 done I suggest : -%- #!/bin/sh cat foo.txt | while read LINE1 do echo 'One' $$tmp cat bar.txt |while read LINE2 do if [ $LINE1 = $LINE2 ]; then echo 'ok' $$tmp break fi done if [ `cat $$tmp` = One ]; then echo One ! fi if [ `cat $$tmp` = ok ]; then echo ok ! fi done Or, to avoid subshell(s) created in pipeline(s), and subsequent loss of variables set in the subshell(s) to their parents, rather than using: cat foo.txt | while read LINE1 [..] cat bar.txt | while read LINE2 [..] done [..] done you can use: while read LINE1 [..] while read LINE2 [..] done bar.txt [..] done foo.txt 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
shell script problem
Hi all Please take a look at the script below wich I've wrote : 1- cat /foo/bar.txt | while read $LINE12- do3- cat /foo/bar/foo/bar.txt | while read $LINE24- do 5- if [ $LINE1 = $LINE2 ]; then6- sw=17- echo Current value of sw is : $sw8- break9- fi10- done11- echo Value of sw is : $sw12- if [ $sw = 0 ]; then13- DO SOMETHING14- fi15- sw=016- done You probebly guessed what I want to do. But the problem is that when the value of sw sets to 1 (in the first if statement) and the loop breaks , the value of sw is not '1' anymore in echo Value of sw is : $sw !!! Thanks in advance ... ___ 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: shell script problem
On Sun, 23 Dec 2012 01:05:35 -0800 (PST), Jack Mc Lauren wrote: Hi all Please take a look at the script below wich I've wrote : 1- cat /foo/bar.txt | while read $LINE12- do3- cat /foo/bar/foo/bar.txt | while read $LINE24- do 5- if [ $LINE1 = $LINE2 ]; then6- sw=17- echo Current value of sw is : $sw8- break9- fi10- done11- echo Value of sw is : $sw12- if [ $sw = 0 ]; then13- DO SOMETHING14- fi15- sw=016- done This is totally distorted! Allow me to re-arrange it. cat /foo/bar.txt | while read $LINE1 do cat /foo/bar/foo/bar.txt | while read $LINE2 do if [ $LINE1 = $LINE2 ]; then sw=1 echo Current value of sw is : $sw break fi done echo Value of sw is : $sw if [ $sw = 0 ]; then DO SOMETHING fi sw=0 done First, the lines with read have to be: cat /foo/bar.txt | while read $LINE1 cat /foo/bar/foo/bar.txt | while read $LINE2 Reason: $LINE1 and $LINE2 will be evaluated here, they are empty string, causing read to throw an error. You probebly guessed what I want to do. But the problem is that when the value of sw sets to 1 (in the first if statement) and the loop breaks , the value of sw is not '1' anymore in echo Value of sw is : $sw !!! Thanks in advance ... For testing, I've replaced the $sw=0 line with an echo command. I've created two files foo.txt and bar.txt for test, both have one line in common (3rd line in my example data). If I run the script, I get this output: Value of sw is :- after 1st line (uninitialized) Value of sw is : 0 - after 2nd line DO SOMETHING! Current value of sw is : 1 - after 3nd line (common entry) Value of sw is : 0 - after 4th line DO SOMETHING! Value of sw is : 0 - after 5th line DO SOMETHING! It seems that the condition $LINE1=$LINE2 properly triggers the current value echo command, while all non-common lines trigger the DO SOMETHING action. If you indended something else, please elaborate. -- 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: shell script problem
On Sun, 23 Dec 2012 10:34:34 +0100, Polytropon wrote: First, the lines with read have to be: cat /foo/bar.txt | while read $LINE1 cat /foo/bar/foo/bar.txt | while read $LINE2 Reason: $LINE1 and $LINE2 will be evaluated here, they are empty string, causing read to throw an error. Excuse me - I made a mistake! Of course those two lines have to be: cat /foo/bar.txt | while read LINE1 and cat /foo/bar/foo/bar.txt | while read LINE2 The $ infront of the variable names have to be removed. The variable _name_, not its content, has to be provided to read as a parameter. The script so far: #!/bin/sh cat foo.txt | while read LINE1 do cat bar.txt | while read LINE2 do if [ $LINE1 = $LINE2 ]; then sw=1 echo Current value of sw is : $sw break fi done echo Value of sw is : $sw if [ $sw = 0 ]; then echo DO SOMETHING! fi sw=0 done -- 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: shell script problem
On 23/12/2012 09:43, Polytropon wrote: On Sun, 23 Dec 2012 10:34:34 +0100, Polytropon wrote: First, the lines with read have to be: cat /foo/bar.txt | while read $LINE1 cat /foo/bar/foo/bar.txt | while read $LINE2 Reason: $LINE1 and $LINE2 will be evaluated here, they are empty string, causing read to throw an error. Excuse me - I made a mistake! Of course those two lines have to be: cat /foo/bar.txt | while read LINE1 and cat /foo/bar/foo/bar.txt | while read LINE2 The $ infront of the variable names have to be removed. The variable _name_, not its content, has to be provided to read as a parameter. The script so far: #!/bin/sh cat foo.txt | while read LINE1 do cat bar.txt | while read LINE2 do if [ $LINE1 = $LINE2 ]; then sw=1 echo Current value of sw is : $sw break fi done echo Value of sw is : $sw if [ $sw = 0 ]; then echo DO SOMETHING! fi sw=0 done Hmmm I'd just like to draw your attention to the comm(1) program, which lets you find lines common to two files, or only in one or other of a pair of inputs, very easily. The only slight gotcha is that the input files have to be sorted. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: shell script problem
On Sun, 23 Dec 2012 09:57:02 + Matthew Seaman matt...@freebsd.org wrote: Hmmm I'd just like to draw your attention to the comm(1) program, which lets you find lines common to two files, or only in one or other of a pair of inputs, very easily. The only slight gotcha is that the input files have to be sorted. For which purpose the sort program is most useful. -- Steve O'Hara-Smith st...@sohara.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: shell script problem
2012/12/23 Polytropon free...@edvax.de On Sun, 23 Dec 2012 10:34:34 +0100, Polytropon wrote: First, the lines with read have to be: cat /foo/bar.txt | while read $LINE1 cat /foo/bar/foo/bar.txt | while read $LINE2 Reason: $LINE1 and $LINE2 will be evaluated here, they are empty string, causing read to throw an error. Excuse me - I made a mistake! Of course those two lines have to be: cat /foo/bar.txt | while read LINE1 and cat /foo/bar/foo/bar.txt | while read LINE2 The $ infront of the variable names have to be removed. The variable _name_, not its content, has to be provided to read as a parameter. The script so far: #!/bin/sh cat foo.txt | while read LINE1 * echo Pid Process: $$* do cat bar.txt | while read LINE2 do if [ $LINE1 = $LINE2 ]; then sw=1 echo Current value of sw is : $sw *ps -ax |grep bar * break fi done echo Value of sw is : $sw if [ $sw = 0 ]; then echo DO SOMETHING! fi sw=0 done Has you can see, pipe make a subshell and sw is lost. Hope this help - (° Dhénin Jean-Jacques / ) 48, rue de la Justice 78300 Poissy ^^ dhe...@gmail.com - ___ 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: shell script problem
2012/12/23 Polytropon free...@edvax.de #!/bin/sh cat foo.txt | while read LINE1 do cat bar.txt | while read LINE2 do if [ $LINE1 = $LINE2 ]; then sw=1 echo Current value of sw is : $sw * ps -l | grep $$ * # see subshell here break fi done * echo Process: $$* # And the parent echo Value of sw is : $sw if [ $sw = 0 ]; then echo DO SOMETHING! fi sw=0 done I suggest : -%- #!/bin/sh cat foo.txt | while read LINE1 do echo 'One' $$tmp cat bar.txt |while read LINE2 do if [ $LINE1 = $LINE2 ]; then echo 'ok' $$tmp break fi done if [ `cat $$tmp` = One ]; then echo One ! fi if [ `cat $$tmp` = ok ]; then echo ok ! fi done Best regards - (° Dhénin Jean-Jacques / ) 48, rue de la Justice 78300 Poissy ^^ dhe...@gmail.com - ___ 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
Radeon HD 2400 PRO, DRI setup problem
Hi all, I here reproduce the mail I sent to freebsd-x11 for which I received no reply. I hope I have more luck in questions@ I'm having quite a few problems setting DRI up on my system. I'm running 9.0-RELEASE on amd64 using GENERIC kernel. I recompiled the radeon kernel module with WITHOUT_NOUVEAU=YES just to see if I had more luck. This is some information about my system: pciconf -lv: vgapci0@pci0:4:0:0: class=0x03 card=0x10411462 chip=0x94c31002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'RV610 video device [Radeon HD 2400 PRO]' class = display subclass = VGA Using GENERIC kernel for 9.0-RELEASE on amd64. radeon kernel driver compiled with WITHOUT_NOUVEAU. /usr/ports/graphics/dri properly configured and installed. I followed instructions at http://dri.freedesktop.org/wiki/DriTroubleshooting, but I found that dmesg | grep agp doesn't return anything so I suppose this is a bad sign. I know agp subsystem has been in the default kernel for a while. I can also load the radeon module and I get the /dev/dri/card0 device node. Using the radeon driver for Xorg results in a system hang after a blank screen and the monitor going to sleep. Only if I set DRI to false and I _do not_ load the radeon driver I can get my X server running though it is quite slow. The output of glxinfo | grep OpenGL is: OpenGL vendor string: Mesa Project OpenGL renderer string: Software Rasterizer OpenGL version string: 2.1 Mesa 7.6.1 OpenGL shading language version string: 1.20 OpenGL extensions: So basically I don't know how to get the card working. It works in Linux with the Xorg's radeon driver so I suppose I have some misconfiguration around but I can not figure it out. Any help would be appreciated. Thanks in advance. PS: Please, CC me as I'm not subscribed to the list. ___ 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
portmaster + unknown dependency problem
I have a 8.2-STABLE system. Last port upgrade was about a year ago. (I know, this is bad.) I was trying to update all ports, by following the UPDATING file. As it turned out, some ports has been deprecated/deleted. I have a problem in particular with the py-bittornado-core port. I do not need it. So I have deleted it: # pkg_info | grep bittornado # Clearly, it is not installed. However, when I write in this command: # portmaster -a Then I get this error: === The net-p2p/py-bittornado-core port has been deleted: Has expired: Depends on the deprecated wx 2.4 === Aborting update Well, here is the question: why does it want to build a port that does not even exist in the ports tree? It was really deleted, there is no such thing as /usr/ports/net-p2p/py-bittornado-core . I have also tried to do this: # portmaster -a -x py-bittornado-core but it has exactly the same problem. Is this a stale dependency to a nonexistent port? How can I overcome this problem? Thanks, Laszlo ___ 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
boot problem after freebsd-update from 9.1-RC2 to 9.1-RC3
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 ___ 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: 9.0 crash, ssd or filesystem problem?
On 11/16/12 21:38, Warren Block wrote: On Fri, 16 Nov 2012, Gary Aitken wrote: On 11/16/12 12:10, Warren Block wrote: Additional SSD suggestions: when creating partitions, leave out the swap partition. If you have lots of memory, leave out the /tmp partition. Add that extra space to the /usr partition. Format the UFS filesystems with -Ut, for soft updates and TRIM support. (Make sure your SSD supports TRIM, almost all do.) (I don't use soft updates journaling.) Use dd(1) to make a zero-filled file on /usr somewhere, say /usr/swap. Make it the size you want swap to be, and do not make it a sparse file. Tell the system to use the swapfile in /etc/rc.conf: swapfile=/usr/swap Use tmpfs for /tmp in /etc/fstab: tmpfs/tmptmpfsrw,mode=0177700 When using the above in /etc/fstab to establish a tmp file, how does the size of /tmp get established? Is it limited only by the available swap, or is it possible to put an upper bound on it that is smaller than swap? e.g. if I built it manually: mdconfig -a -t swap -s 1g -u 1 newfs -U /dev/md1 mount /dev/md1 /tmp chmod 1777 /tmp wouldn't it be limited to 1g of swap space? Gary ___ 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
Problem with installing coreutils port
Hello All, I recently had to re-install FreeBSD on my system. I installed FreeBSD-8.3-i386 and successfully managed to install all ports except one - the sysutils/coreutils port. Underneath is the error I get : gmake[2]: Entering directory `/usr/ports/sysutils/coreutils/work/coreutils-8.20' CCLD src/factor lib/libcoreutils.a(striconv.o)(.text+0x68): In function `str_cd_iconv': : undefined reference to `libiconv' lib/libcoreutils.a(striconv.o)(.text+0xfa): In function `str_cd_iconv': : undefined reference to `libiconv' lib/libcoreutils.a(striconv.o)(.text+0x180): In function `str_cd_iconv': : undefined reference to `libiconv' lib/libcoreutils.a(striconv.o)(.text+0x26d): In function `str_iconv': : undefined reference to `libiconv_open' lib/libcoreutils.a(striconv.o)(.text+0x290): In function `str_iconv': : undefined reference to `libiconv_close' lib/libcoreutils.a(striconv.o)(.text+0x2bd): In function `str_iconv': : undefined reference to `libiconv_close' lib/libcoreutils.a(striconv.o)(.text+0x303): In function `mem_cd_iconv': : undefined reference to `libiconv' lib/libcoreutils.a(striconv.o)(.text+0x35e): In function `mem_cd_iconv': : undefined reference to `libiconv' lib/libcoreutils.a(striconv.o)(.text+0x3af): In function `mem_cd_iconv': : undefined reference to `libiconv' lib/libcoreutils.a(striconv.o)(.text+0x41b): In function `mem_cd_iconv': : undefined reference to `libiconv' lib/libcoreutils.a(striconv.o)(.text+0x458): In function `mem_cd_iconv': : undefined reference to `libiconv' lib/libcoreutils.a(striconv.o)(.text+0x4d2): more undefined references to `libiconv' follow gmake[2]: *** [src/factor] Error 1 gmake[2]: Leaving directory `/usr/ports/sysutils/coreutils/work/coreutils-8.20' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/sysutils/coreutils/work/coreutils-8.20' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/sysutils/coreutils. *** Error code 1 Stop in /usr/ports/sysutils/coreutils. I tried deinstall followed by reinstall of the iconv port. But even that does not solve the problem listed above. Can anyone please point out what might be the error and any possible solution ? I personally think the port is either broken, or the Makefile does not use the correct link options. Thank you -- Regards, Manish Jain bourne.ident...@hotmail.com ___ 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: 9.0 crash, ssd or filesystem problem?
On 11/15/12 15:56, Warren Block wrote: On Thu, 15 Nov 2012, Gary Aitken wrote: Trying to rebuild ports, I'm consistently getting the following: ahcich1 Timeout on slot 13 port 0 ^ slot varies g_vfs_done() ada0p6 [WRITE(offset=38838571008 length=4096)]error=6 That seems familiar, maybe others have reported it. Is this a motherboard controller, or add-in? mobo. Asus M4A89TD PRO/USB3 specs say AMD SB850 controller After a backup, I'd make sure the motherboard and controller BIOS are up to date. And also the SSD firmware. Thanks for the reminder, I see there is a new one. ~$ gpart show ada0 = 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 41943040 2 freebsd-ufs (20G) / 419432021048576 3 freebsd-swap (512M)swap 429917788388608 4 freebsd-ufs (4.0G) /var 513803864194304 5 freebsd-ufs (2.0G) /tmp 55574690 192216088 6 freebsd-ufs (91G) /usr 2477907782278869- free - (1.1G) It would not cause this problem, but those partitions are not aligned. That would only affect speed, not reliability. geezes, it's not even on a 4K boundary from the get-go; not sure how that happened. let-alone the 1M boundary I just learned about. Thanks ___ 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: 9.0 crash, ssd or filesystem problem?
On Fri, 16 Nov 2012, Gary Aitken wrote: ~$ gpart show ada0 = 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 41943040 2 freebsd-ufs (20G) / 419432021048576 3 freebsd-swap (512M)swap 429917788388608 4 freebsd-ufs (4.0G) /var 513803864194304 5 freebsd-ufs (2.0G) /tmp 55574690 192216088 6 freebsd-ufs (91G) /usr 2477907782278869- free - (1.1G) It would not cause this problem, but those partitions are not aligned. That would only affect speed, not reliability. geezes, it's not even on a 4K boundary from the get-go; not sure how that happened. let-alone the 1M boundary I just learned about. That's a normal install. It's fine for 512-byte devices. I have other suggestions too, but let's save that until the problem is fixed. ___ 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: 9.0 crash, ssd or filesystem problem?
~$ gpart show ada0 = 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 41943040 2 freebsd-ufs (20G) / 419432021048576 3 freebsd-swap (512M)swap 429917788388608 4 freebsd-ufs (4.0G) /var 513803864194304 5 freebsd-ufs (2.0G) /tmp 55574690 192216088 6 freebsd-ufs (91G) /usr 2477907782278869- free - (1.1G) It would not cause this problem, but those partitions are not aligned. That would only affect speed, not reliability. geezes, it's not even on a 4K boundary from the get-go; not sure how that happened. let-alone the 1M boundary I just learned about. That's a normal install. It's fine for 512-byte devices. I have other suggestions too, but let's save that until the problem is fixed. aaahhh. Vague recollections of getting this to boot up first time around. How about suggestions anyway, as I'm going to build an sata disk and move things to that as part of the process to see what's wrong. May as well get it right-ish the first time; then repartition the SSD. Thanks. ___ 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: 9.0 crash, ssd or filesystem problem?
On Fri, 16 Nov 2012, Gary Aitken wrote: ~$ gpart show ada0 = 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 41943040 2 freebsd-ufs (20G) / 419432021048576 3 freebsd-swap (512M)swap 429917788388608 4 freebsd-ufs (4.0G) /var 513803864194304 5 freebsd-ufs (2.0G) /tmp 55574690 192216088 6 freebsd-ufs (91G) /usr 2477907782278869- free - (1.1G) It would not cause this problem, but those partitions are not aligned. That would only affect speed, not reliability. geezes, it's not even on a 4K boundary from the get-go; not sure how that happened. let-alone the 1M boundary I just learned about. That's a normal install. It's fine for 512-byte devices. I have other suggestions too, but let's save that until the problem is fixed. aaahhh. Vague recollections of getting this to boot up first time around. How about suggestions anyway, as I'm going to build an sata disk and move things to that as part of the process to see what's wrong. May as well get it right-ish the first time; then repartition the SSD. Okay. The disk setup article shows alignment and using GPT labels, so I'll skip those. Additional SSD suggestions: when creating partitions, leave out the swap partition. If you have lots of memory, leave out the /tmp partition. Add that extra space to the /usr partition. Format the UFS filesystems with -Ut, for soft updates and TRIM support. (Make sure your SSD supports TRIM, almost all do.) (I don't use soft updates journaling.) Use dd(1) to make a zero-filled file on /usr somewhere, say /usr/swap. Make it the size you want swap to be, and do not make it a sparse file. Tell the system to use the swapfile in /etc/rc.conf: swapfile=/usr/swap Use tmpfs for /tmp in /etc/fstab: tmpfs /tmptmpfs rw,mode=01777 0 0 It's possible to limit the size, but not necessary. This /tmp will be cleared on reboot. Now: why? Using a swapfile through the filesystem gives three advantages: 1. Disk space is not tied up in an unused swap partition. 2. Swap can be resized without repartitioning. 3. Swap goes through the filesystem, using TRIM, helping the SSD maintain performance. /tmp as tmpfs is auto-sizing, efficient, and self-clearing on reboot. It doesn't tie up disk space in a mostly-unused partition. I use tmpfs for /usr/obj also. It doesn't improve speed, but reduces writes to SSD and is also self-clearing. ___ 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: 9.0 crash, ssd or filesystem problem?
On 11/16/12 12:10, Warren Block wrote: ~$ gpart show ada0 = 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 41943040 2 freebsd-ufs (20G) / 419432021048576 3 freebsd-swap (512M)swap 429917788388608 4 freebsd-ufs (4.0G) /var 513803864194304 5 freebsd-ufs (2.0G) /tmp 55574690 192216088 6 freebsd-ufs (91G) /usr 2477907782278869- free - (1.1G) It would not cause this problem, but those partitions are not aligned. That would only affect speed, not reliability. geezes, it's not even on a 4K boundary from the get-go; not sure how that happened. let-alone the 1M boundary I just learned about. That's a normal install. It's fine for 512-byte devices. I have other suggestions too, but let's save that until the problem is fixed. aaahhh. Vague recollections of getting this to boot up first time around. After upgrading the mobo bios I re-partitioned and so far so good although ports are messed up and I'll have to rebuild them. Did not implement the suggestions below as I needed to get back up and figured it would take me a while to get it right. Will do that on the new disk. How about suggestions anyway, as I'm going to build an sata disk and move things to that as part of the process to see what's wrong. May as well get it right-ish the first time; then repartition the SSD. Okay. The disk setup article shows alignment and using GPT labels, so I'll skip those. Additional SSD suggestions: when creating partitions, leave out the swap partition. If you have lots of memory, leave out the /tmp partition. Add that extra space to the /usr partition. Format the UFS filesystems with -Ut, for soft updates and TRIM support. (Make sure your SSD supports TRIM, almost all do.) (I don't use soft updates journaling.) Use dd(1) to make a zero-filled file on /usr somewhere, say /usr/swap. Make it the size you want swap to be, and do not make it a sparse file. Tell the system to use the swapfile in /etc/rc.conf: swapfile=/usr/swap Use tmpfs for /tmp in /etc/fstab: tmpfs/tmptmpfsrw,mode=0177700 It's possible to limit the size, but not necessary. This /tmp will be cleared on reboot. Not necessary because it is constrained by the swap file size? Now: why? Using a swapfile through the filesystem gives three advantages: 1. Disk space is not tied up in an unused swap partition. 2. Swap can be resized without repartitioning. 3. Swap goes through the filesystem, using TRIM, helping the SSD maintain performance. /tmp as tmpfs is auto-sizing, efficient, and self-clearing on reboot. It doesn't tie up disk space in a mostly-unused partition. I use tmpfs for /usr/obj also. It doesn't improve speed, but reduces writes to SSD and is also self-clearing. Thanks! ___ 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: 9.0 crash, ssd or filesystem problem?
On Fri, 16 Nov 2012, Gary Aitken wrote: On 11/16/12 12:10, Warren Block wrote: Additional SSD suggestions: when creating partitions, leave out the swap partition. If you have lots of memory, leave out the /tmp partition. Add that extra space to the /usr partition. Format the UFS filesystems with -Ut, for soft updates and TRIM support. (Make sure your SSD supports TRIM, almost all do.) (I don't use soft updates journaling.) Use dd(1) to make a zero-filled file on /usr somewhere, say /usr/swap. Make it the size you want swap to be, and do not make it a sparse file. Tell the system to use the swapfile in /etc/rc.conf: swapfile=/usr/swap Use tmpfs for /tmp in /etc/fstab: tmpfs/tmptmpfsrw,mode=0177700 It's possible to limit the size, but not necessary. This /tmp will be cleared on reboot. Not necessary because it is constrained by the swap file size? Yes, but also because /tmp usually doesn't need much space. On this desktop system, du shows all of /tmp is only 52K. ___ 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
9.0 crash, ssd or filesystem problem?
Trying to rebuild ports, I'm consistently getting the following: ahcich1 Timeout on slot 13 port 0 ^ slot varies g_vfs_done() ada0p6 [WRITE(offset=38838571008 length=4096)]error=6 /usr got error 6 while accessing filesyustem cpuid=0 panic: softdep_deallocate_dependencies:unrecovered I/O error KBD: stack backtrace: #0 ... kbd_backtrace+0x5e #1 ... panic+0x187 #2 ... clear_remove+0 #3 ... brelse+0x60 (ada0:ahcich1:0:0:0): lost device #4 ... bufdone+0x68 #5 ... g_io_schedule_up+0xa6 #6 ... fork_exit+0x11f #7 ... fork_trampoline+0xe This happens consistently when doing portmaster www/firefox ... firefox-16.0.2,1 depends on file: /usr/local/bin/perl5.12.4 - found The firefox build said it was going to build audio/alsa also, so to make things easier after rebooting I would do portmaster audio/alsa which would succeed, and then again try portmaster www/firefox which would always fail the same way. The interesting part about the above is that after the crash, the firefox build would say it needed to build audio/alsa again. I tried doing portmaster lang/perl5.12 to rebuild perl and get it placed somewhere different on the ssd, but I'm still getting a consistent crash after I get the firefox-16.0.2,1 depends on file: /usr/local/bin/perl5.12.4 - found line. I'm guessing it's crashing on something after the perl; how to find out what it is? Error 6 is ENXIO, device not configured; not sure exactly what that means. This machine has: 16G mem 0.5G swap 2G /tmp 4G /var Is any of that likely to be related to the problem? Given an addr in the failure error: g_vfs_done() ada0p6 [WRITE(offset=38838571008 length=4096)]error=6 how does one relate that addr to the partitioning scheme? ~$ gpart show ada0 = 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 41943040 2 freebsd-ufs (20G) / 419432021048576 3 freebsd-swap (512M)swap 429917788388608 4 freebsd-ufs (4.0G) /var 513803864194304 5 freebsd-ufs (2.0G) /tmp 55574690 192216088 6 freebsd-ufs (91G) /usr 2477907782278869- free - (1.1G) Thanks for any insights, Gary ___ 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: 9.0 crash, ssd or filesystem problem?
On Thu, Nov 15, 2012 at 1:18 PM, Gary Aitken free...@dreamchaser.orgwrote: Error 6 is ENXIO, device not configured; not sure exactly what that means. This machine has: 16G mem 0.5G swap 2G /tmp 4G /var Is any of that likely to be related to the problem? Given an addr in the failure error: g_vfs_done() ada0p6 [WRITE(offset=38838571008 length=4096)]error=6 how does one relate that addr to the partitioning scheme? ~$ gpart show ada0 = 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 41943040 2 freebsd-ufs (20G) / 419432021048576 3 freebsd-swap (512M)swap 429917788388608 4 freebsd-ufs (4.0G) /var 513803864194304 5 freebsd-ufs (2.0G) /tmp 55574690 192216088 6 freebsd-ufs (91G) /usr 2477907782278869- free - (1.1G) Thanks for any insights, Sounds like you have bad hardware. Drive, cable, controller etc. Probably wouldn't hurt to do a fsck either. -- Adam Vande More ___ 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: 9.0 crash, ssd or filesystem problem?
On Thu, 15 Nov 2012 13:30:43 -0600 Adam Vande More amvandem...@gmail.com wrote: Sounds like you have bad hardware. Drive, cable, controller etc. Probably wouldn't hurt to do a fsck either. *After* identifying and fixing the hardware problem, otherwise you may make things worse. -- Steve O'Hara-Smith at...@sohara.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: 9.0 crash, ssd or filesystem problem?
On Thu, 15 Nov 2012, Gary Aitken wrote: Trying to rebuild ports, I'm consistently getting the following: ahcich1 Timeout on slot 13 port 0 ^ slot varies g_vfs_done() ada0p6 [WRITE(offset=38838571008 length=4096)]error=6 That seems familiar, maybe others have reported it. Is this a motherboard controller, or add-in? After a backup, I'd make sure the motherboard and controller BIOS are up to date. And also the SSD firmware. ~$ gpart show ada0 = 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 41943040 2 freebsd-ufs (20G) / 419432021048576 3 freebsd-swap (512M)swap 429917788388608 4 freebsd-ufs (4.0G) /var 513803864194304 5 freebsd-ufs (2.0G) /tmp 55574690 192216088 6 freebsd-ufs (91G) /usr 2477907782278869- free - (1.1G) It would not cause this problem, but those partitions are not aligned. That would only affect speed, not reliability. ___ 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
ugh. dump / restore problem(s) Cannot find file dump list
I needed to expand a /var partition, which required saving and restoring /var and /usr did the following: booted to backup disk dump -0aR -h 0 -f /usr/backup/dump_var_0_20121113_1920 /dev/ada0p4 (repeat for /tmp, /usr, / partitions to be safe) repartitioned the main disk using gpart newfs the modified partitions (var, tmp, usr) rewrote the boot block and boot partition (#1) mount /dev/ada0p4 /mnt/ssd/var cd /mnt/ssd/var restore -r /usr/backup/dump_var_0_20121113_1920 Cannot find file dump list Any ideas why I get the Cannot find file dump list? What / where is it supposed to be? I was able to get some stuff back from one of the files, but only by doing: #restore -if /usr/backup/dump_usr_0_201121113_1920 restore verbose restore add libdata restore extract Extract requested files You have not read any tapes yet If you are extracting just a few files, start with the last volume and work towards the first; restore can quickly skip tapes that have no further files to extract. Otherwise, begin with volume 1. Specify next volume #: 1 Mount tape volume 1 Enter none if there are no more tapes otherwise enter tape name (default: /usr/backup/dump_usr_0_20121113_1920) unknown tape header type -2 abort [yn] n resync restore, skipped 786 blocks extract file ... ... Add links Set directory mode, owner, and times. Set owner / mode for '.' [yn] y restore If I did not enter Enter after the otherwise enter tape name, but rather entered none I did not get all of the desired contents. Can anyone shed light on this problem? I have been able to restore most everything from a cp I had done at the same time, but I'm not very confident in the results. Fortunately, user data was on a different disk. Obviously, should have done a restore -rN ... before repartitioning. Ugh. Related question: I now realize I should not have answered y to the set owner / mode question, as it changed the mode to the default for root instead of doing what I thought which was restoring the owner / mode to what was saved in the dump. Will restore -x /usr/backup/dump... correct the owner and mode? (and group and flags?) Thanks, Gary ___ 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: ugh. dump / restore problem(s) Cannot find file dump list
El día Wednesday, November 14, 2012 a las 01:20:14AM -0700, Gary Aitken escribió: I needed to expand a /var partition, which required saving and restoring /var and /usr did the following: booted to backup disk dump -0aR -h 0 -f /usr/backup/dump_var_0_20121113_1920 /dev/ada0p4 (repeat for /tmp, /usr, / partitions to be safe) repartitioned the main disk using gpart newfs the modified partitions (var, tmp, usr) rewrote the boot block and boot partition (#1) mount /dev/ada0p4 /mnt/ssd/var cd /mnt/ssd/var restore -r /usr/backup/dump_var_0_20121113_1920 Cannot find file dump list Any ideas why I get the Cannot find file dump list? What / where is it supposed to be? You need to specify the file containing the DUMP with -f flag; and use the flag -r only to restore to the original location, or -x to restore into the current dir; check the man page for details; matthias -- Sent from my FreeBSD netbook Matthias Apitz | - No system with backdoors like Apple/Android E-mail: g...@unixarea.de | - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | - No proprietary attachments phone: +49-170-4527211 | - Respect for open standards ___ 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: ugh. dump / restore problem(s) Cannot find file dump list
On Wed, 14 Nov 2012 01:20:14 -0700, Gary Aitken wrote: mount /dev/ada0p4 /mnt/ssd/var cd /mnt/ssd/var restore -r /usr/backup/dump_var_0_20121113_1920 Cannot find file dump list The last command looks wrong. The restore program requires the dump file to be provided via -f, so # restore -rf /usr/backup/dump_var_0_20121113_1920 should work. You can find an example in man restore. -- 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: ugh. dump / restore problem(s) Cannot find file dump list
From: Polytropon free...@edvax.de To: free...@dreamchaser.org Cc: FreeBSD Mailing List freebsd-questions@freebsd.org Sent: Wednesday, November 14, 2012 12:27 PM Subject: Re: ugh. dump / restore problem(s) Cannot find file dump list On Wed, 14 Nov 2012 01:20:14 -0700, Gary Aitken wrote: mount /dev/ada0p4 /mnt/ssd/var cd /mnt/ssd/var restore -r /usr/backup/dump_var_0_20121113_1920 Cannot find file dump list The last command looks wrong. The restore program requires the dump file to be provided via -f, so # restore -rf /usr/backup/dump_var_0_20121113_1920 should work. You can find an example in man restore. Hi There is no - . This is the correct format : restore rf /path/to/dump/files good luck :) ___ 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: ugh. dump / restore problem(s) Cannot find file dump list
El día Wednesday, November 14, 2012 a las 01:01:08AM -0800, Jack Mc Lauren escribió: Hi There is no - . This is the correct format : restore rf /path/to/dump/files from man restore(8): RESTORE(8) FreeBSD System Manager's Manual RESTORE(8) NAME restore, rrestore — restore files or file systems from backups made with dump SYNOPSIS restore -i [-dDhmNuvy] [-b blocksize] [-f file | -P pipecommand] [-s fileno] restore -R [-dDNuvy] [-b blocksize] [-f file | -P pipecommand] [-s fileno] restore -r [-dDNuvy] [-b blocksize] [-f file | -P pipecommand] [-s fileno] restore -t [-dDhNuvy] [-b blocksize] [-f file | -P pipecommand] [-s fileno] [file ...] restore -x [-dDhmNuvy] [-b blocksize] [-f file | -P pipecommand] [-s fileno] [file ...] ... matthias -- Sent from my FreeBSD netbook Matthias Apitz | - No system with backdoors like Apple/Android E-mail: g...@unixarea.de | - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | - No proprietary attachments phone: +49-170-4527211 | - Respect for open standards ___ 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: ugh. dump / restore problem(s) Cannot find file dump list
On Wed, 14 Nov 2012 01:01:08 -0800 (PST), Jack Mc Lauren wrote: There is no - . This is the correct format : restore rf /path/to/dump/files Really? The manual at man restore mentions: restore -r [-dDNuvy] [-b blocksize] [-f file | -P pipecommand] [-s fileno] And in the -r section: newfs /dev/da0s1a mount /dev/da0s1a /mnt cd /mnt restore rf /dev/sa0 So it seems that _both_ formats are supported (comparable to tar). One of the (in my opinion) most interesting reference sources for dump/restore also mentions this format: # mount /dev/da0s1 /mnt # mkdir /tmp/oldvar # cd /tmp/oldvar # restore -ruf /mnt/var.dump # umount /mnt Source: http://www.wonkity.com/~wblock/docs/html/backup.html#_em_dump_8_em_em_restore_8_em -- 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: ugh. dump / restore problem(s) Cannot find file dump list
On 11/14/12 01:30, Matthias Apitz wrote: El día Wednesday, November 14, 2012 a las 01:20:14AM -0700, Gary Aitken escribió: I needed to expand a /var partition, which required saving and restoring /var and /usr did the following: booted to backup disk dump -0aR -h 0 -f /usr/backup/dump_var_0_20121113_1920 /dev/ada0p4 (repeat for /tmp, /usr, / partitions to be safe) repartitioned the main disk using gpart newfs the modified partitions (var, tmp, usr) rewrote the boot block and boot partition (#1) mount /dev/ada0p4 /mnt/ssd/var cd /mnt/ssd/var restore -r /usr/backup/dump_var_0_20121113_1920 Cannot find file dump list Any ideas why I get the Cannot find file dump list? What / where is it supposed to be? You need to specify the file containing the DUMP with -f flag; and use the flag -r only to restore to the original location, or -x to restore into the current dir; check the man page for details; Sorry all, a typing issue on my part when composing the email; problem remains: # restore -iN -f /mnt/hd_ssd_backup/usr/backup/dump_tmp_0_20121113_1920 Cannot find file dump list ___ 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: ugh. dump / restore problem(s) Cannot find file dump list
On Wed, 14 Nov 2012, Polytropon wrote: On Wed, 14 Nov 2012 01:01:08 -0800 (PST), Jack Mc Lauren wrote: There is no - . This is the correct format : restore rf /path/to/dump/files Really? The manual at man restore mentions: restore -r [-dDNuvy] [-b blocksize] [-f file | -P pipecommand] [-s fileno] And in the -r section: newfs /dev/da0s1a mount /dev/da0s1a /mnt cd /mnt restore rf /dev/sa0 So it seems that _both_ formats are supported (comparable to tar). One of the (in my opinion) most interesting reference sources for dump/restore also mentions this format: # mount /dev/da0s1 /mnt # mkdir /tmp/oldvar # cd /tmp/oldvar # restore -ruf /mnt/var.dump Yes, -u unlinks an existing file before restoring that file, useful for restoring dumps over an existing filesystem. Leave out the -u when restoring to a new filesystem and the restore will go faster. # umount /mnt And that points out a mistake: /mnt can't be unmounted while it is the PWD. Fixed. Source: http://www.wonkity.com/~wblock/docs/html/backup.html#_em_dump_8_em_em_restore_8_em Thanks! ___ 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: ugh. dump / restore problem(s) Cannot find file dump list
El día Wednesday, November 14, 2012 a las 09:45:22AM -0700, Warren Block escribió: One of the (in my opinion) most interesting reference sources for dump/restore also mentions this format: # mount /dev/da0s1 /mnt # mkdir /tmp/oldvar # cd /tmp/oldvar # restore -ruf /mnt/var.dump Yes, -u unlinks an existing file before restoring that file, useful for restoring dumps over an existing filesystem. Leave out the -u when restoring to a new filesystem and the restore will go faster. # umount /mnt And that points out a mistake: /mnt can't be unmounted while it is the PWD. Fixed. I think PWD is /tmp/oldvar and not /mnt; matthias -- Sent from my FreeBSD netbook Matthias Apitz | - No system with backdoors like Apple/Android E-mail: g...@unixarea.de | - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | - No proprietary attachments phone: +49-170-4527211 | - Respect for open standards ___ 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
problem with pkgng
I am attempting to migrate a test box to pkgng, and have run into difficulty: When I run the pkg2ng script, it fails to register postgreql-jdbc because one if its files, namely /usr/local/share/doc/postgresql/README-client, is also installed by postgresql-client-9.2.1. In this, pkgng is perfectly correct, but how do I work around the issue? My assumption is that I will need to use pkg register with a hacked plist file from which the offending entry has been removed. Can anyone shed light on how to achieve this? I'm afraid I'm rather a novice at present. ___ 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
Custom ISO mount script problem
I have a server that I use to host ISO images, and mount them so they are available via network shares. I ran into a problem today, I temporarily made an ISO image accessible via a md device and mounted it under /mnt just to check the data on the ISO image. My ISO mount script ran its updated check while this was there, and hung up because of it. Now the obvious solution is to fix my script, but as I am baffled as to why it hung-up, it does do a query on md devices, and will try to dismount any that are mounted if they don't match its criteria, and delete the md device as well. However as it would have found this one in use, it should have just returned a failure and continued on. However it didn't and then when I tried to manually umount it, my umount command hung as well. What I was left with was two umount commands attempting to umount /dev/md1000 both stuck, they wouldn't respond to a kill -9 I couldn't use mdconfig -d -u 1000 to delete the md device, even with a -o force (had yet another process stuck). After 1 hour all processes were still hung, killing the shell left them zombied, but still hung there, tying up the md device. I was left with rebooting the server, until I can figure out why my script broke and didn't just error and continue the remaining checks in its list. Does anyone have any idea how if this happens again to kill these hung-up umount processes, without rebooting the server? This could be a fun one to fix, because so far attempting to duplicate the problem hasn't worked, think I just have to time something just right, or wrong depended how you look at it. -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ 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
Facing a strange problem with Boot Manager
Hi, I have never had a problem with dual-booting Win XP and FreeBSD before. Generally, I install XP first and FreeBSD second, putting the Boot Manager to the MBR. Recently, my hard disk started wobbling and I had to replace it with a new Western Digital SATA drive. When all installation work finished, FreeBSD would boot when I press F2 but pressing F1 would fail to boot XP with the error : A disk read error occurred. Press Ctrl+Alt+Del to reboot Can anybody suggest what might be the problem and any possible solution ? For the current time, I reversed the installation order and installed FreeBSD first. I saved the FFS slice's boot sector on a USB pendrive and then installed XP. So, for the time being, I have to use the Windows bootloader to boot FreeBSD by adding an entry for it boot.ini My disk layout is as follows : ad8s1 - NTFS ad8s2 - FFS ad8s3 - Extended (with ad8s5/NTFS as the only logical drive within it) Any help would be greatly appreciated. Thank you -- Regards, Manish Jain bourne.ident...@hotmail.com ___ 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: Facing a strange problem with Boot Manager
Date: Sun, 11 Nov 2012 22:09:09 +0530 From: Manish Jain bourne.ident...@hotmail.com Subject: Facing a strange problem with Boot Manager When all installation work finished, FreeBSD would boot when I press F2 but pressing F1 would fail to boot XP with the error : A disk read error occurred. Press Ctrl+Alt+Del to reboot Can anybody suggest what might be the problem and any possible solution ? No help on a fix. i'm fighting that exact problem on a FreeBSD 8.3 install on a 2nd sata drive with xp pro on the 1st drive. installed strictly to the 2nd drive -- would select in bios which to boot from. booting fbsd works fine. attempting to boot th XP drive gives the above error. Apparently the 8.3 install trashed something on the XP 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: Facing a strange problem with Boot Manager
On 12-Nov-12 02:35, Robert Bonomi wrote: Date: Sun, 11 Nov 2012 22:09:09 +0530 From: Manish Jain bourne.ident...@hotmail.com Subject: Facing a strange problem with Boot Manager When all installation work finished, FreeBSD would boot when I press F2 but pressing F1 would fail to boot XP with the error : A disk read error occurred. Press Ctrl+Alt+Del to reboot Can anybody suggest what might be the problem and any possible solution ? No help on a fix. i'm fighting that exact problem on a FreeBSD 8.3 install on a 2nd sata drive with xp pro on the 1st drive. installed strictly to the 2nd drive -- would select in bios which to boot from. booting fbsd works fine. attempting to boot th XP drive gives the above error. Apparently the 8.3 install trashed something on the XP drive. :(( I am using FreeBSD 8.3 too (i386). When XP failed to boot, a wrote out a new boot sector to drive C: with recovery console's fixboot command, but it did not make a difference. Interestingly, when all seemed lost, I even ran fixmbr, which complained that it could not fix much as my system seemed to be using a non-standard MBR. Never saw this problem before. Has the Boot Manager code/behavior changed in 8.X ? -- Regards, Manish Jain bourne.ident...@hotmail.com ___ 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
portmaster or ports (packaging) problem ?
Hi, I hit a problem today during a system update. There were two libxul ports: /usr/ports/www/libxul /usr/ports/www/libxul19 of which the last one was installed: /var/db/pkg/libxul-1.9.2.28_1/ There was a port to update which died on error: # portmaster icedtea-web ... === The dependency for www/libxul seems to be handled by libxul-1.9.2.28_1 ... === Found libxul-1.9.2.28_1, but you need to upgrade to libxul=10. *** [build-depends] Error code 1 ... # So, I had to manually deinstall www/libxul19 and install www/libxul and try again. # portmaster icedtea-web ... === The following actions will be taken if you choose to proceed: Upgrade icedtea-web-1.3_1 to icedtea-web-1.3.1 Install www/libxul ... # Is the portmaster to blame for not being smart enough and not taking steps of deinstalling www/libxul19 and installing www/libxul in one step ? jb ___ 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: portmaster or ports (packaging) problem ?
But theese are different packages (different names). since ports dont have any equivalent of debian provides flag it is impossible to figure it out in a safe way. 09-11-2012 19:19, jb jb.1234a...@gmail.com napisał(a): Hi, I hit a problem today during a system update. There were two libxul ports: /usr/ports/www/libxul /usr/ports/www/libxul19 of which the last one was installed: /var/db/pkg/libxul-1.9.2.28_1/ There was a port to update which died on error: # portmaster icedtea-web ... === The dependency for www/libxul seems to be handled by libxul-1.9.2.28_1 ... === Found libxul-1.9.2.28_1, but you need to upgrade to libxul=10. *** [build-depends] Error code 1 ... # So, I had to manually deinstall www/libxul19 and install www/libxul and try again. # portmaster icedtea-web ... === The following actions will be taken if you choose to proceed: Upgrade icedtea-web-1.3_1 to icedtea-web-1.3.1 Install www/libxul ... # Is the portmaster to blame for not being smart enough and not taking steps of deinstalling www/libxul19 and installing www/libxul in one step ? jb ___ 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: portmaster or ports (packaging) problem ?
uki ukaszg at gmail.com writes: But theese are different packages (different names). since ports dont have any equivalent of debian provides flag it is impossible to figure it out in a safe way. I have never built a port/package, so I could be wrong here. This paragraph seems to contain means to specify a dependency and built it if needed: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-depend.html for example 5.8.3 BUILD_DEPENDS aside from its primary meaning as a requirement for building *this* port, it could be used indirectly to build and install a dependent port :-) and this offer means to specify a minimal version of a dependency: 5.8.8 Minimal Version of a Dependency My point is, the logic/infrastrucutre already exists, just adopt it to next level of port/package management. jb ___ 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
nanobsd boot problem
Hi all I have some problems in the second phase of running a device from a nanobsd image. After copying the image on a flash memory, and after I set the system to boot up from flash memory, I just see a black screen and a blinking cursor ! looks like the boot device ( flash memory ) is not recognized by the system. Here are my debugging information , if they are not enough, tell me please to send you necessary informations : dmesg output : da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: UFD 2.0 Silicon-Power8G PMAP Removable Direct Access SCSI-4 device da0: 40.000MB/s transfers da0: 7388MB (15130624 512 byte sectors: 255H 63S/T 941C) according to the last line, I change the NANO_SECTS to 63 and NANO_HEADS to 255. (in nanobsd.sh). ls /dev output : da0s1 da0s1a ad6s1b da0s3 ad6s1d da0s4 according to the first column , I set NANO_DRIVE to da0. (in nanobsd.sh) and here are the contents of the flash memory : ls /mnt .cshrc boot lib rescue usr .profile cfg libexec root var .snap conf media sbin COPYRIGHT dev mnt sys bin etc proc tmp Am I missing something ?? could you please me please ? ___ 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: Problem with libpng + Mozilla applications on FreeBSD 8.3
On Sunday 28 October 2012 01:17:46 Manish Jain wrote: Consider me a newbie here. How do I do wide-reinstall ? You can do this with ports-mgmt/portmaster. See the section Using portmaster to do a complete reinstallation of all your ports at the end of the examples section of the man page. I don't mind pulling in and building a few more ports as long as it is not the whole GNOME2 metaport Rebuilding everything is the least complicated way of fixing the problem. It's a big job but if you don't do that then you're likely to have to keep doing even more firefighting in the future. -- 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
Problem with connecting FreeBSD 8.3 to wireless network
On 28-Oct-12 05:53, Polytropon wrote: On Sun, 28 Oct 2012 05:47:46 +0530, Manish Jain wrote: On 28-Oct-12 01:49, Polytropon wrote: I don't mind pulling in and building a few more ports as long as it is not the whole GNOME2 metaport. It could very well be the whole Gnome 2 metaport. :-( Hi All, After reading all the replies to my earlier post Problem with libpng + Mozilla applications on FreeBSD 8.3, I finally summoned up the courage to build the GNOME2 metaport from the ports directory. Since this would not be possible within my lifetime with my usual internet connection, I paid for and succeeded in getting temporary access to a wireless network. Win XP connects to the network pretty smoothly, so there was much reason for hope that things would go smoothly on my FreeBSD 8.3 installation too. I tried configuring the Atheros device to the network as explained in the FreeBSD handbook. But I am having usual rate of success, which is not very high. All the required modules are present in the kernel, as can be seen below : # kldload ath kldload: can't load ath: File exists # kldload wlan_tkip kldload: can't load wlan_tkip: File exists But dmesg returns no output for ath0 : # dmesg | grep -i ath Empty output ifconfig returns the following output : # ifconfig bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=c019bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE ether b8:88:e3:45:63:b1 inet6 fe80::ba88:e3ff:fe45:63b1%bge0 prefixlen 64 scopeid 0x2 nd6 options=3PERFORMNUD,ACCEPT_RTADV media: Ethernet autoselect (none) status: no carrier lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 nd6 options=3PERFORMNUD,ACCEPT_RTADV tun0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST metric 0 mtu 1500 options=8LINKSTATE inet 10.0.0.1 -- 10.0.0.2 netmask 0xff00 Opened by PID 767 Since there is no mention of ath0, I did not expect creating the wlan0 pseudo-device would be a simple matter, and I was right : # ifconfig wlan0 create wlandev ath0 ifconfig: SIOCIFCREATE2: Device not configured Manually trying to create the pseudo-device ath0 presents equally unpleasant output : # ifconfig ath0 create ifconfig: SIOCIFCREATE2: Invalid argument pciconf does show my device, but I do not know how to make use of the information (please refer the last few lines of the output) : # pciconf -lv hostb0@pci0:0:0:0: class=0x06 card=0x06491025 chip=0x01048086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' class = bridge subclass = HOST-PCI vgapci0@pci0:0:2:0: class=0x03 card=0x06491025 chip=0x01068086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' class = display subclass = VGA none0@pci0:0:22:0: class=0x078000 card=0x06491025 chip=0x1e3a8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = simple comms ehci0@pci0:0:26:0: class=0x0c0320 card=0x06491025 chip=0x1e2d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = USB hdac0@pci0:0:27:0: class=0x040300 card=0x06491025 chip=0x1e208086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = multimedia subclass = HDA pcib1@pci0:0:28:0: class=0x060400 card=0x06491025 chip=0x1e108086 rev=0xc4 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI pcib2@pci0:0:28:1: class=0x060400 card=0x06491025 chip=0x1e128086 rev=0xc4 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI ehci1@pci0:0:29:0: class=0x0c0320 card=0x06491025 chip=0x1e268086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = USB isab0@pci0:0:31:0: class=0x060100 card=0x06491025 chip=0x1e5e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = bridge subclass = PCI-ISA atapci0@pci0:0:31:2: class=0x01018f card=0x06491025 chip=0x1e018086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = mass storage subclass = ATA none1@pci0:0:31:3: class=0x0c0500 card=0x06491025 chip=0x1e228086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = SMBus atapci1@pci0:0:31:5: class=0x010185 card=0x06491025 chip=0x1e098086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = mass storage subclass = ATA bge0@pci0:2:0:0: class=0x02 card=0x06471025 chip=0x16b514e4 rev=0x10 hdr=0x00 vendor = 'Broadcom Corporation' class = network subclass = ethernet none2@pci0:2:0:1: class=0x080501 card=0x06471025 chip=0x16bc14e4 rev=0x10 hdr=0x00 vendor = 'Broadcom
Re: Problem with connecting FreeBSD 8.3 to wireless network
On 10/28/12 20:50, Manish Jain wrote: # dmesg | grep -i ath Empty output Doesn't look like your atheros network card has been detected by your system. Did you check the ath(4) man page to see if your particular piece of hardware is supported on FreeBSD 8.3? http://www.freebsd.org/cgi/man.cgi?query=athsektion=4manpath=FreeBSD+8.3-RELEASE HARDWARE The ath driver supports all Atheros Cardbus and PCI cards, except those that are based on the AR5005VL chipset. I'm running: box0=; uname -a FreeBSD box0.my.domain 9.1-RC2 FreeBSD 9.1-RC2 #0 r241133: Tue Oct 2 17:11:45 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 And my atheros card is supported. box0=; dmesg | grep ath ath0: Atheros 5424/2424 mem 0xd600-0xd600 irq 16 at device 0.0 on pci2 ath0: AR2425 mac 14.2 RF5424 phy 7.0 ___ 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: Problem with connecting FreeBSD 8.3 to wireless network
Forgot to mention the full name of the adapter : Atheros AR5B125 Regards, Manish Jain bourne.ident...@hotmail.com On 29-Oct-12 00:20, Manish Jain wrote: On 28-Oct-12 05:53, Polytropon wrote: On Sun, 28 Oct 2012 05:47:46 +0530, Manish Jain wrote: On 28-Oct-12 01:49, Polytropon wrote: I don't mind pulling in and building a few more ports as long as it is not the whole GNOME2 metaport. It could very well be the whole Gnome 2 metaport. :-( Hi All, After reading all the replies to my earlier post Problem with libpng + Mozilla applications on FreeBSD 8.3, I finally summoned up the courage to build the GNOME2 metaport from the ports directory. Since this would not be possible within my lifetime with my usual internet connection, I paid for and succeeded in getting temporary access to a wireless network. Win XP connects to the network pretty smoothly, so there was much reason for hope that things would go smoothly on my FreeBSD 8.3 installation too. I tried configuring the Atheros device to the network as explained in the FreeBSD handbook. But I am having usual rate of success, which is not very high. All the required modules are present in the kernel, as can be seen below : # kldload ath kldload: can't load ath: File exists # kldload wlan_tkip kldload: can't load wlan_tkip: File exists But dmesg returns no output for ath0 : # dmesg | grep -i ath Empty output ifconfig returns the following output : # ifconfig bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=c019bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE ether b8:88:e3:45:63:b1 inet6 fe80::ba88:e3ff:fe45:63b1%bge0 prefixlen 64 scopeid 0x2 nd6 options=3PERFORMNUD,ACCEPT_RTADV media: Ethernet autoselect (none) status: no carrier lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 nd6 options=3PERFORMNUD,ACCEPT_RTADV tun0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST metric 0 mtu 1500 options=8LINKSTATE inet 10.0.0.1 -- 10.0.0.2 netmask 0xff00 Opened by PID 767 Since there is no mention of ath0, I did not expect creating the wlan0 pseudo-device would be a simple matter, and I was right : # ifconfig wlan0 create wlandev ath0 ifconfig: SIOCIFCREATE2: Device not configured Manually trying to create the pseudo-device ath0 presents equally unpleasant output : # ifconfig ath0 create ifconfig: SIOCIFCREATE2: Invalid argument pciconf does show my device, but I do not know how to make use of the information (please refer the last few lines of the output) : # pciconf -lv hostb0@pci0:0:0:0:class=0x06 card=0x06491025 chip=0x01048086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' class = bridge subclass = HOST-PCI vgapci0@pci0:0:2:0:class=0x03 card=0x06491025 chip=0x01068086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' class = display subclass = VGA none0@pci0:0:22:0:class=0x078000 card=0x06491025 chip=0x1e3a8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = simple comms ehci0@pci0:0:26:0:class=0x0c0320 card=0x06491025 chip=0x1e2d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = USB hdac0@pci0:0:27:0:class=0x040300 card=0x06491025 chip=0x1e208086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = multimedia subclass = HDA pcib1@pci0:0:28:0:class=0x060400 card=0x06491025 chip=0x1e108086 rev=0xc4 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI pcib2@pci0:0:28:1:class=0x060400 card=0x06491025 chip=0x1e128086 rev=0xc4 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI ehci1@pci0:0:29:0:class=0x0c0320 card=0x06491025 chip=0x1e268086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = USB isab0@pci0:0:31:0:class=0x060100 card=0x06491025 chip=0x1e5e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = bridge subclass = PCI-ISA atapci0@pci0:0:31:2:class=0x01018f card=0x06491025 chip=0x1e018086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = mass storage subclass = ATA none1@pci0:0:31:3:class=0x0c0500 card=0x06491025 chip=0x1e228086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = SMBus atapci1@pci0:0:31:5:class=0x010185 card=0x06491025 chip=0x1e098086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = mass storage subclass = ATA bge0@pci0:2:0:0:class=0x02 card=0x06471025 chip=0x16b514e4 rev=0x10 hdr=0x00 vendor = 'Broadcom Corporation' class
Re: Problem with connecting FreeBSD 8.3 to wireless network
On Mon, 29 Oct 2012, Manish Jain wrote: Those in a position to help but smugly choose not to may soon start experiencing a dramatic decline in their good fortunes. I'm not in a position to help, but I can explain a couple of things. # kldload ath kldload: can't load ath: File exists # kldload wlan_tkip kldload: can't load wlan_tkip: File exists This tells you that the module in question has already been loaded, or is present in the kernel. [snip] none5@pci0:3:0:0: class=0x028000 card=0x661711ad chip=0x0032168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' class = network The 'none..' tells you that no driver was attached to the device. I suspect that Alexander Kapshuk's reply is relevant here: that your Atheros card is not supported by the driver. I know it's not much help, but maybe it's nonzero. Good luck. -- Chris Hill ch...@monochrome.org ** [ Busy Expunging / ] ___ 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: ata controller problem
Am 26.10.2012 18:33, schrieb Jeremy Chadwick: Regarding this: http://lists.freebsd.org/pipermail/freebsd-questions/2012-October/245862.html No no NO *NO*! I wish people would stop recommending this utter garbage. There is absolutely no justification behind using the highly convoluted labelling mechanisms at multiple layers within FreeBSD. There are 3 (possibly 4) different label mechanisms which do nothing but confuse the user, or cause other oddities/complexities. Good grief, there is so much hard evidence on the mailing lists over the past 5 (maybe even 7?) years talking about the utter mess that is filesystem/device/geom/blahblah labels that to recommend this is borderline insane. The proper way to solve this problem is to user /boot/loader.conf tie-downs to assign each disk to each individual controllers' device number (e.g. ada0 -- scbus0 -- ahcich0, or whatever you want). Please note I said ahcichX, not ahciX. Different things. I have helped others in the past do this; Randy Bush is one such person. Taken directly from my /boot/loader.conf with a single SATA controller, but obviously this can be adjusted to whatever you want. # Wire down device names (ada[0-5]) to each individual port # on the SATA/AHCI controller. This ensures that if we reboot # with a disk missing, the device names stay the same, and stay # attached to the same SATA/AHCI controller. # http://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html # hint.scbus.0.at=ahcich0 hint.scbus.1.at=ahcich1 hint.scbus.2.at=ahcich2 hint.scbus.3.at=ahcich3 hint.scbus.4.at=ahcich4 hint.scbus.5.at=ahcich5 hint.ada.0.at=scbus0 hint.ada.1.at=scbus1 hint.ada.2.at=scbus2 hint.ada.3.at=scbus3 hint.ada.4.at=scbus4 hint.ada.5.at=scbus5 See CAM(4) man page (read it, don't skim!) for full details. Just please for the love of god do not use labels to solve this. Sorry this doesn't work because the numbering of the ahci change with the occupancy of the Hot-Swap Bays. And that is my Problem. This i have tried first. Any idea how i can fix which controller gets which number. Regard Estartu -- - Gerhard Schmidt | E-Mail und JabberID: TU-München| schm...@ze.tum.de WWW Online Services | Tel: 089/289-25270| Fax: 089/289-25257| PGP-Publickey auf Anfrage ___ 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: ata controller problem
On 26.10.2012 18:00, Polytropon wrote: On Fri, 26 Oct 2012 14:18:16 +0200, Gerhard Schmidt wrote: The Problem is that, if there is a Drive in one of the HotSwap Bays the PCI-Express controller is detected as ahci0 and the onboard is detected as ahci1. Therefore any drives in the HotSwap Bays become ada0-3 and the drives on the mainboard controller are the upper numbers which causes the boot to fail as the Root Partition isn't there where it's expected. The BIOS has the PCI-Express Card as second Card only so the Kernel is Booted but the RootFS is not Found. You can use labels (GPT or UFS labels) or UFSIDs to become independent of the actual device name where things are stored on. You could also use this to make disks easier to identify (e. g. /dev/label/red1root = the disk with a red 1 on it, carrying the root file system). I suggest those pages for more detailed information: http://www.wonkity.com/~wblock/docs/html/disksetup.html http://www.freebsd.org/doc/handbook/geom-glabel.html Maybe as well (specific and general notes and inspiration): http://www.daemonforums.org/showthread.php?t=2666 http://www.freebsdonline.com/content/view/731/506/ http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html I assume that you are using UFS. Is there a way to ensure that the onboard SATA Controller is always probed first. I'm not sure if this can be done, but using labels should make the question go away, and the problem causing it. :-) Labels are good for naming Drives but how does it help me if the root filesystem changing device ids. I don't think the boot loader is able to use the label for the root Filesystem. Regards Estartu -- - Gerhard Schmidt | E-Mail und JabberID: TU-München| schm...@ze.tum.de WWW Online Services | Tel: 089/289-25270| Fax: 089/289-25257| PGP-Publickey auf Anfrage ___ 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: ata controller problem
Hi, On Sat, 27 Oct 2012 10:22:01 +0200 Gerhard Schmidt schm...@ze.tum.de wrote: hint.ada.3.at=scbus3 hint.ada.4.at=scbus4 hint.ada.5.at=scbus5 See CAM(4) man page (read it, don't skim!) for full details. Just please for the love of god do not use labels to solve this. Sorry this doesn't work because the numbering of the ahci change with the occupancy of the Hot-Swap Bays. And that is my Problem. This i have tried first. Any idea how i can fix which controller gets which number. just you labels. Chose the labelling method which fits best your file system. gpt seems to fit most scenarios. Labels came up to solve your problem. Erich ___ 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: Problem with libpng + Mozilla applications on FreeBSD 8.3
Sometimes placing symlink to the newer version of library instead of older version helps. On Fri, Oct 26, 2012 at 11:06 PM, Polytropon free...@edvax.de wrote: On Sat, 27 Oct 2012 00:06:44 +0530, Manish Jain wrote: Hello Polytropon, Thanks for replying. Maybe an update of FF and TB would be sufficient, so it can link to the present (or at least expected) libraries accordingly. Maybe I did not make it clear enough in the original message. The only thing I installed from the installation DVD was the OS and the GNOME2 metaport. Everything else including FF and TB was installed from ports, the tarball of which I downloaded just a couple of days back. I hope you are not suggesting that I build the GNOME2 metaport too from the ports directory : with my internet connection, that really would take me into the next century. Exactly that would have been the preferred solution. :-) You should not manually copy things. At some point, something will crash, and the ports infrastructure cannot take care of it. It's easier to use a port management tool (like portmaster) to deal with installing and updating of ports. For the present issue, it seems logical that I would need 2 versions of libpng : one for GNOME and one for the ports being installed. Having the two versions reside independently in /usr/lib and /usr/local/lib seems to be the only way out. I still must admit that it defeats the purpose of having port management tools. It also blurs the line between OS (/usr/lib) and additional software (/usr/local/lib) directories. However, both directories are used by the linker, so it looks possible (and probably better than messing with symlinks in /usr/local/lib). Problems _might_ occur when updating world. -- 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 -- 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: ata controller problem
Hi, On Sat, 27 Oct 2012 10:25:41 +0200 Gerhard Schmidt schm...@ze.tum.de wrote: On 26.10.2012 18:00, Polytropon wrote: = I'm not sure if this can be done, but using labels should make the question go away, and the problem causing it. :-) Labels are good for naming Drives but how does it help me if the root filesystem changing device ids. I don't think the boot loader is able to use the label for the root Filesystem. put a root file system on all drives and make it bootable. I use this trick also. You do not need that much space there to get the system up compared to the size of current media. Erich ___ 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: Problem with libpng + Mozilla applications on FreeBSD 8.3
On Saturday 27 October 2012 09:42:10 Alexandr Alexeev wrote: Sometimes placing symlink to the newer version of library instead of older version helps. Specifying the alternative version in /etc/libmap.conf (5) is a neater way of doing this. The man page also shows you how to restrict the mapping to apply for only specified executables. -- 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
Re: Problem with libpng + Mozilla applications on FreeBSD 8.3
On Fri, Oct 26, 2012 at 11:06 PM, Polytropon free...@edvax.de wrote: On Sat, 27 Oct 2012 00:06:44 +0530, Manish Jain wrote: Hello Polytropon, Thanks for replying. Maybe an update of FF and TB would be sufficient, so it can link to the present (or at least expected) libraries accordingly. Maybe I did not make it clear enough in the original message. The only thing I installed from the installation DVD was the OS and the GNOME2 metaport. Everything else including FF and TB was installed from ports, the tarball of which I downloaded just a couple of days back. I hope you are not suggesting that I build the GNOME2 metaport too from the ports directory : with my internet connection, that really would take me into the next century. Exactly that would have been the preferred solution. :-) You should not manually copy things. At some point, something will crash, and the ports infrastructure cannot take care of it. It's easier to use a port management tool (like portmaster) to deal with installing and updating of ports. For the present issue, it seems logical that I would need 2 versions of libpng : one for GNOME and one for the ports being installed. Having the two versions reside independently in /usr/lib and /usr/local/lib seems to be the only way out. I still must admit that it defeats the purpose of having port management tools. It also blurs the line between OS (/usr/lib) and additional software (/usr/local/lib) directories. However, both directories are used by the linker, so it looks possible (and probably better than messing with symlinks in /usr/local/lib). Problems _might_ occur when updating world. -- 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 Sometimes placing symlink to the newer version of library instead of older version helps. There is only one symlink (/usr/local/bin/libpng.so) and it points to the newer version. Regards, Manish Jain bourne.ident...@hotmail.com ___ 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: ata controller problem
Am 27.10.2012 10:39, schrieb Erich Dollansky: Hi, On Sat, 27 Oct 2012 10:22:01 +0200 Gerhard Schmidt schm...@ze.tum.de wrote: hint.ada.3.at=scbus3 hint.ada.4.at=scbus4 hint.ada.5.at=scbus5 See CAM(4) man page (read it, don't skim!) for full details. Just please for the love of god do not use labels to solve this. Sorry this doesn't work because the numbering of the ahci change with the occupancy of the Hot-Swap Bays. And that is my Problem. This i have tried first. Any idea how i can fix which controller gets which number. just you labels. Chose the labelling method which fits best your file system. gpt seems to fit most scenarios. Labels came up to solve your problem. Can I mount the root filesystem via label. That's the problem here. Regard Estartu -- - Gerhard Schmidt | E-Mail und JabberID: TU-München| schm...@ze.tum.de WWW Online Services | Tel: 089/289-25270| Fax: 089/289-25257| PGP-Publickey auf Anfrage signature.asc Description: OpenPGP digital signature
Re: ata controller problem / AHCI numbering
On 2012.10.26 14:18, Gerhard Schmidt wrote: if there is a Drive in one of the HotSwap Bays the PCI-Express controller is detected as ahci0 and the onboard is detected as ahci1. So Far i could have set some devices.hints entries to sort the scsi busses. But the problem is that if there are no drives in the Bays the PCI-Expresscard is detected as ahci1 On 2012.10.27 10:22, Gerhard Schmidt wrote: Am 26.10.2012 18:33, schrieb Jeremy Chadwick: The proper way to solve this problem is to user /boot/loader.conf tie-downs to assign each disk to each individual controllers' device number (e.g. ada0 -- scbus0 -- ahcich0, or whatever you want). Please note I said ahcichX, not ahciX. Different things. Sorry this doesn't work because the numbering of the ahci change with the occupancy of the Hot-Swap Bays. I'm surprised and curious about this... Don't all devices, including SATA/AHCI controllers, get probed and numbered in the order they are presented to a kernel ? What can cause that presentation order to vary when physical connections don't change ? How could even an intrusive x86 BIOS feature change that presentation order based on whether or not a disk is connected to a peripheral device ? Doesn't a BIOS stay ignorant of what is plugged into external controllers, which have their own boot ROM ? Certainly FreeBSD's kernel would not bother to reorder device numbers based on what is connected to them lower down the chain after it's discovered these children, right ? (I'd be curious to take a look at your dmesg, Gerhard) I wish I could test this and figure it out on my own, but I don't have the right hardware available to replicate it and VirtualBox only supports a single virtual SATA controller. Using two identical (crappy) ASMedia AHCI 6Gbps PCIe adapters, I wasn't able to get their ahci numbering reversed by plugging or unplugging disks from them before booting. But the mainboard's SATA controllers are driven by atapci instead of ahci, so it's not quite the same... ___ 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: ata controller problem
Gerhard Schmidt schm...@ze.tum.de writes: Labels are good for naming Drives but how does it help me if the root filesystem changing device ids. I don't think the boot loader is able to use the label for the root Filesystem. From my fstab: /dev/ufs/Oak / ufs rw,noatime 1 1 /dev/label/OakSwap none swapsw 0 0 I think any of the other label schemes will also work. If you don't remember which label is which device id, then 'glabel status' will show that, but you shouldn't need to. -- Carl Johnsonca...@peak.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: Problem with libpng + Mozilla applications on FreeBSD 8.3
But Mozilla applications like Firefox and Thunderbird present a peculiar problem - the buttons on the Tool bar/Menu bar do not have any image on them. The problem is not Mozilla-specific. I built Opera web browser from ports, and that too has images missing from its buttons. Looks like I am going to have to contend with being less image-inative in the coming days. Regards, Manish Jain bourne.ident...@hotmail.com ___ 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: Problem with libpng + Mozilla applications on FreeBSD 8.3
On Sun, 28 Oct 2012 01:43:11 +0530, Manish Jain wrote: But Mozilla applications like Firefox and Thunderbird present a peculiar problem - the buttons on the Tool bar/Menu bar do not have any image on them. The problem is not Mozilla-specific. I built Opera web browser from ports, and that too has images missing from its buttons. It seems that the problem is in some dependency, not the top port itself. This usually indicates that something in /usr/local is dangerously out of sync, and in most cases, wide re-installs solve such kind of problem. Looks like I am going to have to contend with being less image-inative in the coming days. You just need to imagine the images. :-) -- 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: Problem with libpng + Mozilla applications on FreeBSD 8.3
Date: Sat, 27 Oct 2012 22:19:16 +0200 From: Polytropon free...@edvax.de Subject: Re: Problem with libpng + Mozilla applications on FreeBSD 8.3 On Sun, 28 Oct 2012 01:43:11 +0530, Manish Jain wrote: Looks like I am going to have to contend with being less image-inative in the coming days. You just need to imagine the images. :-) It's a complex issue. a purely imagine-ary solution is inadequate. *SNICKER* (or *ALMOND*JOY* if you prefer nuts) ___ 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: Problem with libpng + Mozilla applications on FreeBSD 8.3
On 28-Oct-12 01:49, Polytropon wrote: On Sun, 28 Oct 2012 01:43:11 +0530, Manish Jain wrote: But Mozilla applications like Firefox and Thunderbird present a peculiar problem - the buttons on the Tool bar/Menu bar do not have any image on them. The problem is not Mozilla-specific. I built Opera web browser from ports, and that too has images missing from its buttons. It seems that the problem is in some dependency, not the top port itself. This usually indicates that something in /usr/local is dangerously out of sync, and in most cases, wide re-installs solve such kind of problem. Looks like I am going to have to contend with being less image-inative in the coming days. You just need to imagine the images. :-) Hello Poly, wide re-installs Consider me a newbie here. How do I do wide-reinstall ? I don't mind pulling in and building a few more ports as long as it is not the whole GNOME2 metaport. Thank you Regards, Manish Jain bourne.ident...@hotmail.com ___ 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: Problem with libpng + Mozilla applications on FreeBSD 8.3
On Sun, 28 Oct 2012 05:47:46 +0530, Manish Jain wrote: On 28-Oct-12 01:49, Polytropon wrote: On Sun, 28 Oct 2012 01:43:11 +0530, Manish Jain wrote: But Mozilla applications like Firefox and Thunderbird present a peculiar problem - the buttons on the Tool bar/Menu bar do not have any image on them. The problem is not Mozilla-specific. I built Opera web browser from ports, and that too has images missing from its buttons. It seems that the problem is in some dependency, not the top port itself. This usually indicates that something in /usr/local is dangerously out of sync, and in most cases, wide re-installs solve such kind of problem. Looks like I am going to have to contend with being less image-inative in the coming days. You just need to imagine the images. :-) Hello Poly, wide re-installs Consider me a newbie here. How do I do wide-reinstall ? That's nowhere a correct terminus technicus or established word. It just means that, for example, if you update one small library that is incorporated by a dependency of a dependency of a library part of Gtk, you need to recompile everything in relation to Gtk, all Gtk programs, libraries and dependencies. Manually tracing down the dependency could be possible, and maybe manual overrides with symlinks and libmap.conf can work, but if you update something here, in conclusion something there, it could lead to even more trouble, forcing you to do much more updates than you are willing to perform. I don't mind pulling in and building a few more ports as long as it is not the whole GNOME2 metaport. It could very well be the whole Gnome 2 metaport. :-( -- 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
ata controller problem
Hi, i have a very strange Problem with my new Workstation. The Problem is the order of the sata controllers. The Mainboard has 6 sata Ports and i have a PCI-Express Card with 4 more sata Channels. I boot from a SSD connected to port 0 in the Mainboard. Channels 1-3 are additional Harddisks and 5 is a optical drive. I've a Hotswap-Bay for 3 SATA Drives the bay is connected to the PCI-Express Card SATA Channel. The Problem is that, if there is a Drive in one of the HotSwap Bays the PCI-Express controller is detected as ahci0 and the onboard is detected as ahci1. Therefore any drives in the HotSwap Bays become ada0-3 and the drives on the mainboard controller are the upper numbers which causes the boot to fail as the Root Partition isn't there where it's expected. The BIOS has the PCI-Express Card as second Card only so the Kernel is Booted but the RootFS is not Found. So Far i could have set some devices.hints entries to sort the scsi busses. But the problem is that if there are no drives in the Bays the PCI-Expresscard is detected as ahci1 Is there a way to ensure that the onboard SATA Controller is always probed first. Regards Gerhard -- - Gerhard Schmidt | E-Mail und JabberID: TU-München| schm...@ze.tum.de WWW Online Services | ___ 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
Problem with libpng + Mozilla applications on FreeBSD 8.3
Hi All, I recently purchased a laptop (Intel Pentium dual core) and installed FreeBSD 8.3-i386 on it using the 'All' canned distribution. I then downloaded the latest ports tarball and started building them. Some of the ports required a newer version of the graphics/png port, so I did a deinstall and reinstall in graphics/png. This removed the previous binary libpng.so.6 and placed version libpng15.so.15 in its stead. Things went wrong here - the GNOME desktop started crashing with the panel not working and practically all desktop icons gone. So I guessed that the canned version of GNOME in the installation DVD had a dependency on libpng.so.6. I reinstalled FreeBSD 8.3, and copied /usr/local/lib/libpng.so.6 to /usr/lib/libpng.so.6 before building the ports a second time. This time things went a lot more smoothly. GNOME works. But Mozilla applications like Firefox and Thunderbird present a peculiar problem - the buttons on the Tool bar/Menu bar do not have any image on them. While this is not exactly a catastrophe, it is rankling to say the least. Maybe some gentleman has faced this problem and has sorted it out. If anyone can provide a hint on how to fix the problem, I would be grateful indeed. Thank you Regards, Manish Jain bourne.ident...@hotmail.com ___ 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: Problem with libpng + Mozilla applications on FreeBSD 8.3
On Fri, 26 Oct 2012 20:03:11 +0530, Manish Jain wrote: Hi All, I recently purchased a laptop (Intel Pentium dual core) and installed FreeBSD 8.3-i386 on it using the 'All' canned distribution. I then downloaded the latest ports tarball and started building them. This ports snapshot is not in sync with the installed world and possibly installed 3rd party programs (ports) anymore. Some of the ports required a newer version of the graphics/png port, so I did a deinstall and reinstall in graphics/png. This removed the previous binary libpng.so.6 and placed version libpng15.so.15 in its stead. Things went wrong here - the GNOME desktop started crashing with the panel not working and practically all desktop icons gone. Exactly my experience with some libjpeg update some years ago. :-) The rule usually is: If you update a port others depend on (read: depend on a specific version), you also need to update those ports. Mixing versions doesn't seem to be a good idea. So I guessed that the canned version of GNOME in the installation DVD had a dependency on libpng.so.6. Correct. I reinstalled FreeBSD 8.3, [...] Why did you reinstall the OS? Things like Gnome or PNG libarary are separated. [...] and copied /usr/local/lib/libpng.so.6 to /usr/lib/libpng.so.6 before building the ports a second time. You should not manually copy things. At some point, something will crash, and the ports infrastructure cannot take care of it. It's easier to use a port management tool (like portmaster) to deal with installing and updating of ports. This time things went a lot more smoothly. GNOME works. But Mozilla applications like Firefox and Thunderbird present a peculiar problem - the buttons on the Tool bar/Menu bar do not have any image on them. It seems that there is some library collision. If you update things, update _all_ of them, in order to avoid version trouble. The best approach (in your case) would be: Install the OS, do not install anything from ports yet. Get the ports tree. Update it to the recent version. Now start installing stuff, and do it from the _same_ ports tree. Alternative: If you go with the programs installed from the media (e. g. the DVD), use pkg_add to get binary installed applications. In case you insist on compiling, get the ports tree of the _state of your installation_ (i. e. the tarball from the DVD) and use that. Do not update it. In this case, you can easily mix compiling from source and installing via binary packages. This alternative is not suggested now. :-) While this is not exactly a catastrophe, it is rankling to say the least. Maybe some gentleman has faced this problem and has sorted it out. If anyone can provide a hint on how to fix the problem, I would be grateful indeed. Maybe an update of FF and TB would be sufficient, so it can link to the present (or at least expected) libraries accordingly. -- 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: ata controller problem
On Fri, 26 Oct 2012 14:18:16 +0200, Gerhard Schmidt wrote: The Problem is that, if there is a Drive in one of the HotSwap Bays the PCI-Express controller is detected as ahci0 and the onboard is detected as ahci1. Therefore any drives in the HotSwap Bays become ada0-3 and the drives on the mainboard controller are the upper numbers which causes the boot to fail as the Root Partition isn't there where it's expected. The BIOS has the PCI-Express Card as second Card only so the Kernel is Booted but the RootFS is not Found. You can use labels (GPT or UFS labels) or UFSIDs to become independent of the actual device name where things are stored on. You could also use this to make disks easier to identify (e. g. /dev/label/red1root = the disk with a red 1 on it, carrying the root file system). I suggest those pages for more detailed information: http://www.wonkity.com/~wblock/docs/html/disksetup.html http://www.freebsd.org/doc/handbook/geom-glabel.html Maybe as well (specific and general notes and inspiration): http://www.daemonforums.org/showthread.php?t=2666 http://www.freebsdonline.com/content/view/731/506/ http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html I assume that you are using UFS. Is there a way to ensure that the onboard SATA Controller is always probed first. I'm not sure if this can be done, but using labels should make the question go away, and the problem causing it. :-) -- 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: ata controller problem
Regarding this: http://lists.freebsd.org/pipermail/freebsd-questions/2012-October/245862.html No no NO *NO*! I wish people would stop recommending this utter garbage. There is absolutely no justification behind using the highly convoluted labelling mechanisms at multiple layers within FreeBSD. There are 3 (possibly 4) different label mechanisms which do nothing but confuse the user, or cause other oddities/complexities. Good grief, there is so much hard evidence on the mailing lists over the past 5 (maybe even 7?) years talking about the utter mess that is filesystem/device/geom/blahblah labels that to recommend this is borderline insane. The proper way to solve this problem is to user /boot/loader.conf tie-downs to assign each disk to each individual controllers' device number (e.g. ada0 -- scbus0 -- ahcich0, or whatever you want). Please note I said ahcichX, not ahciX. Different things. I have helped others in the past do this; Randy Bush is one such person. Taken directly from my /boot/loader.conf with a single SATA controller, but obviously this can be adjusted to whatever you want. # Wire down device names (ada[0-5]) to each individual port # on the SATA/AHCI controller. This ensures that if we reboot # with a disk missing, the device names stay the same, and stay # attached to the same SATA/AHCI controller. # http://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html # hint.scbus.0.at=ahcich0 hint.scbus.1.at=ahcich1 hint.scbus.2.at=ahcich2 hint.scbus.3.at=ahcich3 hint.scbus.4.at=ahcich4 hint.scbus.5.at=ahcich5 hint.ada.0.at=scbus0 hint.ada.1.at=scbus1 hint.ada.2.at=scbus2 hint.ada.3.at=scbus3 hint.ada.4.at=scbus4 hint.ada.5.at=scbus5 See CAM(4) man page (read it, don't skim!) for full details. Just please for the love of god do not use labels to solve this. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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: ata controller problem
On Fri, 26 Oct 2012 09:33:38 -0700, Jeremy Chadwick wrote: Regarding this: http://lists.freebsd.org/pipermail/freebsd-questions/2012-October/245862.html No no NO *NO*! No? :-) I wish people would stop recommending this utter garbage. There is absolutely no justification behind using the highly convoluted labelling mechanisms at multiple layers within FreeBSD. There are 3 (possibly 4) different label mechanisms which do nothing but confuse the user, or cause other oddities/complexities. Good grief, there is so much hard evidence on the mailing lists over the past 5 (maybe even 7?) years talking about the utter mess that is filesystem/device/geom/blahblah labels that to recommend this is borderline insane. Yes, the amount of different, present (in parallel) and differently implemented and accessible labeling mechanisms can be confusing. There is no the one true way to do it. Especially when dealing with metadata (e. g. for rare cases of data recovery) it might make things more complicated. I don't agree that labels in general do nothing but confuse the user - the same could be said about controllers, devices and how they are partitioned (again, many different ways here). But users usually don't deal with that. Sysadmins do. And they should be able to deal with it, as it's not _that_ complicated (from their educated and experienced point of view, I assume). That's why I would still say labels have their place, especially in settings with many disks (10 and more) where concluding which disk? is sometimes required, in terms of disk, not disk _bay_. The proper way to solve this problem is to user /boot/loader.conf tie-downs to assign each disk to each individual controllers' device number (e.g. ada0 -- scbus0 -- ahcich0, or whatever you want). Please note I said ahcichX, not ahciX. Different things. I have helped others in the past do this; Randy Bush is one such person. Taken directly from my /boot/loader.conf with a single SATA controller, but obviously this can be adjusted to whatever you want. # Wire down device names (ada[0-5]) to each individual port # on the SATA/AHCI controller. This ensures that if we reboot # with a disk missing, the device names stay the same, and stay # attached to the same SATA/AHCI controller. # http://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html # hint.scbus.0.at=ahcich0 hint.scbus.1.at=ahcich1 hint.scbus.2.at=ahcich2 hint.scbus.3.at=ahcich3 hint.scbus.4.at=ahcich4 hint.scbus.5.at=ahcich5 hint.ada.0.at=scbus0 hint.ada.1.at=scbus1 hint.ada.2.at=scbus2 hint.ada.3.at=scbus3 hint.ada.4.at=scbus4 hint.ada.5.at=scbus5 That's a very nice contribution to the topic - I hadn't thought it was that easy, and it actually solves the who comes first kind of problems. See CAM(4) man page (read it, don't skim!) for full details. Just please for the love of god do not use labels to solve this. Thanks, this contains inspiration of maybe how to make access to USB devices and memory card readers more efficient (i. e. making sure they are always represented by one and the same device, instead of the next free one). -- 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: Strange I/O problem on Freenas 0.7.2
Freenas 0.7.2 is old. Is write cache enable? http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-disk.html Is ZFS in use? ZFS has a value for tuning. On 22.10.2012 07:34, Henti Smith wrote: Hi all. I'm having a very weird problem with a friends Freenas set-up. I'm trying to backup his data before migrating to nas4free or just plain FreeBSD. The setup is as follows: HP Microserver N36. 2BG Mem (1713 MB Usable) (no swap) 4 x 2000GB (ST2000DL003-9VT166 Seagate) drives in a graid5 setup. Initially he had no problems with the setup. Samba share was fine and he populated the raid set with 3TB of data, but somewhere along the line the disk I/O went VERY slow. I initially thought this might be raid related and did some tests but actually found the problem to be on the discs. [root@freenas ~]# diskinfo -c /dev/ad4 /dev/ad4 512 # sectorsize 2000398934016 # mediasize in bytes (1.8T) 3907029168 # mediasize in sectors 3876021 # Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. ad:5YD2VEWQ # Disk ident. I/O command overhead: time to read 10MB block 0.250736 sec =0.012 msec/sector time to read 20480 sectors 79.653738 sec =3.889 msec/sector calculated command overhead =3.877 msec/sector [root@freenas ~]# diskinfo -t /dev/ad4 /dev/ad4 512 # sectorsize 2000398934016 # mediasize in bytes (1.8T) 3907029168 # mediasize in sectors 3876021 # Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. ad:5YD2VEWQ # Disk ident. Seek times: Full stroke: 250 iter in 124.649884 sec = 498.600 msec Half stroke: 250 iter in 52.112172 sec = 208.449 msec Quarter stroke: 500 iter in 167.991252 sec = 335.983 msec Short forward:400 iter in 72.027133 sec = 180.068 msec Short backward: 400 iter in 150.708625 sec = 376.772 msec Seq outer: 2048 iter in 5.748059 sec =2.807 msec Seq inner: 2048 iter in 119.395823 sec = 58.299 msec Transfer rates: outside: 102400 kbytes in 39.207296 sec = 2612 kbytes/sec middle:102400 kbytes in 113.757181 sec = 900 kbytes/sec inside:102400 kbytes in 153.438159 sec = 667 kbytes/sec S.M.A.R.T. is not reporting any issues either and the speeds are similar on all the drives. No errors in /var/log either. Any help or suggestions would be appreciated. Regards Henti ___ 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: ata controller problem
On Fri, Oct 26, 2012 at 06:43:28PM +0200, Polytropon wrote: I wish people would stop recommending this utter garbage. There is absolutely no justification behind using the highly convoluted labelling mechanisms at multiple layers within FreeBSD. There are 3 (possibly 4) different label mechanisms which do nothing but confuse the user, or cause other oddities/complexities. Good grief, there is so much hard evidence on the mailing lists over the past 5 (maybe even 7?) years talking about the utter mess that is filesystem/device/geom/blahblah labels that to recommend this is borderline insane. Yes, the amount of different, present (in parallel) and differently implemented and accessible labeling mechanisms can be confusing. There is no the one true way to do it. Especially when dealing with metadata (e. g. for rare cases of data recovery) it might make things more complicated. I don't agree that labels in general do nothing but confuse the user - the same could be said about controllers, devices and how they are partitioned (again, many different ways here). But users usually don't deal with that. Sysadmins do. And they should be able to deal with it, as it's not _that_ complicated (from their educated and experienced point of view, I assume). That's why I would still say labels have their place, especially in settings with many disks (10 and more) where concluding which disk? is sometimes required, in terms of disk, not disk _bay_. Let me make myself extra clear here -- and I won't be replying past this point (privately or publicly): What the OP wanted was to have a static mapping between a physical SATA port (e.g. Card #1 Port #0) and a device name (e.g. ada0) -- one which never changes no matter if there's a disk attached to the port or not. The wire-down method described above does this. Using labels does not. Here's a list of the wonderful fun things labels offer: - You get to remember or write down the label; don't forget it - You get to change /etc/fstab - You get to pray you never have to replace a disk, and if you do, that you remember which labelling method you used, and/or deal with partitioning complexities (see last item) - You get to be subjected to bugs in the GEOM layer or UFS layer when it comes to labels (this has happened!) - If using GPT (the only present way to align a partition properly to a 1MByte boundary -- matters greatly for SSDs due to NAND erase page size!), you're subjected to the problem where GEOM stores its metadata in the last sector, which is also where GPT stores its backup table. This is even documented in the Handbook, which is both good *and* hilarious at the same time And don't forget about the automatic vs. manual GEOM label method (but for this case I'm assuming automatic is used, since that method stores metadata). Every one of these situations has happened to at least one person in the past 5 (7?) years. They CONTINUE to happen. It cannot be denied. We FreeBSD users way too often shove our fingers into our ears and yell LALALA when people point out shortcomings. Blind advocacy of any kind of technology these days is something to be wary of. All that said: labels have a very, very specific purpose, backed by a list of many caveats. But I want to ensure controller port X maps to device X at all times is not one of those purposes. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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: Problem with libpng + Mozilla applications on FreeBSD 8.3
Hello Polytropon, Thanks for replying. Maybe an update of FF and TB would be sufficient, so it can link to the present (or at least expected) libraries accordingly. Maybe I did not make it clear enough in the original message. The only thing I installed from the installation DVD was the OS and the GNOME2 metaport. Everything else including FF and TB was installed from ports, the tarball of which I downloaded just a couple of days back. I hope you are not suggesting that I build the GNOME2 metaport too from the ports directory : with my internet connection, that really would take me into the next century. You should not manually copy things. At some point, something will crash, and the ports infrastructure cannot take care of it. It's easier to use a port management tool (like portmaster) to deal with installing and updating of ports. For the present issue, it seems logical that I would need 2 versions of libpng : one for GNOME and one for the ports being installed. Having the two versions reside independently in /usr/lib and /usr/local/lib seems to be the only way out. I still must admit that it defeats the purpose of having port management tools. I suspect that there might be folks at Mozilla who might see the light at the end of the tunnel (and the images on their buttons). I'll try roping them in with a separate message. If anything useful comes up, I'll post it to freebsd-questions as a message of possible interest to any other users who might be facing the same problem. Regards, Manish Jain bourne.ident...@hotmail.com ___ 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: Problem with libpng + Mozilla applications on FreeBSD 8.3
On Sat, 27 Oct 2012 00:06:44 +0530, Manish Jain wrote: Hello Polytropon, Thanks for replying. Maybe an update of FF and TB would be sufficient, so it can link to the present (or at least expected) libraries accordingly. Maybe I did not make it clear enough in the original message. The only thing I installed from the installation DVD was the OS and the GNOME2 metaport. Everything else including FF and TB was installed from ports, the tarball of which I downloaded just a couple of days back. I hope you are not suggesting that I build the GNOME2 metaport too from the ports directory : with my internet connection, that really would take me into the next century. Exactly that would have been the preferred solution. :-) You should not manually copy things. At some point, something will crash, and the ports infrastructure cannot take care of it. It's easier to use a port management tool (like portmaster) to deal with installing and updating of ports. For the present issue, it seems logical that I would need 2 versions of libpng : one for GNOME and one for the ports being installed. Having the two versions reside independently in /usr/lib and /usr/local/lib seems to be the only way out. I still must admit that it defeats the purpose of having port management tools. It also blurs the line between OS (/usr/lib) and additional software (/usr/local/lib) directories. However, both directories are used by the linker, so it looks possible (and probably better than messing with symlinks in /usr/local/lib). Problems _might_ occur when updating world. -- 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: ata controller problem
On Fri, 26 Oct 2012, Jeremy Chadwick wrote: Regarding this: http://lists.freebsd.org/pipermail/freebsd-questions/2012-October/245862.html No no NO *NO*! I wish people would stop recommending this utter garbage. There is absolutely no justification behind using the highly convoluted labelling mechanisms at multiple layers within FreeBSD. There are 3 (possibly 4) different label mechanisms which do nothing but confuse the user, or cause other oddities/complexities. Good grief, there is so much hard evidence on the mailing lists over the past 5 (maybe even 7?) years talking about the utter mess that is filesystem/device/geom/blahblah labels that to recommend this is borderline insane. Hmm. Six months to April 1? Seriously, labels provide a simple, relocatable identification mechanism that works across machines. If someone finds them confusing, it can be cleared up easily: use GPT labels when possible, otherwise use filesystem labels or glabel. The proper way to solve this problem is to user /boot/loader.conf tie-downs to assign each disk to each individual controllers' device number (e.g. ada0 -- scbus0 -- ahcich0, or whatever you want). Please note I said ahcichX, not ahciX. Different things. Labels work on different machines or controllers without added configuration, and stay with the partition or filesystem. Your static config appears to not share those properties. ___ 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: ata controller problem
Hi, On Fri, 26 Oct 2012 09:33:38 -0700 Jeremy Chadwick j...@koitsu.org wrote: Regarding this: http://lists.freebsd.org/pipermail/freebsd-questions/2012-October/245862.html No no NO *NO*! YES, YES, YES, YES! The proper way to solve this problem is to user /boot/loader.conf How does this help when media is moved between machines? Erich ___ 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
Gimp - problem opening images using URI's
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
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
'svn up' problem on amd64
Hello, Advice? I have not seen this before: (685) @ 2:22:16 cd /usr/src (686) @ 2:22:18 svn up Updating '.': Skipped 'sys' -- Node remains in conflict At revision 241794. Summary of conflicts: Skipped paths: 1 (687) @ 2:22:43 - more background information: ZFS Subsystem ReportSun Oct 21 02:32:36 2012 System Information: Kernel Version: 901000 (osreldate) Hardware Platform: amd64 Processor Architecture: amd64 ZFS Storage pool Version: 28 ZFS Filesystem Version: 5 FreeBSD 9.1-RC2 #0 r241106: Mon Oct 1 18:26:44 UTC 2012 root 2:32AM up 4 days, 18:32, 7 users, load averages: 0.14, 0.10, 0.08 Darrel ___ 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: 'svn up' problem on amd64
On 21/10/2012 07:35, Darrel wrote: Advice? I have not seen this before: (685) @ 2:22:16 cd /usr/src (686) @ 2:22:18 svn up Updating '.': Skipped 'sys' -- Node remains in conflict At revision 241794. Summary of conflicts: Skipped paths: 1 (687) @ 2:22:43 For some reason svn thinks your local copy of sys conflicts with the copy from the repo. That could happen if you have local patches or similar, but svn would usually prompt you to merge any such. Also this seems to have affected people completely innocent of any such changes. Assuming you've checked out the stable/9 branch then I think this (untested) command should resolve the problems: # cd /usr/src # svn merge --accept theirs-full ^/stable/9 Use 'svn info' to see what the URL setting for your repo is -- you can just paste that in as is instead of '^/stable/9', or you can use the shorthand '^' which stands for the text from the 'Repository Root' setting plus the rest of the URL string. Note that the 'theirs-full' method of resolving conflicts will tend to wipe out any local changes you may have. If that is a concern, then you could try using the 'edit' method instead. (As the name suggests, this puts you in an editor showing the conflicting merge results, and requires you to edit things into what the result of the mmerge should have been.) Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Strange I/O problem on Freenas 0.7.2
Hi all. I'm having a very weird problem with a friends Freenas set-up. I'm trying to backup his data before migrating to nas4free or just plain FreeBSD. The setup is as follows: HP Microserver N36. 2BG Mem (1713 MB Usable) (no swap) 4 x 2000GB (ST2000DL003-9VT166 Seagate) drives in a graid5 setup. Initially he had no problems with the setup. Samba share was fine and he populated the raid set with 3TB of data, but somewhere along the line the disk I/O went VERY slow. I initially thought this might be raid related and did some tests but actually found the problem to be on the discs. [root@freenas ~]# diskinfo -c /dev/ad4 /dev/ad4 512 # sectorsize 2000398934016 # mediasize in bytes (1.8T) 3907029168 # mediasize in sectors 3876021 # Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. ad:5YD2VEWQ # Disk ident. I/O command overhead: time to read 10MB block 0.250736 sec =0.012 msec/sector time to read 20480 sectors 79.653738 sec =3.889 msec/sector calculated command overhead =3.877 msec/sector [root@freenas ~]# diskinfo -t /dev/ad4 /dev/ad4 512 # sectorsize 2000398934016 # mediasize in bytes (1.8T) 3907029168 # mediasize in sectors 3876021 # Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. ad:5YD2VEWQ # Disk ident. Seek times: Full stroke: 250 iter in 124.649884 sec = 498.600 msec Half stroke: 250 iter in 52.112172 sec = 208.449 msec Quarter stroke: 500 iter in 167.991252 sec = 335.983 msec Short forward:400 iter in 72.027133 sec = 180.068 msec Short backward: 400 iter in 150.708625 sec = 376.772 msec Seq outer: 2048 iter in 5.748059 sec =2.807 msec Seq inner: 2048 iter in 119.395823 sec = 58.299 msec Transfer rates: outside: 102400 kbytes in 39.207296 sec = 2612 kbytes/sec middle:102400 kbytes in 113.757181 sec = 900 kbytes/sec inside:102400 kbytes in 153.438159 sec = 667 kbytes/sec S.M.A.R.T. is not reporting any issues either and the speeds are similar on all the drives. No errors in /var/log either. Any help or suggestions would be appreciated. Regards Henti ___ 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: Problem upgrading
On Wed, Oct 17, 2012 at 02:14:10PM -0700, Timothy Snowberger wrote: On 10/17/2012 7:27 AM, Jim Trigg wrote: Any suggestions on how to fix this? --- argent(1) /usr/ports/ports-mgmt/portmaster# freebsd-update -r 9.0-RELEASE upgrade Does this look reasonable (y/n)? y ... Fetching metadata signature for 9.0-RELEASE from update5.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. The update metadata is correctly signed, but failed an integrity check. Cowardly refusing to proceed any further. sed -i '' -e 's/=_/=%@_/' /usr/sbin/freebsd-update See http://lists.freebsd.org/pipermail/freebsd-stable/2011-October/064321.html First, a minor change must be made to the freebsd-update code in order for it to accept file names appearing in FreeBSD 9.0 which contain the '%' and '@' characters; without this change, freebsd-update will error out with the message The update metadata is correctly signed, but failed an integrity check. This fixed it. Thanks, Jim ___ 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
Problem upgrading
Any suggestions on how to fix this? --- argent(1) /usr/ports/ports-mgmt/portmaster# freebsd-update -r 9.0-RELEASE upgrade Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata signature for 8.2-RELEASE from update5.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata files... done. Inspecting system... done. The following components of FreeBSD seem to be installed: kernel/generic src/base src/bin src/cddl src/contrib src/crypto src/etc src/games src/gnu src/include src/krb5 src/lib src/libexec src/release src/rescue src/sbin src/secure src/share src/sys src/tools src/ubin src/usbin world/base world/dict world/doc world/games world/info world/manpages world/proflibs The following components of FreeBSD do not seem to be installed: world/catpages Does this look reasonable (y/n)? y Fetching metadata signature for 9.0-RELEASE from update5.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. The update metadata is correctly signed, but failed an integrity check. Cowardly refusing to proceed any further. --- Thanks, Jim ___ 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: Problem upgrading
On 10/17/2012 7:27 AM, Jim Trigg wrote: Any suggestions on how to fix this? --- argent(1) /usr/ports/ports-mgmt/portmaster# freebsd-update -r 9.0-RELEASE upgrade Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata signature for 8.2-RELEASE from update5.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata files... done. Inspecting system... done. The following components of FreeBSD seem to be installed: kernel/generic src/base src/bin src/cddl src/contrib src/crypto src/etc src/games src/gnu src/include src/krb5 src/lib src/libexec src/release src/rescue src/sbin src/secure src/share src/sys src/tools src/ubin src/usbin world/base world/dict world/doc world/games world/info world/manpages world/proflibs The following components of FreeBSD do not seem to be installed: world/catpages Does this look reasonable (y/n)? y Fetching metadata signature for 9.0-RELEASE from update5.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. The update metadata is correctly signed, but failed an integrity check. Cowardly refusing to proceed any further. --- Thanks, Jim ___ 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 sed -i '' -e 's/=_/=%@_/' /usr/sbin/freebsd-update See http://lists.freebsd.org/pipermail/freebsd-stable/2011-October/064321.html First, a minor change must be made to the freebsd-update code in order for it to accept file names appearing in FreeBSD 9.0 which contain the '%' and '@' characters; without this change, freebsd-update will error out with the message The update metadata is correctly signed, but failed an integrity check. ___ 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: geforce 310m CUDA problem
On 08/10/2012 16:24, Ashkan Rahmani wrote: Unfortunately (for me of course) it has geforce 310m cuda 1gb VGA, and it seems this VGA is not supported by FreeBSD. After installing FreeBSD/PC-BSD resolution is about 800x600 and I can not change it. Color depth is also terrible. Configuring xorg.conf automatically or manually can not fix my problem. installing nvidia driver from ports also can not fix my problem. some ideas -- The release notes for nvidia-driver 304.51 lists the 310M as supported. Check that you have the latest version Maybe try with driver nv instead of nvidia to see if the issue is the driver. kldstat | grep nvidia to check that the nvidia kernel module has loaded. Is there any helpful info in Xorg.0.log Lines starting with (EE) are errors. (WW) warning lines may also be helpful. dmesg will show the startup log and may highlight any hardware detection problems. Have you installed x11/nvidia-settings? It is a gui app that should show you all available resolutions. The Xorg.conf from your archlinux install should produce the same results on FreeBSD. Or at least give hints to what is configured wrong. There is a chance that your linux install used a newer version of xorg - 1.7 is default in ports but you can set WITH_NEW_XORG to build 1.10 ___ 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
geforce 310m CUDA problem
hi I'm really interesting to switch from Linux to FreeBSD for my personal use. Currently I'm using Archlinux on my Asus K52J notebook. Unfortunately (for me of course) it has geforce 310m cuda 1gb VGA, and it seems this VGA is not supported by FreeBSD. After installing FreeBSD/PC-BSD resolution is about 800x600 and I can not change it. Color depth is also terrible. Configuring xorg.conf automatically or manually can not fix my problem. installing nvidia driver from ports also can not fix my problem. Notebook has NVIDIA Optimus technology and I don't know may be it's source of my problem or not. anybody know how I can solve this problem!? PS: my friend has a dell 1555 notebook, and FreeBSD work nice and soft on it! VGA is nvidia. my very old notebook (acer) has ATI vga and FreeBSD work well too! --- Best Regards, Ashkan R ___ 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
