Re: Booting Problem
On Wed, 30 Jan 2013, Doug Hardie wrote: On 30 January 2013, at 05:16, Fbsd8 wrote: Doug Hardie wrote: On 29 January 2013, at 07:18, Mario Lobo wrote: On Mon, 28 Jan 2013 15:16:14 -0800 Doug Hardie wrote: I have a relatively old machine that I am trying to boot 9.1 on. The bios will not boot from USB stick. I am using an external CD drive. It starts the boot process fine and gets to the Bootstrap loader message with revision 1.1. Then it puts out the machine, date, time the CD was created and starts the spinner. It spins around about 2 times and stops. The system continues to read from the drive for another couple minutes. Then everything stops. Nothing more happens. The CD is good. I can boot it just fine using the same external drive on another machine. While I could remove the drive and temporarily mount in in the working machine and build it there, I would like to find a way to successfully boot from CD. This will become a remote machine and taking it apart later is not a viable option. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" Can you boot a different OS (Win, Ububtu, gparted, etc ...) from the same drive on the same machine? Not so far. The drive works fine on other systems. You said in your orginal post "The bios will not boot from USB stick." I see no reason why you would think your PC would BOOT from any USB attached devices. Since you have another PC that does boot off of usb cd drive, swap hard drives and use that pc to load FreeBSD to the hard drive. This method will work for you. Yes that works now. But starting this weekend it will be about 100 miles away. That no longer will be practical. The CD will not be of much help then either. The problem started with the root partition being too small. Just repartition to make sure that does not come up for a while. While you have you hands of the machine you should see if you can figure out if it can do a pixe boot. You should also see if you can arrange for a serial console into the system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Booting Problem
On 30 January 2013, at 05:16, Fbsd8 wrote: > Doug Hardie wrote: >> On 29 January 2013, at 07:18, Mario Lobo wrote: >>> On Mon, 28 Jan 2013 15:16:14 -0800 >>> Doug Hardie wrote: >>> I have a relatively old machine that I am trying to boot 9.1 on. The bios will not boot from USB stick. I am using an external CD drive. It starts the boot process fine and gets to the Bootstrap loader message with revision 1.1. Then it puts out the machine, date, time the CD was created and starts the spinner. It spins around about 2 times and stops. The system continues to read from the drive for another couple minutes. Then everything stops. Nothing more happens. The CD is good. I can boot it just fine using the same external drive on another machine. While I could remove the drive and temporarily mount in in the working machine and build it there, I would like to find a way to successfully boot from CD. This will become a remote machine and taking it apart later is not a viable option. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" >>> Can you boot a different OS (Win, Ububtu, gparted, etc ...) from the >>> same drive on the same machine? >> Not so far. The drive works fine on other systems. >> > > You said in your orginal post "The bios will not boot from USB stick." > I see no reason why you would think your PC would BOOT from any USB attached > devices. > > Since you have another PC that does boot off of usb cd drive, swap hard > drives and use that pc to load FreeBSD to the hard drive. This method will > work for you. Yes that works now. But starting this weekend it will be about 100 miles away. That no longer will be practical. > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Booting Problem
Doug Hardie wrote: On 29 January 2013, at 07:18, Mario Lobo wrote: On Mon, 28 Jan 2013 15:16:14 -0800 Doug Hardie wrote: I have a relatively old machine that I am trying to boot 9.1 on. The bios will not boot from USB stick. I am using an external CD drive. It starts the boot process fine and gets to the Bootstrap loader message with revision 1.1. Then it puts out the machine, date, time the CD was created and starts the spinner. It spins around about 2 times and stops. The system continues to read from the drive for another couple minutes. Then everything stops. Nothing more happens. The CD is good. I can boot it just fine using the same external drive on another machine. While I could remove the drive and temporarily mount in in the working machine and build it there, I would like to find a way to successfully boot from CD. This will become a remote machine and taking it apart later is not a viable option. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" Can you boot a different OS (Win, Ububtu, gparted, etc ...) from the same drive on the same machine? Not so far. The drive works fine on other systems. You said in your orginal post "The bios will not boot from USB stick." I see no reason why you would think your PC would BOOT from any USB attached devices. Since you have another PC that does boot off of usb cd drive, swap hard drives and use that pc to load FreeBSD to the hard drive. This method will work for you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Booting Problem
On 1/29/2013 10:25 PM, d...@safeport.com wrote: What is the system you are using? What external devices does it have built-in support for? In the absence of any data - how about trying an external hard drive? Why not remove the hard drive, use another system to put FreeBSD on the drive, and put it back. From that point on you should be able to use the network to upgrade. I had to do something like this to try out PC-BSD years ago. I had one computer that wouldn't boot the install CD. I moved the hard drive to a computer that would boot the install CD. The catch was the computer that could boot the install CD wouldn't boot PC-BSD from the hard drive. Sometimes you just find hardware that doesn't behave. I'd also double check your BIOS settings for USB emulation. Most external CD drives are just an IDE or SATA drive with an adapter. If you take it apart, you can put the drive into the computer and see if skipping the USB helps it to boot. It's also a nice way to find a cheap drive. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Booting Problem
On 29 January 2013, at 20:25, d...@safeport.com wrote: > > On Tue, 29 Jan 2013, Doug Hardie wrote: > >> On 29 January 2013, at 07:18, Mario Lobo wrote: >> >>> On Mon, 28 Jan 2013 15:16:14 -0800 >>> Doug Hardie wrote: >>> I have a relatively old machine that I am trying to boot 9.1 on. The bios will not boot from USB stick. I am using an external CD drive. It starts the boot process fine and gets to the Bootstrap loader message with revision 1.1. Then it puts out the machine, date, time the CD was created and starts the spinner. It spins around about 2 times and stops. The system continues to read from the drive for another couple minutes. Then everything stops. Nothing more happens. The CD is good. I can boot it just fine using the same external drive on another machine. While I could remove the drive and temporarily mount in in the working machine and build it there, I would like to find a way to successfully boot from CD. This will become a remote machine and taking it apart later is not a viable option. > > What is the system you are using? What external devices does it have built-in > support for? In the absence of any data - how about trying an external hard > drive? 9.1 release - Generic. Basically the disk1. Don't have an extra external drive. > > Why not remove the hard drive, use another system to put FreeBSD on the > drive, and put it back. From that point on you should be able to use the > network to upgrade. I have done that before and it does work. However, with the various changes to the system, the root partition I had previously built that way for 8.2 is just not large enough for 9.1. Also, I wanted to go to a single partition (the 9.1 default). Probably freebsd-update will take me through major releases after this, but I was hoping for a better solution so I could avoid having to transport the machine a long way twice to be able to update it. > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Booting Problem
On Tue, 29 Jan 2013, Doug Hardie wrote: On 29 January 2013, at 07:18, Mario Lobo wrote: On Mon, 28 Jan 2013 15:16:14 -0800 Doug Hardie wrote: I have a relatively old machine that I am trying to boot 9.1 on. The bios will not boot from USB stick. I am using an external CD drive. It starts the boot process fine and gets to the Bootstrap loader message with revision 1.1. Then it puts out the machine, date, time the CD was created and starts the spinner. It spins around about 2 times and stops. The system continues to read from the drive for another couple minutes. Then everything stops. Nothing more happens. The CD is good. I can boot it just fine using the same external drive on another machine. While I could remove the drive and temporarily mount in in the working machine and build it there, I would like to find a way to successfully boot from CD. This will become a remote machine and taking it apart later is not a viable option. What is the system you are using? What external devices does it have built-in support for? In the absence of any data - how about trying an external hard drive? Why not remove the hard drive, use another system to put FreeBSD on the drive, and put it back. From that point on you should be able to use the network to upgrade. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Booting Problem
On 29 January 2013, at 07:18, Mario Lobo wrote: > On Mon, 28 Jan 2013 15:16:14 -0800 > Doug Hardie wrote: > >> I have a relatively old machine that I am trying to boot 9.1 on. The >> bios will not boot from USB stick. I am using an external CD drive. >> It starts the boot process fine and gets to the Bootstrap loader >> message with revision 1.1. Then it puts out the machine, date, time >> the CD was created and starts the spinner. It spins around about 2 >> times and stops. The system continues to read from the drive for >> another couple minutes. Then everything stops. Nothing more happens. >> >> The CD is good. I can boot it just fine using the same external >> drive on another machine. While I could remove the drive and >> temporarily mount in in the working machine and build it there, I >> would like to find a way to successfully boot from CD. This will >> become a remote machine and taking it apart later is not a viable >> option. ___ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions To >> unsubscribe, send any mail to >> "freebsd-questions-unsubscr...@freebsd.org" > > Can you boot a different OS (Win, Ububtu, gparted, etc ...) from the > same drive on the same machine? Not so far. The drive works fine on other systems. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Booting Problem
On Mon, 28 Jan 2013 15:16:14 -0800 Doug Hardie wrote: > I have a relatively old machine that I am trying to boot 9.1 on. The > bios will not boot from USB stick. I am using an external CD drive. > It starts the boot process fine and gets to the Bootstrap loader > message with revision 1.1. Then it puts out the machine, date, time > the CD was created and starts the spinner. It spins around about 2 > times and stops. The system continues to read from the drive for > another couple minutes. Then everything stops. Nothing more happens. > > The CD is good. I can boot it just fine using the same external > drive on another machine. While I could remove the drive and > temporarily mount in in the working machine and build it there, I > would like to find a way to successfully boot from CD. This will > become a remote machine and taking it apart later is not a viable > option. ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions To > unsubscribe, send any mail to > "freebsd-questions-unsubscr...@freebsd.org" Can you boot a different OS (Win, Ububtu, gparted, etc ...) from the same drive on the same machine? -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblows FREE) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Booting problem
On Tuesday 27 June 2006 14:07, Winston wrote: > I tried to boot via a serial console, so I modified/added the > following config files: > --- > /boot/loader.conf: > boot_multicons="YES" > boot_serial="YES" > console="comconsole" > --- > /boot.config > # wyt: added > -Dh > --- > Changed /etc/ttys: > ttyd0 "/usr/libexec/getty std.9600" dialup off secure > to > ttyd0 "/usr/libexec/getty std.9600" xterm on secure > > However, I got the following messages while booting: > /boot.config: # > FreeBSD/i386 boot > Default: 0:ad(0,a)boot > boot: > > I think I prob. made a mistake by putting a line of comment "#wyt: > added" at the beginning of /boot.conf and the boot loader doesn't like > it. > > But if I specify /boot/kernel/kernel after the line boot: > I got a bunch of reg dumps and finally: > BTX halted > > The kernel was booting fine before I make the changes. I now have the > chicken and egg problem: I need to get rid of the line of comment in > boot.conf for it to boot, but I can't access it without booting into > it. > > Any hint? Use /boot/loader rather than /boot/kernel/kernel at the boot2 prompt. -- John Baldwin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting Problem After Power Loss (fsck)?
Good news and bad news: Good News: System seems to have recovered. Booting into single user mode and running fsck worked great for / and /var, but did nothing for my /usr partition with all my data. After letting fsck run on my /usr partition for 4 days, the raid controller appeared to stall and the machine did not return to a prompt. Regular boot (multi-user mode) somehow worked where it would not work before, and background fsck on the /usr partition eventually ended. The system is now up and reachable, which is all I care about. Bad News: No one who read my last message offered to help. I suppose you can draw your own conclusions about the community-like nature of FreeBSD use in the Bay Area (home to UC Berkeley, FreeBSD Mall, and birthplace of the FreeBSD movement.) -- Rishi Chopra http://www.ocf.berkeley.edu/~rchopra Rishi Chopra wrote: I do not have the FIX-IT CD or another FreeBSD machine. Is there another fellow FreeBSD'er in the Bay Area, CA that can volunteer to help me troubleshoot the card as described below (e.g. plug in the card and break to debugger to gather info)? I can drive over to your place or you can come over to my house (directions on my homepage). If it helps, my perspective is that meeting up is totally positve and the only thing left keeping me involved with computing - allow me to explain: The server was totally idle when the power was cut, and I didn't make any changes while the server was down. I've seen some crazy things working on computers before (I can show you a list, post one to the newsgroup, or if you're curious you can try searching the google groups link on my homepage.) This would by far have to the most stubborn, underhanded, mean, nasty and implausable error I've ever come accross. I could really use some help getting the filesytem up again; my heart can't take another failure like this, and I'm ready to give up computers (recreationally and professionally) if I can't get this problem fixed. I had just finished recovering from a 2 year reconsolidation of life and data (a 75GXP/Raid-0 failure and data loss occurred while I was studying at UC Berkeley and triggered a very nasty chain of events culminating in this problem.) I can't handle going through another data consolidation; recovering from a recent thyroid removal and a 12-hour neck dissection/removal is a full-time affair, and the 30 some-odd staples in my neck greatly limit my ability to sit at the computer. Looks like the important thing is for me to make a new friend in the FreeBSD community and a new start on computing, or bid y'all adieu. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting Problem After Power Loss (fsck)?
I do not have the FIX-IT CD or another FreeBSD machine. Is there another fellow FreeBSD'er in the Bay Area, CA that can volunteer to help me troubleshoot the card as described below (e.g. plug in the card and break to debugger to gather info)? I can drive over to your place or you can come over to my house (directions on my homepage). If it helps, my perspective is that meeting up is totally positve and the only thing left keeping me involved with computing - allow me to explain: The server was totally idle when the power was cut, and I didn't make any changes while the server was down. I've seen some crazy things working on computers before (I can show you a list, post one to the newsgroup, or if you're curious you can try searching the google groups link on my homepage.) This would by far have to the most stubborn, underhanded, mean, nasty and implausable error I've ever come accross. I could really use some help getting the filesytem up again; my heart can't take another failure like this, and I'm ready to give up computers (recreationally and professionally) if I can't get this problem fixed. I had just finished recovering from a 2 year reconsolidation of life and data (a 75GXP/Raid-0 failure and data loss occurred while I was studying at UC Berkeley and triggered a very nasty chain of events culminating in this problem.) I can't handle going through another data consolidation; recovering from a recent thyroid removal and a 12-hour neck dissection/removal is a full-time affair, and the 30 some-odd staples in my neck greatly limit my ability to sit at the computer. Looks like the important thing is for me to make a new friend in the FreeBSD community and a new start on computing, or bid y'all adieu. -- Rishi Chopra http://www.ocf.berkeley.edu/~rchopra Ion-Mihai Tetcu wrote: On Sun, 08 Feb 2004 21:12:51 -0800 Rishi Chopra <[EMAIL PROTECTED]> wrote: Here's a summary of my problem so far: Server was idle (e.g. absolutely no processes running aside from csh, ttyv0 and ps) when power was cut; server reports a problem mounting /usr partition upon reboot. I have since tried the following: (1) Booted into single-user mode and ran 'fsck' - the latest output to the terminal says: FILE SYSTEM MARKED CLEAN /dev/da0s1e Last Mounted on /usr Phase 1 - check blocks and sizes After letting the system 'do its thing' for 5+ days, the output did not change. (2) I tried an 'fsck -p' and got the following message: /dev/da0s1a: 1128 files, 36058 used, 47059 free (261 frags, 58771 blocks, 0.1% fragmentations) Do you get the prompt back ? Try fsck -p on / then on /var /tmp and last /usr. At least you will know what partitions are ok. Better yet I suggest you boot from the second aka Fixit CD and run fsck from there; you fsck binary may be broken. Also boot verbose (I don't know if safe-mode applies to SCSI, but if it does, try that also). The display has been stuck with that same output for countless hours now. Do you have disk activity when fsck seems to be stuck ? Questions I have: (1) Have I suffered a total loss or is this still some way to revover my filesystem? After suffering a similar loss with a hardware raid-0 failure under win2k, I was assuming the FreeBSD setup would be more durable. I would hate to walk away thinking that a simple power loss could wipe out a freebsd server under nothing more than one terminal login. Generally this doesn't happen. From my experience, it happens if either there are problems with the disk access infrastructure (a la timeouts, etc. on ata) or something bad elsewhere in the kernel. (2) Why would a simple fsck of the filesystem not work in my case? If you have the kernel with options DDB options BREAK_TO_DEBUGGER and no disk activity I suggest that you break to debugger hitting Ctrl+Esc and try to gather some info from there. Note that in case fsck is actually running this could further damage you fs, but since you can't do anything else I would say to give it a try. To summarize: 1. See if you have disk activity when fsck seems to be stuck. 2. Try fsck (-p) first on root, the on tmp, /var, /usr, /home. 3. Esp. if fsck / doesn't go ok try booting verbose with Fixit CD and run fsck from there. 4. If 1 gets you the same results try putting the disk in another machine where you have debugging options in the kernel, break to debugger and gather info from there (esp. if you're running 5.x try asking on current@ what exactly to look for in the debugger). ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting Problem After Power Loss (fsck)?
Please see my reply below: Ion-Mihai Tetcu wrote: On Sun, 08 Feb 2004 21:12:51 -0800 Rishi Chopra <[EMAIL PROTECTED]> wrote: Here's a summary of my problem so far: Server was idle (e.g. absolutely no processes running aside from csh, ttyv0 and ps) when power was cut; server reports a problem mounting /usr partition upon reboot. I have since tried the following: (1) Booted into single-user mode and ran 'fsck' - the latest output to the terminal says: FILE SYSTEM MARKED CLEAN /dev/da0s1e Last Mounted on /usr Phase 1 - check blocks and sizes After letting the system 'do its thing' for 5+ days, the output did not change. (2) I tried an 'fsck -p' and got the following message: /dev/da0s1a: 1128 files, 36058 used, 47059 free (261 frags, 58771 blocks, 0.1% fragmentations) Do you get the prompt back ? Try fsck -p on / then on /var /tmp and last /usr. At least you will know what partitions are ok. Better yet I suggest you boot from the second aka Fixit CD and run fsck from there; you fsck binary may be broken. Also boot verbose (I don't know if safe-mode applies to SCSI, but if it does, try that also). This is exactly the problem. The 'fsck' command does not return to a prompt. The display has been stuck with that same output for countless hours now. Do you have disk activity when fsck seems to be stuck ? Questions I have: (1) Have I suffered a total loss or is this still some way to revover my filesystem? After suffering a similar loss with a hardware raid-0 failure under win2k, I was assuming the FreeBSD setup would be more durable. I would hate to walk away thinking that a simple power loss could wipe out a freebsd server under nothing more than one terminal login. Generally this doesn't happen. From my experience, it happens if either there are problems with the disk access infrastructure (a la timeouts, etc. on ata) or something bad elsewhere in the kernel. (2) Why would a simple fsck of the filesystem not work in my case? If you have the kernel with options DDB options BREAK_TO_DEBUGGER and no disk activity I suggest that you break to debugger hitting Ctrl+Esc and try to gather some info from there. Note that in case fsck is actually running this could further damage you fs, but since you can't do anything else I would say to give it a try. To summarize: 1. See if you have disk activity when fsck seems to be stuck. 2. Try fsck (-p) first on root, the on tmp, /var, /usr, /home. 3. Esp. if fsck / doesn't go ok try booting verbose with Fixit CD and run fsck from there. 4. If 1 gets you the same results try putting the disk in another machine where you have debugging options in the kernel, break to debugger and gather info from there (esp. if you're running 5.x try asking on current@ what exactly to look for in the debugger). -- Rishi Chopra http://www.ocf.berkeley.edu/~rchopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting Problem After Power Loss (fsck)?
On Mon, 9 Feb 2004 11:44:46 +0200 Ion-Mihai Tetcu <[EMAIL PROTECTED]> wrote: > On Sun, 08 Feb 2004 21:12:51 -0800 > Rishi Chopra <[EMAIL PROTECTED]> wrote: > > > Here's a summary of my problem so far: [..] > To summarize: > > 1. See if you have disk activity when fsck seems to be stuck. > > 2. Try fsck (-p) first on root, the on tmp, /var, /usr, /home. > > 3. Esp. if fsck / doesn't go ok try booting verbose with Fixit CD and > run fsck from there. > > 4. If 1 gets you the same results try putting the disk in another If 3 gets ... > machine where you have debugging options in the kernel, break to > debugger and gather info from there (esp. if you're running 5.x try > asking on current@ what exactly to look for in the debugger). -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting Problem After Power Loss (fsck)?
On Sun, 08 Feb 2004 21:12:51 -0800 Rishi Chopra <[EMAIL PROTECTED]> wrote: > Here's a summary of my problem so far: > > Server was idle (e.g. absolutely no processes running aside from > csh, ttyv0 and ps) when power was cut; server reports a problem mounting > /usr partition upon reboot. > > I have since tried the following: > > (1) Booted into single-user mode and ran 'fsck' - the latest output to > the terminal says: > > FILE SYSTEM MARKED CLEAN > /dev/da0s1e > Last Mounted on /usr > Phase 1 - check blocks and sizes > > After letting the system 'do its thing' for 5+ days, the output did not > change. > > (2) I tried an 'fsck -p' and got the following message: > > /dev/da0s1a: 1128 files, 36058 used, 47059 free (261 frags, 58771 > blocks, 0.1% fragmentations) Do you get the prompt back ? Try fsck -p on / then on /var /tmp and last /usr. At least you will know what partitions are ok. Better yet I suggest you boot from the second aka Fixit CD and run fsck from there; you fsck binary may be broken. Also boot verbose (I don't know if safe-mode applies to SCSI, but if it does, try that also). > The display has been stuck with that same output for countless hours now. Do you have disk activity when fsck seems to be stuck ? > Questions I have: > > (1) Have I suffered a total loss or is this still some way to revover my > filesystem? After suffering a similar loss with a hardware raid-0 > failure under win2k, I was assuming the FreeBSD setup would be more > durable. I would hate to walk away thinking that a simple power loss > could wipe out a freebsd server under nothing more than one terminal login. Generally this doesn't happen. From my experience, it happens if either there are problems with the disk access infrastructure (a la timeouts, etc. on ata) or something bad elsewhere in the kernel. > (2) Why would a simple fsck of the filesystem not work in my case? If you have the kernel with options DDB options BREAK_TO_DEBUGGER and no disk activity I suggest that you break to debugger hitting Ctrl+Esc and try to gather some info from there. Note that in case fsck is actually running this could further damage you fs, but since you can't do anything else I would say to give it a try. To summarize: 1. See if you have disk activity when fsck seems to be stuck. 2. Try fsck (-p) first on root, the on tmp, /var, /usr, /home. 3. Esp. if fsck / doesn't go ok try booting verbose with Fixit CD and run fsck from there. 4. If 1 gets you the same results try putting the disk in another machine where you have debugging options in the kernel, break to debugger and gather info from there (esp. if you're running 5.x try asking on current@ what exactly to look for in the debugger). -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting Problem
On Tue, 03 Feb 2004 22:35:35 -0800 Rishi Chopra <[EMAIL PROTECTED]> wrote: > Here's some questions: > > If the server was idle (e.g. absolutely no processes running aside from > login shell and terminal and no disk access occurring) does it make > sense that the filesystem would have had a problem after being > improperly unmounted? Each file system would be at least marked as being used, so fsck -p on boot will print that and check them. Usually if the system is idle the fs will be ok. But you have processes that are active in regard the fs, even if not logged in (cron, ntp/ntpdate, syslog to name a few); /tmp and /var usually have problems after an unclean shutdown. Note two things about disks: 1. hw.ata.wc=0 disables write caching - bad for performance good for integrity. When a disk does wc it holds data in its buffer and report it as being written to the OS and this delay could go up to 60 seconds (and even more) depending on the HDD and the load. atacontrol cap should tell you the state of write caching; on my system I have wc=0 but atacontrol shows it turned on, so I might be wrong here or this is not supported on all HDDs. 2. kern.filedelay=30, kern.dirdelay=29, kern.metadelay=28 sets how often the respective data is flushed ( synced(8) ) to disk when using soft-updates; note the descending order, it is important. You might want to decrease them, which will degrade performance, but could help a more consistent fs in case of a crash. When I test a new HDD, CDROM, kernel and world I usually decrease them to 15,14,13 or even 10,9,8 until everything seems OK. > Also, how long should an 'fsck' on a 500GB partition take? It's been > running for almost 12 hours now, and the latest output is still "Phase 1 > - check blocks and sizes"; is something wrong or is fsck still doing its > thing? My largest was about 80G and it takes a few minutes with UDMA100 for a small amount of errors, so I don't really know. But it depends on how much the file system is damaged, the access speed of the disk/controller and the processor/memory; I have the feeling the size - time progression is not at all arithmetical. As a note, if you don't really need a fs that big, use smaller partitions and mount / symlink them where you need them where you need. This will give you better chances in case of crash. -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting Problem
Here's some questions: If the server was idle (e.g. absolutely no processes running aside from login shell and terminal and no disk access occurring) does it make sense that the filesystem would have had a problem after being improperly unmounted? Also, how long should an 'fsck' on a 500GB partition take? It's been running for almost 12 hours now, and the latest output is still "Phase 1 - check blocks and sizes"; is something wrong or is fsck still doing its thing? Ion-Mihai Tetcu wrote: On Tue, 03 Feb 2004 01:09:22 -0800 Rishi Chopra <[EMAIL PROTECTED]> wrote: I booted into single-user mode and ran 'fsck' - the latest output to the terminal says: FILE SYSTEM MARKED CLEAN /dev/da0s1e Last Mounted on /usr Phase 1 - check blocks and sizes FILE SYSTEM STILL DIRTY Can't be only this. It should have outputted something else between Phase 1 and FILE SYSTEM STILL DIRTY. Will fsck continue attempting to fix the filesystem? Have I suffered a total loss or is fsck still doing its thing? Read man fsck and its see also section. -- Rishi Chopra http://www.ocf.berkeley.edu/~rchopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting Problem
On Tue, 03 Feb 2004 01:09:22 -0800 Rishi Chopra <[EMAIL PROTECTED]> wrote: > I booted into single-user mode and ran 'fsck' - the latest output to the > terminal says: > > FILE SYSTEM MARKED CLEAN > /dev/da0s1e > Last Mounted on /usr > Phase 1 - check blocks and sizes > > FILE SYSTEM STILL DIRTY Can't be only this. It should have outputted something else between Phase 1 and FILE SYSTEM STILL DIRTY. > Will fsck continue attempting to fix the filesystem? Have I suffered a > total loss or is fsck still doing its thing? Read man fsck and its see also section. -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting Problem
I booted into single-user mode and ran 'fsck' - the latest output to the terminal says: FILE SYSTEM MARKED CLEAN /dev/da0s1e Last Mounted on /usr Phase 1 - check blocks and sizes FILE SYSTEM STILL DIRTY Will fsck continue attempting to fix the filesystem? Have I suffered a total loss or is fsck still doing its thing? If this is a total loss, can I do anything to get my data back? -Rishi Rishi Chopra wrote: I'm getting the following error message during startup: /usr: mount pending error: blocks 16 files 1 I'm guessing this orrcured due to a shutdown during background fsck of the filesystem. Will the error fix itself (e.g. will the boot process continue and finally proceed to a prompt) or do I need to intervene? If intervention is required, how would I go about setting things right? -- Rishi Chopra http://www.ocf.berkeley.edu/~rchopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting Problem
Thank you! Ion-Mihai Tetcu wrote: On Mon, 02 Feb 2004 19:49:50 -0800 Rishi Chopra <[EMAIL PROTECTED]> wrote: I'm getting the following error message during startup: /usr: mount pending error: blocks 16 files 1 I'm guessing this orrcured due to a shutdown during background fsck of the filesystem. Not necessarily during a bgfsck, just the filesystem is not clean, so bgfsck will run. Will the error fix itself (e.g. will the boot process continue and finally proceed to a prompt) or do I need to intervene? Usually it will continue, if not, you will be the first or know ;) If intervention is required, how would I go about setting things right? Watch (tail -F) /var/log/messages, after login, if you get something strange there (like unexpected softupdate inconsistency, run fsck manually or fsck drops core) or if on the next reboot it happens again boot is single user and run fsck. -- Rishi Chopra http://www.ocf.berkeley.edu/~rchopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Rishi Chopra http://www.ocf.berkeley.edu/~rchopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting Problem
On Mon, 02 Feb 2004 19:49:50 -0800 Rishi Chopra <[EMAIL PROTECTED]> wrote: > I'm getting the following error message during startup: > > /usr: mount pending error: blocks 16 files 1 > > I'm guessing this orrcured due to a shutdown during background fsck of > the filesystem. Not necessarily during a bgfsck, just the filesystem is not clean, so bgfsck will run. > Will the error fix itself (e.g. will the boot process continue and > finally proceed to a prompt) or do I need to intervene? Usually it will continue, if not, you will be the first or know ;) > If intervention is required, how would I go about setting things right? Watch (tail -F) /var/log/messages, after login, if you get something strange there (like unexpected softupdate inconsistency, run fsck manually or fsck drops core) or if on the next reboot it happens again boot is single user and run fsck. > > -- > Rishi Chopra > http://www.ocf.berkeley.edu/~rchopra > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
