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
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
Problem with freebsd-update
I tried to update an amd64 FreeBSD 9.0 p0 system via freebsd-update tonight. It fetched everything fine. However, the install just hung after about 10 minutes. The 2 sh processes are basically doing nothing. Not consuming any processor time and not doing any I/O. I killed it and tried another install. Same thing. Tried a rollback. Same thing. The system still runs mostly. Top takes about 5 minutes before it produces any output. It shows basically nothing running. I really don't want to reinstall again as the system has a lot of files customized including many ports. Is there any way to recover 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 with freebsd-update on 7.3-RELEASE
27.01.2011 15:19, Konstantin Vasilyev пишет: Ok. Things a not good :-( freebsd-update produce a lot of output like this /usr/src/sys/kern/uipc_mbuf.c has SHA256 hash 893beadfcf15784f31553ea142867c2949422d6937cb61f11a0f42ae3d7727fc, but should have SHA256 hash ce374f0d9434d08ee35769f8cbad7ca074506b814394b30d19d2aebcf3b2a29c. /usr/src/sys/nfsclient/nfs_vfsops.c has SHA256 hash 7a69b307a5df13994c8c229946e3f20cdb22268ca967f596c70477c82250c7d2, but should have SHA256 hash 397e464eea58b339597b4a3ee6117ad9b58827814462131153070c2a067e357d. /usr/src/sys/nfsclient/nfs_vfsops.c has SHA256 hash 7a69b307a5df13994c8c229946e3f20cdb22268ca967f596c70477c82250c7d2, but should have SHA256 hash c54c0c265e22fdb7a323680ccbc25859fc171ebec485a68a06eae774683321ab. /usr/src/usr.bin/lex/mkskel.sh has 0755 permissions, but should have 0744 permissions. /usr/src/usr.sbin/pkg_install/tkpkg has 0755 permissions, but should have 0754 permissions. My system is out of sync now. Question is How can I sync my system? -- With best regards, Konstantin Vasilyev 27.01.2011 12:31, Brian DeFreitas пишет: Konstantin Vasilyev wrote: I know about how freedsd-update work. I use for a long time. But I don't understand why is freebsd-update going to update FreeBSD ota2.cellnetrix.com 7.3-RELEASE-p4 FreeBSD 7.3-RELEASE-p4 to The following files will be updated as part of updating to 7.3-RELEASE-p4:... Ah, I see the problem now. The only thing I can think of is that your kernel and world might be out of sync, but if you're used to freebsd-update that seems unlikely. What's the output of 'freebsd-update IDS' ? I've had luck running that to see what freebsd-update thinks is going on with the system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ 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 I'm trying to refresh post. Please give me an idea how to make my system updatable via freebsd-update. -- With best regards, Konstantin Vasilyev ___ 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 freebsd-update on 7.3-RELEASE
Konstantin Vasilyev wrote: Hi all! I have installed %uname -a FreeBSD ota2.cellnetrix.com 7.3-RELEASE-p4 FreeBSD 7.3-RELEASE-p4 #3: Tue Jan 25 19:19:34 MSK 2011 kvasi...@ota2.cellnetrix.com:/usr/obj/usr/src/sys/GENERIC i386 I have @dailyfreebsd-update cron in root's crontab. Why does freebsd-update mail me the following? [...] Who can give me ideas what's happening? Have you checked the man page for freebsd-update(8) ? cron Sleep a random amount of time between 1 and 3600 seconds, then download updates as if the fetch command was used. If updates are downloaded, an email will be sent (to root or a different address if specified via the -t option or in the configuration file). Sounds exactly like the expected behavior to me. So, the cron subcommand only does the 'fetch' part of freebsd-update. You'll still need to run 'freebsd-update install' to actually install the updates. ___ 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 freebsd-update on 7.3-RELEASE
I know about how freedsd-update work. I use for a long time. But I don't understand why is freebsd-update going to update FreeBSD ota2.cellnetrix.com 7.3-RELEASE-p4 FreeBSD 7.3-RELEASE-p4 to The following files will be updated as part of updating to 7.3-RELEASE-p4:... -- With best regards, Konstantin Vasilyev 27.01.2011 10:56, Brian DeFreitas пишет: Konstantin Vasilyev wrote: Hi all! I have installed %uname -a FreeBSD ota2.cellnetrix.com 7.3-RELEASE-p4 FreeBSD 7.3-RELEASE-p4 #3: Tue Jan 25 19:19:34 MSK 2011 kvasi...@ota2.cellnetrix.com:/usr/obj/usr/src/sys/GENERIC i386 I have @daily freebsd-update cron in root's crontab. Why does freebsd-update mail me the following? [...] Who can give me ideas what's happening? Have you checked the man page for freebsd-update(8) ? cron Sleep a random amount of time between 1 and 3600 seconds, then download updates as if the fetch command was used. If updates are downloaded, an email will be sent (to root or a different address if specified via the -t option or in the configuration file). Sounds exactly like the expected behavior to me. So, the cron subcommand only does the 'fetch' part of freebsd-update. You'll still need to run 'freebsd-update install' to actually install the updates. ___ 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: Problem with freebsd-update on 7.3-RELEASE
Konstantin Vasilyev wrote: I know about how freedsd-update work. I use for a long time. But I don't understand why is freebsd-update going to update FreeBSD ota2.cellnetrix.com 7.3-RELEASE-p4 FreeBSD 7.3-RELEASE-p4 to The following files will be updated as part of updating to 7.3-RELEASE-p4:... Ah, I see the problem now. The only thing I can think of is that your kernel and world might be out of sync, but if you're used to freebsd-update that seems unlikely. What's the output of 'freebsd-update IDS' ? I've had luck running that to see what freebsd-update thinks is going on with the system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problem with freebsd-update on 7.3-RELEASE
Ok. Things a not good :-( freebsd-update produce a lot of output like this /usr/src/sys/kern/uipc_mbuf.c has SHA256 hash 893beadfcf15784f31553ea142867c2949422d6937cb61f11a0f42ae3d7727fc, but should have SHA256 hash ce374f0d9434d08ee35769f8cbad7ca074506b814394b30d19d2aebcf3b2a29c. /usr/src/sys/nfsclient/nfs_vfsops.c has SHA256 hash 7a69b307a5df13994c8c229946e3f20cdb22268ca967f596c70477c82250c7d2, but should have SHA256 hash 397e464eea58b339597b4a3ee6117ad9b58827814462131153070c2a067e357d. /usr/src/sys/nfsclient/nfs_vfsops.c has SHA256 hash 7a69b307a5df13994c8c229946e3f20cdb22268ca967f596c70477c82250c7d2, but should have SHA256 hash c54c0c265e22fdb7a323680ccbc25859fc171ebec485a68a06eae774683321ab. /usr/src/usr.bin/lex/mkskel.sh has 0755 permissions, but should have 0744 permissions. /usr/src/usr.sbin/pkg_install/tkpkg has 0755 permissions, but should have 0754 permissions. My system is out of sync now. Question is How can I sync my system? -- With best regards, Konstantin Vasilyev 27.01.2011 12:31, Brian DeFreitas пишет: Konstantin Vasilyev wrote: I know about how freedsd-update work. I use for a long time. But I don't understand why is freebsd-update going to update FreeBSD ota2.cellnetrix.com 7.3-RELEASE-p4 FreeBSD 7.3-RELEASE-p4 to The following files will be updated as part of updating to 7.3-RELEASE-p4:... Ah, I see the problem now. The only thing I can think of is that your kernel and world might be out of sync, but if you're used to freebsd-update that seems unlikely. What's the output of 'freebsd-update IDS' ? I've had luck running that to see what freebsd-update thinks is going on with the system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ 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 freebsd-update on 7.3-RELEASE
Hi all! I have installed %uname -a FreeBSD ota2.cellnetrix.com 7.3-RELEASE-p4 FreeBSD 7.3-RELEASE-p4 #3: Tue Jan 25 19:19:34 MSK 2011 kvasi...@ota2.cellnetrix.com:/usr/obj/usr/src/sys/GENERIC i386 I have @daily freebsd-update cron in root's crontab. Why does freebsd-update mail me the following? Looking up update.FreeBSD.org mirrors... 4 mirrors found. Fetching metadata signature for 7.3-RELEASE from update4.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. The following files are affected by updates, but no changes have been downloaded because the files have been modified locally: /var/db/mergemaster.mtree The following files will be updated as part of updating to 7.3-RELEASE-p4: /boot/kernel/kernel /boot/kernel/kernel.symbols /boot/kernel/nfsclient.ko /boot/kernel/nfsclient.ko.symbols /usr/lib/libbz2.a /usr/lib/libbz2_p.a /usr/lib/libopie.a /usr/lib/libopie_p.a /usr/lib/libssl.a /usr/lib/libssl_p.a /usr/lib/libstand.a /usr/share/man/man2/mount.2.gz /usr/share/man/man2/nmount.2.gz /usr/share/man/man2/unmount.2.gz /usr/src/contrib/opie/libopie/readrec.c /usr/src/lib/libc/sys/mount.2 /usr/src/sys/conf/newvers.sh /usr/src/sys/kern/uipc_mbuf.c /usr/src/sys/nfsclient/nfs_vfsops.c Who can give me ideas what's happening? -- With best regards, Konstantin Vasilyev ___ 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 freebsd-update-upgrade.tgz.asc
Hi, I have downloaded the above script from http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html Installed gpg all set up ok AFAICT. put the freebsd security officer's public key on my gpg keyring . Used the following command to verify the file: localhost# gpg --verify freebsd-update-upgrade.tgz.asc freebsd-update-upgrade.tgz gpg: can't open signed data `freebsd-update-upgrade.tgz' gpg: can't hash datafile: No such file or directory localhost# AFAICT the public key is ok pub 1024D/CA6CDFB2 2002-08-27 uid FreeBSD Security Officer [EMAIL PROTECTED] sub 2048g/A3071809 2002-08-27 Apart from the fact that the file could be dodgy (?) What could be the problem? Have I used the wrong key? I imagine the error msg would be different if that was the case. Thanks, Alasdair ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem with freebsd-update
Hello freebsd-questions, I need to update mpd4 binary package via freebsd-update. After installing FreeBSD 6.2 RELEASE I have mpd4-4.0b4. Settings in /etc/freebsd-update.conf: Components src world kernel After running commands freebsd-update fetch, then freebsd-update install I still have the same mpd4-4.0b4 version. I saw in http://www.freebsd.org/cgi/ports.cgi?query=mpdstype=all that the last version is mpd-4.1 ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/All/mpd-4.1.tbz How can I upgrade to the last packages versions with freebsd-update? -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with freebsd-update
Dmitry wrote: Hello freebsd-questions, I need to update mpd4 binary package via freebsd-update. After installing FreeBSD 6.2 RELEASE I have mpd4-4.0b4. Settings in /etc/freebsd-update.conf: Components src world kernel After running commands freebsd-update fetch, then freebsd-update install I still have the same mpd4-4.0b4 version. I saw in http://www.freebsd.org/cgi/ports.cgi?query=mpdstype=all that the last version is mpd-4.1 ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/All/mpd-4.1.tbz How can I upgrade to the last packages versions with freebsd-update? maybe I am wrong here, but isnt mpd4 a port? Freebsd-update is for the base system, not ports, so it wont be able to update the mpd4 port. Try portsnap and portmaster to update your ports. Eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
