Re: Something since June 8th clobbers my disk...
On Friday 12 June 2009 08:24:42 pm Gary Kline wrote: On Fri, Jun 12, 2009 at 08:45:01PM -0600, Dan Allen wrote: On 12 Jun 2009, at 6:32 AM, John Baldwin wrote: On Thursday 11 June 2009 9:33:24 pm Dan Allen wrote: Whew!! i'm giving thanks to every saint, god and daemon known. i rebuilt my kernel in very recent days (7.2) on my ancient 500MHz kayak, but did not go further. So still runing on the 7.0 kernel. Will someone send up a flare when it's *safe*? gary Gary, it isn't affecting everyone. FreeBSD ruby.owt.com 7.2-STABLE FreeBSD 7.2-STABLE #4: Wed Jun 10 14:07:14 PDT 2009 r...@ruby.owt.com:/usr/obj/usr/src/sys/FREEBSD2 i386 FreeBSD kstewart2.owt.com 7.2-STABLE FreeBSD 7.2-STABLE #6: Wed Jun 10 15:03:03 PDT 2009 r...@kstewart2.owt.com:/usr/obj/usr/src/sys/FREEBSD1 i386 Ruby is an Intel core duo and the other has dual Xeon's. They were all installed the canonical way. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Something since June 8th clobbers my disk...
On Fri, Jun 12, 2009 at 11:24:07PM -0700, Kent Stewart wrote: On Friday 12 June 2009 08:24:42 pm Gary Kline wrote: On Fri, Jun 12, 2009 at 08:45:01PM -0600, Dan Allen wrote: On 12 Jun 2009, at 6:32 AM, John Baldwin wrote: On Thursday 11 June 2009 9:33:24 pm Dan Allen wrote: Whew!! i'm giving thanks to every saint, god and daemon known. i rebuilt my kernel in very recent days (7.2) on my ancient 500MHz kayak, but did not go further. So still runing on the 7.0 kernel. Will someone send up a flare when it's *safe*? gary Gary, it isn't affecting everyone. FreeBSD ruby.owt.com 7.2-STABLE FreeBSD 7.2-STABLE #4: Wed Jun 10 14:07:14 PDT 2009 r...@ruby.owt.com:/usr/obj/usr/src/sys/FREEBSD2 i386 FreeBSD kstewart2.owt.com 7.2-STABLE FreeBSD 7.2-STABLE #6: Wed Jun 10 15:03:03 PDT 2009 r...@kstewart2.owt.com:/usr/obj/usr/src/sys/FREEBSD1 i386 Ruby is an Intel core duo and the other has dual Xeon's. They were all installed the canonical way. Thanks for the insight, Kent. I'll go ahead and install 7.2 on the P3, then. Should be done this weekend. gary Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org For FBSD list: http://transfinite.thought.org/slicejourney.php The 4.98a release of Jottings: http://jottings.thought.org/index.php ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Something since June 8th clobbers my disk...
On Saturday 13 June 2009 12:08:17 am Gary Kline wrote: On Fri, Jun 12, 2009 at 11:24:07PM -0700, Kent Stewart wrote: On Friday 12 June 2009 08:24:42 pm Gary Kline wrote: On Fri, Jun 12, 2009 at 08:45:01PM -0600, Dan Allen wrote: On 12 Jun 2009, at 6:32 AM, John Baldwin wrote: On Thursday 11 June 2009 9:33:24 pm Dan Allen wrote: Whew!! i'm giving thanks to every saint, god and daemon known. i rebuilt my kernel in very recent days (7.2) on my ancient 500MHz kayak, but did not go further. So still runing on the 7.0 kernel. Will someone send up a flare when it's *safe*? gary Gary, it isn't affecting everyone. FreeBSD ruby.owt.com 7.2-STABLE FreeBSD 7.2-STABLE #4: Wed Jun 10 14:07:14 PDT 2009 r...@ruby.owt.com:/usr/obj/usr/src/sys/FREEBSD2 i386 FreeBSD kstewart2.owt.com 7.2-STABLE FreeBSD 7.2-STABLE #6: Wed Jun 10 15:03:03 PDT 2009 r...@kstewart2.owt.com:/usr/obj/usr/src/sys/FREEBSD1 i386 Ruby is an Intel core duo and the other has dual Xeon's. They were all installed the canonical way. Thanks for the insight, Kent. I'll go ahead and install 7.2 on the P3, then. Should be done this weekend. Coming from the diagnostic side in the days of our Cray, I believe that one broken machine means more than 100 without problems. There just seems to be more to this than is normal. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Something since June 8th clobbers my disk...
On 12 Jun 2009, at 9:50 PM, Yuri Pankov wrote: On Fri, Jun 12, 2009 at 08:24:42PM -0700, Gary Kline wrote: Whew!! i'm giving thanks to every saint, god and daemon known. i rebuilt my kernel in very recent days (7.2) on my ancient 500MHz kayak, but did not go further. So still runing on the 7.0 kernel. Will someone send up a flare when it's *safe*? How do you know it isn't safe? Noone hasn't provided any useful info (debug, revisions where it works and where it doesn't). Well, I do not think it is safe at all either. I must have some strange configuration that others do not have or there would be plenty of people with their drives getting wiped out. I tried removing the zfsboot and gptzfsboot items from /usr/src/sys/ boot/i386/Makefile and then rebuild the boot area but it once again killed things. My hunch is that the boot loader is getting stuck on something strange about my system. Here is my drive config, and perhaps this will cause a light bulb to go on for someone: Toshiba U205, Intel 1.83GHz Core Duo, 1GB RAM, 1 120GB hard drive with two partitions. The first partition is 92161 MB for Windows XP Pro. I rarely use it. The second partition is 22309 MB for FreeBSD. It has 3 slices: The first slice /dev/ad0s2a is the main 22 GB file system. It has the / root mount point and has soft updates turned on. The second slice /dev/ad0s2b is a 1GB SWAP partition. The third slice /dev/ad0s2c is unused. I will continue to test. I am TRYING to narrow it down, it just takes forever. Dan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Something since June 8th clobbers my disk...
On 11 Jun 2009, at 5:41 PM, Paul B. Mahol wrote: Looks like boot(8) is problematic. Okay, here is the June 13th noon update to this problem. I once again installed a May 28th build. Rebuilt world and kernel from source. Everything works great. No custom kernel, just GENERIC. I then merged in just /usr/src/sys/boot/i386/libi386 changes to June 10th. Rebuilt in /usr/src/sys/boot and installed it, no problem. Then I merged in the latest from /usr/src/sys/boot/i386/loader, rebuilt, installed, and BOOM. DEATH TO DRIVE. Disk label GONE again. Hangs after BIOS drive C: is disk1 at boot. Does not get to memory check, let alone to the Welcome to FreeBSD and choose a boot option screen. CULPRIT REVEALED: So, there is only one file change in /usr/src/sys/boot/i386/loader from June 8th to June 10th, which kills my machine very repeatably, and that is the Makefile. Something in /usr/src/sys/boot/i386/loader/Makefile is killing my drive. What do I try next? Thanks for the help. Dan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Something since June 8th clobbers my disk...
On 6/13/09, Dan Allen danalle...@airwired.net wrote: On 12 Jun 2009, at 6:32 AM, John Baldwin wrote: On Thursday 11 June 2009 9:33:24 pm Dan Allen wrote: Isn't boot part of the kernel build? Why would installing the kernel not cause this problem? No, sys/boot is built during world. Likely some change in /boot/ loader is causing your problem. Can you narrow it down to a specific change under sys/boot? Ok. I updated just the one file since it appeared like one of the few changed files /usr/src/sys/boot/i386/libi386/biosdisk.c and rebuilt things with cd /usr/src/sys/boot; make cleandir obj depend all install and it was okay. No problems. Then I did sync'd all of the changed files for /usr/src/sys/boot and my machine is hung again at boot, so we have narrowed it down to somewhere in /usr/src/sys/boot/. Time to reinstall from a DVD and try it with finer granularity. This will take some time. There appears to be only four files that have changed in /usr/src/sys/ boot from June 8th (all working fine) to June 11th (dead in the water). They are: /usr/src/sys/boot/Makefile /usr/src/sys/boot/i386/Makefile /usr/src/sys/boot/i386/libi386/biosdisk.c I doubt it is loader fault, from your description it appears that loader is never started. Could you try to remove -DLOADER_ZFS_SUPPORT from Makefile? /usr/src/sys/boot/i386/loader/Makefile I have ruled out bisodisk.c, as stated above. That means that the Makefiles are building new stuff that previously was not built, namely zfsboot gptzfsboot I believe it has to do with that. More help is needed! I am tired of reinstalling the OS, but I am much more paranoid about updating my other machine in any way now, as it could erase that whole machine. I can't believe I am the only one seeing this... Dan -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Something since June 8th clobbers my disk...
On 13 Jun 2009, at 12:50 PM, Paul B. Mahol wrote: I doubt it is loader fault, from your description it appears that loader is never started. Could you try to remove -DLOADER_ZFS_SUPPORT from Makefile? /usr/src/sys/boot/i386/loader/Makefile BINGO! LOADER_ZFS_SUPPORT is the culprit. I rebuilt the good world, and brought in the loader changes which have caused previously caused death to my drive, then deleted the ZFS_SUPPORT path in /usr/src/sys/boot/i386/loader/Makefile as you recommended, and rebuilt things and everything works fine. Now what do we do? Dan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Something since June 8th clobbers my disk...
On Sat, Jun 13, 2009 at 12:41:55PM -0600, Dan Allen wrote: On 11 Jun 2009, at 5:41 PM, Paul B. Mahol wrote: Looks like boot(8) is problematic. Okay, here is the June 13th noon update to this problem. I once again installed a May 28th build. Rebuilt world and kernel from source. Everything works great. No custom kernel, just GENERIC. I then merged in just /usr/src/sys/boot/i386/libi386 changes to June 10th. Rebuilt in /usr/src/sys/boot and installed it, no problem. Then I merged in the latest from /usr/src/sys/boot/i386/loader, rebuilt, installed, and BOOM. DEATH TO DRIVE. Disk label GONE again. Hangs after BIOS drive C: is disk1 at boot. Does not get to memory check, let alone to the Welcome to FreeBSD and choose a boot option screen. CULPRIT REVEALED: So, there is only one file change in /usr/src/sys/boot/i386/loader from June 8th to June 10th, which kills my machine very repeatably, and that is the Makefile. Something in /usr/src/sys/boot/i386/loader/Makefile is killing my drive. What do I try next? Thanks for the help. Dan I just checked the timestamped on my i386/loader/Makefile. The CVS/RCS v that may show you something is from 07jun09: 1.85.2.4 and if you find what changed between your working build on 28may and failing build, that might isolate it. just my dime's worth :-) gary ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org For FBSD list: http://transfinite.thought.org/slicejourney.php The 4.98a release of Jottings: http://jottings.thought.org/index.php ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Something since June 8th clobbers my disk...
On Thursday 11 June 2009 9:33:24 pm Dan Allen wrote: Isn't boot part of the kernel build? Why would installing the kernel not cause this problem? No, sys/boot is built during world. Likely some change in /boot/loader is causing your problem. Can you narrow it down to a specific change under sys/boot? -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Something since June 8th clobbers my disk...
On Thursday 11 June 2009 06:33:24 pm Dan Allen wrote: On 11 Jun 2009, at 5:41 PM, Paul B. Mahol wrote: Looks like boot(8) is problematic. Anything in /etc/src.conf or /etc/make.conf? I have never touched or created a src.conf. If there was one there, it has been unmodified by me. I HAVE modified make.conf. Here is its contents: --- /etc/make.conf --- BATCH=yes NO_PROFILE=yes KERNCONF=DKA USE_FORTRAN=yes WITH_JADETEX=no PERL_VERSION=5.8.9 --- My custom kernel named DKA has only three modifications from GENERIC: I commented out the following three lines: #cpu I486_CPU #cpu I586_CPU #makeoptions DEBUG=-g I have run with such a kernel on many machines for many years now. However, my experiments have shown that the kernel build is not to blame. Isn't boot part of the kernel build? Why would installing the kernel not cause this problem? It is by installing the world via make installworld that my drive gets munged. I obviously am missing something, but boot(8) sounds like it is in the neighborhood of where the problem is. There were changes to /usr/src/sys/boot/i386/libi386/biosdisk.c and biospnp.c that really look suspect to me. The order of your builds in previous messages had the kernel built on an old world. You are supposed to do the buildworld first and then, build and install the kernel. The classic way at this point is to boot into single user mode and do the installworld. Kent Dan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Something since June 8th clobbers my disk...
On 12 Jun 2009, at 6:32 AM, John Baldwin wrote: On Thursday 11 June 2009 9:33:24 pm Dan Allen wrote: Isn't boot part of the kernel build? Why would installing the kernel not cause this problem? No, sys/boot is built during world. Likely some change in /boot/ loader is causing your problem. Can you narrow it down to a specific change under sys/boot? Ok. I updated just the one file since it appeared like one of the few changed files /usr/src/sys/boot/i386/libi386/biosdisk.c and rebuilt things with cd /usr/src/sys/boot; make cleandir obj depend all install and it was okay. No problems. Then I did sync'd all of the changed files for /usr/src/sys/boot and my machine is hung again at boot, so we have narrowed it down to somewhere in /usr/src/sys/boot/. Time to reinstall from a DVD and try it with finer granularity. This will take some time. There appears to be only four files that have changed in /usr/src/sys/ boot from June 8th (all working fine) to June 11th (dead in the water). They are: /usr/src/sys/boot/Makefile /usr/src/sys/boot/i386/Makefile /usr/src/sys/boot/i386/libi386/biosdisk.c /usr/src/sys/boot/i386/loader/Makefile I have ruled out bisodisk.c, as stated above. That means that the Makefiles are building new stuff that previously was not built, namely zfsboot gptzfsboot I believe it has to do with that. More help is needed! I am tired of reinstalling the OS, but I am much more paranoid about updating my other machine in any way now, as it could erase that whole machine. I can't believe I am the only one seeing this... Dan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Something since June 8th clobbers my disk...
On Fri, Jun 12, 2009 at 08:45:01PM -0600, Dan Allen wrote: On 12 Jun 2009, at 6:32 AM, John Baldwin wrote: On Thursday 11 June 2009 9:33:24 pm Dan Allen wrote: Isn't boot part of the kernel build? Why would installing the kernel not cause this problem? No, sys/boot is built during world. Likely some change in /boot/ loader is causing your problem. Can you narrow it down to a specific change under sys/boot? Ok. I updated just the one file since it appeared like one of the few changed files /usr/src/sys/boot/i386/libi386/biosdisk.c and rebuilt things with cd /usr/src/sys/boot; make cleandir obj depend all install and it was okay. No problems. Then I did sync'd all of the changed files for /usr/src/sys/boot and my machine is hung again at boot, so we have narrowed it down to somewhere in /usr/src/sys/boot/. Time to reinstall from a DVD and try it with finer granularity. This will take some time. There appears to be only four files that have changed in /usr/src/sys/ boot from June 8th (all working fine) to June 11th (dead in the water). They are: /usr/src/sys/boot/Makefile /usr/src/sys/boot/i386/Makefile /usr/src/sys/boot/i386/libi386/biosdisk.c /usr/src/sys/boot/i386/loader/Makefile I have ruled out bisodisk.c, as stated above. That means that the Makefiles are building new stuff that previously was not built, namely zfsboot gptzfsboot I believe it has to do with that. More help is needed! I am tired of reinstalling the OS, but I am much more paranoid about updating my other machine in any way now, as it could erase that whole machine. I can't believe I am the only one seeing this... Dan Whew!! i'm giving thanks to every saint, god and daemon known. i rebuilt my kernel in very recent days (7.2) on my ancient 500MHz kayak, but did not go further. So still runing on the 7.0 kernel. Will someone send up a flare when it's *safe*? gary -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org For FBSD list: http://transfinite.thought.org/slicejourney.php The 4.98a release of Jottings: http://jottings.thought.org/index.php ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Something since June 8th clobbers my disk...
On Fri, Jun 12, 2009 at 08:24:42PM -0700, Gary Kline wrote: On Fri, Jun 12, 2009 at 08:45:01PM -0600, Dan Allen wrote: On 12 Jun 2009, at 6:32 AM, John Baldwin wrote: On Thursday 11 June 2009 9:33:24 pm Dan Allen wrote: Isn't boot part of the kernel build? Why would installing the kernel not cause this problem? No, sys/boot is built during world. Likely some change in /boot/ loader is causing your problem. Can you narrow it down to a specific change under sys/boot? Ok. I updated just the one file since it appeared like one of the few changed files /usr/src/sys/boot/i386/libi386/biosdisk.c and rebuilt things with cd /usr/src/sys/boot; make cleandir obj depend all install and it was okay. No problems. Then I did sync'd all of the changed files for /usr/src/sys/boot and my machine is hung again at boot, so we have narrowed it down to somewhere in /usr/src/sys/boot/. Time to reinstall from a DVD and try it with finer granularity. This will take some time. There appears to be only four files that have changed in /usr/src/sys/ boot from June 8th (all working fine) to June 11th (dead in the water). They are: /usr/src/sys/boot/Makefile /usr/src/sys/boot/i386/Makefile /usr/src/sys/boot/i386/libi386/biosdisk.c /usr/src/sys/boot/i386/loader/Makefile I have ruled out bisodisk.c, as stated above. That means that the Makefiles are building new stuff that previously was not built, namely zfsboot gptzfsboot I believe it has to do with that. More help is needed! I am tired of reinstalling the OS, but I am much more paranoid about updating my other machine in any way now, as it could erase that whole machine. I can't believe I am the only one seeing this... Dan Whew!! i'm giving thanks to every saint, god and daemon known. i rebuilt my kernel in very recent days (7.2) on my ancient 500MHz kayak, but did not go further. So still runing on the 7.0 kernel. Will someone send up a flare when it's *safe*? gary -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org For FBSD list: http://transfinite.thought.org/slicejourney.php The 4.98a release of Jottings: http://jottings.thought.org/index.php How do you know it isn't safe? Noone hasn't provided any useful info (debug, revisions where it works and where it doesn't). Yuri ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Something since June 8th clobbers my disk...
I sync with 7-STABLE almost every day. I build everything on a Toshiba U205 Satellite. Things are fine for months on end. I did this on June 8th. Everything was fine. I did this on June 10th. The machine no longer booted. The entire root partition got clobbered. I reinstalled a snapshot of 7-STABLE from May 28th that I had put on a DVD. Everything was once again fine. I then sync'd again this morning June 11th with 7-STABLE, did a full build, and reproducibly, BOOM - the entire root partition got clobbered. Gone. Again. After the reboot it just comes up with: BTX loader 1.00 BTX version is 1.02 Consoles: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 and stops. Nothing else is printed. There is no choice of how to boot. There is no files for me to send, no log files to inspect, no remnants. I unfortunately did not see where in the build this happened. My build does the canonical steps exactly as outlined in / usr/src/Makefile and then does a reboot. It builds userland and the kernel. When I inspect it from the bootable DVD the partition that my root filesystem was in has no association with it having the root any more. The partition is listed, but it looks like it had been freshly partitioned. Something is very, very wrong. Ideas? Dan Allen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Something since June 8th clobbers my disk...
On 6/11/09, Dan Allen danalle...@airwired.net wrote: I sync with 7-STABLE almost every day. I build everything on a Toshiba U205 Satellite. Things are fine for months on end. I did this on June 8th. Everything was fine. I did this on June 10th. The machine no longer booted. The entire root partition got clobbered. I reinstalled a snapshot of 7-STABLE from May 28th that I had put on a DVD. Everything was once again fine. I then sync'd again this morning June 11th with 7-STABLE, did a full build, and reproducibly, BOOM - the entire root partition got clobbered. Gone. Again. After the reboot it just comes up with: BTX loader 1.00 BTX version is 1.02 Consoles: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 and stops. Nothing else is printed. There is no choice of how to boot. There is no files for me to send, no log files to inspect, no remnants. I unfortunately did not see where in the build this happened. My build does the canonical steps exactly as outlined in / usr/src/Makefile and then does a reboot. It builds userland and the kernel. When I inspect it from the bootable DVD the partition that my root filesystem was in has no association with it having the root any more. The partition is listed, but it looks like it had been freshly partitioned. Something is very, very wrong. Ideas? Are you using ZFS on root partition? -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Something since June 8th clobbers my disk...
On 11 Jun 2009, at 3:40 PM, Paul B. Mahol wrote: Are you using ZFS on root partition? No. The disk is the default (UFS2 I believe). So I just reinstalled BSD again and this time I did not reinitialize the file system and after a brief disk integrity check it reinstalled and files I had added were still there! So apparently the file system did not get munged as much as the main disk partition map got nailed. So, what has changed recently that could mess with the disk partition map? I have Windows on the first disk partition and it has not been harmed with these problems. Dan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Something since June 8th clobbers my disk...
In trying to figure this out, I rebuilt a GENERIC kernel after sync'ing to today's RELENG_7 sources. I then installed it, held my breath, and rebooted. It works! So I am now looking at userland (make buildworld make installworld) to see if it is the culprit. Another possibility is my custom kernel build. Stay tuned... Dan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Something since June 8th clobbers my disk...
Okay. I did a make buildkernel installkernel and rebooted, no problems. I then did a make buildworld and rebooted, no problems. I then did a make installworld which completed normally, rebooted, and BINGO - my disk partition table has been zapped. The problem appears to be something that runs during this 'make installworld'! There are no problems with the build itself that I can tell, but some program is munging the disk partition table. In a zany sort of way this is progress. Of course now I have to reinstall the OS, again... Dan Allen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Something since June 8th clobbers my disk...
On 6/11/09, Dan Allen danalle...@airwired.net wrote: Okay. I did a make buildkernel installkernel and rebooted, no problems. I then did a make buildworld and rebooted, no problems. I then did a make installworld which completed normally, rebooted, and BINGO - my disk partition table has been zapped. The problem appears to be something that runs during this 'make installworld'! There are no problems with the build itself that I can tell, but some program is munging the disk partition table. In a zany sort of way this is progress. Of course now I have to reinstall the OS, again... Looks like boot(8) is problematic. Anything in /etc/src.conf or /etc/make.conf? -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Something since June 8th clobbers my disk...
On 11 Jun 2009, at 5:41 PM, Paul B. Mahol wrote: Looks like boot(8) is problematic. Anything in /etc/src.conf or /etc/make.conf? I have never touched or created a src.conf. If there was one there, it has been unmodified by me. I HAVE modified make.conf. Here is its contents: --- /etc/make.conf --- BATCH=yes NO_PROFILE=yes KERNCONF=DKA USE_FORTRAN=yes WITH_JADETEX=no PERL_VERSION=5.8.9 --- My custom kernel named DKA has only three modifications from GENERIC: I commented out the following three lines: #cpu I486_CPU #cpu I586_CPU #makeoptions DEBUG=-g I have run with such a kernel on many machines for many years now. However, my experiments have shown that the kernel build is not to blame. Isn't boot part of the kernel build? Why would installing the kernel not cause this problem? It is by installing the world via make installworld that my drive gets munged. I obviously am missing something, but boot(8) sounds like it is in the neighborhood of where the problem is. There were changes to /usr/src/sys/boot/i386/libi386/biosdisk.c and biospnp.c that really look suspect to me. Dan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
