Re: fsck failed after hard crash
(...) unexpected soft-update inconsistency, unable to write block, etc. going back to my 9/9/2003 good kernel, it works. i tried to use my old kernel; build with sources from fbsd 5.1 release). i rebooted the system and started fsck -y /usr again but the same problems occur :( now there are two possibilities i guess: - something in userland is broken too - my ufs2 is really dead I'm using ufs1, FWIW, and my userland is from september 9 as well. So, either 5.1R is too far back or you are in trouble. FWIW. so here i go again :) - partly at least ... i booted the live CD and was able to fix my ufs2 fs (still some errors reported but marked as clean). then i re-installed the sources from fbsd 5.1 release cd, built a new kernel and did a make world - everything seems to be ok now :) so there seems to be something broken in sources from 13.9.2003 ? seb (...) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
fsck failed after hard crash
hi, i did cvsup for /usr/src yesterday and did a build world. i also build a new kernel without all these debugging things. i rebooted the system and everything went fine first but then i tried to recompile pf_freebsd and the system crashed. i rebooted and did fsck and tried the rebuild again - same thing :( reboot again, fsck with many errors (some sectors could not be written, inconsistancy soft updates). i managed to start gnome2 agian. i started vmware and ... crash agin :'( so i thought of using the old kernel again but when i restart and run fsck it is NOT able to mark /usr as clean !! :( what can i do now ? any ideas ? thx seb -- COMPUTERBILD 15/03: Premium-e-mail-Dienste im Test -- 1. GMX TopMail - Platz 1 und Testsieger! 2. GMX ProMail - Platz 2 und Preis-Qualitätssieger! 3. Arcor - 4. web.de - 5. T-Online - 6. freenet.de - 7. daybyday - 8. e-Post ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck failed after hard crash
On Sun, Sep 14, 2003 at 11:42:21AM +0200, Sebastian Ssmoller wrote: i did cvsup for /usr/src yesterday and did a build world. i also build a new kernel without all these debugging things. If you're running FreeBSD-current, I would suggest that you put the debugging options back into your kernel. i rebooted the system and everything went fine first but then i tried to recompile pf_freebsd and the system crashed. Without debugging or even a panic message, it is fairly difficult to make any useful suggestions. i rebooted and did fsck and tried the rebuild again - same thing :( Panic message? reboot again, fsck with many errors (some sectors could not be written, inconsistancy soft updates). i managed to start gnome2 agian. i started vmware and ... crash agin :'( Are you sure you don't want to run FreeBSD 4.8? so i thought of using the old kernel again but when i restart and run fsck it is NOT able to mark /usr as clean !! :( what can i do now ? any ideas ? When fsck fails to clean /usr are there any error messages? What fsck command did you issue to clean up /usr? Did you try using an alternate super block? What compiler flags did you use to build the kernel? -- Steve ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck failed after hard crash
I'm seeing similar messages from fsck: unexpected soft-update inconsistency, unable to write block, etc. going back to my 9/9/2003 good kernel, it works. so I think SOMETHING broke here. LER --On Sunday, September 14, 2003 08:30:51 -0700 Steve Kargl [EMAIL PROTECTED] wrote: On Sun, Sep 14, 2003 at 11:42:21AM +0200, Sebastian Ssmoller wrote: i did cvsup for /usr/src yesterday and did a build world. i also build a new kernel without all these debugging things. If you're running FreeBSD-current, I would suggest that you put the debugging options back into your kernel. i rebooted the system and everything went fine first but then i tried to recompile pf_freebsd and the system crashed. Without debugging or even a panic message, it is fairly difficult to make any useful suggestions. i rebooted and did fsck and tried the rebuild again - same thing :( Panic message? reboot again, fsck with many errors (some sectors could not be written, inconsistancy soft updates). i managed to start gnome2 agian. i started vmware and ... crash agin :'( Are you sure you don't want to run FreeBSD 4.8? so i thought of using the old kernel again but when i restart and run fsck it is NOT able to mark /usr as clean !! :( what can i do now ? any ideas ? When fsck fails to clean /usr are there any error messages? What fsck command did you issue to clean up /usr? Did you try using an alternate super block? What compiler flags did you use to build the kernel? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 pgp0.pgp Description: PGP signature
Re: fsck failed after hard crash
Am Son, 2003-09-14 um 17.30 schrieb Steve Kargl: On Sun, Sep 14, 2003 at 11:42:21AM +0200, Sebastian Ssmoller wrote: i did cvsup for /usr/src yesterday and did a build world. i also build a new kernel without all these debugging things. If you're running FreeBSD-current, I would suggest that you put the debugging options back into your kernel. sorry to forget to post these info's: i am running freebsd-current. started with 5.1 release and updated yesterday. i removed the debugging stuff from the kernel cause i wanted to check the possible performance difference. i rebooted the system and everything went fine first but then i tried to recompile pf_freebsd and the system crashed. Without debugging or even a panic message, it is fairly difficult to make any useful suggestions i agree but this would be difficult when being unable to reboot the system :) . i rebooted and did fsck and tried the rebuild again - same thing :( Panic message? no message :( first time it froze , second time it rebooted. reboot again, fsck with many errors (some sectors could not be written, inconsistancy soft updates). i managed to start gnome2 agian. i started vmware and ... crash agin :'( Are you sure you don't want to run FreeBSD 4.8? good question :) so i thought of using the old kernel again but when i restart and run fsck it is NOT able to mark /usr as clean !! :( what can i do now ? any ideas ? When fsck fails to clean /usr are there any error messages? What fsck command did you issue to clean up /usr? Did you try using an alternate super block? i ran: fsck -y /usr and it complains several times (!) about unexpected soft-update inconsistency and unable to write block :( i have not tried an alternate super block yet - i was not sure whether this could help, could it ? What compiler flags did you use to build the kernel? i used default settings finally i found out that i can mount /usr readonly so a backup could be possible (?); creating new ufs2 and restore backup could be a possible solution (?) thx seb -- Steve ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck failed after hard crash
Am Son, 2003-09-14 um 17.49 schrieb Larry Rosenman: I'm seeing similar messages from fsck: unexpected soft-update inconsistency, unable to write block, etc. going back to my 9/9/2003 good kernel, it works. i tried to use my old kernel; build with sources from fbsd 5.1 release). i rebooted the system and started fsck -y /usr again but the same problems occur :( now there are two possibilities i guess: - something in userland is broken too - my ufs2 is really dead any ideas ? seb so I think SOMETHING broke here. LER --On Sunday, September 14, 2003 08:30:51 -0700 Steve Kargl [EMAIL PROTECTED] wrote: On Sun, Sep 14, 2003 at 11:42:21AM +0200, Sebastian Ssmoller wrote: i did cvsup for /usr/src yesterday and did a build world. i also build a new kernel without all these debugging things. If you're running FreeBSD-current, I would suggest that you put the debugging options back into your kernel. i rebooted the system and everything went fine first but then i tried to recompile pf_freebsd and the system crashed. Without debugging or even a panic message, it is fairly difficult to make any useful suggestions. i rebooted and did fsck and tried the rebuild again - same thing :( Panic message? reboot again, fsck with many errors (some sectors could not be written, inconsistancy soft updates). i managed to start gnome2 agian. i started vmware and ... crash agin :'( Are you sure you don't want to run FreeBSD 4.8? so i thought of using the old kernel again but when i restart and run fsck it is NOT able to mark /usr as clean !! :( what can i do now ? any ideas ? When fsck fails to clean /usr are there any error messages? What fsck command did you issue to clean up /usr? Did you try using an alternate super block? What compiler flags did you use to build the kernel? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck failed after hard crash
--On Sunday, September 14, 2003 19:02:17 +0200 Sebastian Ssmoller [EMAIL PROTECTED] wrote: Am Son, 2003-09-14 um 17.49 schrieb Larry Rosenman: I'm seeing similar messages from fsck: unexpected soft-update inconsistency, unable to write block, etc. going back to my 9/9/2003 good kernel, it works. i tried to use my old kernel; build with sources from fbsd 5.1 release). i rebooted the system and started fsck -y /usr again but the same problems occur :( now there are two possibilities i guess: - something in userland is broken too - my ufs2 is really dead I'm using ufs1, FWIW, and my userland is from september 9 as well. So, either 5.1R is too far back or you are in trouble. FWIW. any ideas ? seb so I think SOMETHING broke here. LER --On Sunday, September 14, 2003 08:30:51 -0700 Steve Kargl [EMAIL PROTECTED] wrote: On Sun, Sep 14, 2003 at 11:42:21AM +0200, Sebastian Ssmoller wrote: i did cvsup for /usr/src yesterday and did a build world. i also build a new kernel without all these debugging things. If you're running FreeBSD-current, I would suggest that you put the debugging options back into your kernel. i rebooted the system and everything went fine first but then i tried to recompile pf_freebsd and the system crashed. Without debugging or even a panic message, it is fairly difficult to make any useful suggestions. i rebooted and did fsck and tried the rebuild again - same thing :( Panic message? reboot again, fsck with many errors (some sectors could not be written, inconsistancy soft updates). i managed to start gnome2 agian. i started vmware and ... crash agin :'( Are you sure you don't want to run FreeBSD 4.8? so i thought of using the old kernel again but when i restart and run fsck it is NOT able to mark /usr as clean !! :( what can i do now ? any ideas ? When fsck fails to clean /usr are there any error messages? What fsck command did you issue to clean up /usr? Did you try using an alternate super block? What compiler flags did you use to build the kernel? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 pgp0.pgp Description: PGP signature
