Ubuntu Servers :: SERVER Stuck During Boot (fsck Waiting For Input)
Aug 11, 2010
all is well on my headless Lucid server until a recent apt-get upgrade && shutdown -R now ... it did not come back up? after i moved a screen to the other side of the house, i found fcsk waiting for input during the boot process errors on / ... (I)gnore / (F)ix " ...so i had to attach a keyboard just to push <F> i could change /etc/fstab so it never runs fsck, but this doesn't seem wise. how can i make it <F>ix automatically ? ( or maybe after Xsec )
This is a standard install, just like I've done dozens of times before.
Plain vanilla, just installed.
When I boot, I get to the splash screen and it doesn't go into the default selection.
Could this be a Hardware thingy? The reason I ask is because I've had this issue happening with 5.2 on the same machine. I just formatted it completely and installed a fresh 5.3 i386 on it and I get the same behavior.
[root@server ~]# cat /boot/grub/grub.conf # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that
After a while trying to update, it trows out this error:
Code: Select allIgn http://ftp.mx.debian.org wheezy-updates/non-free Translation-en W: Imposible obtener http://security.debian.org/dists/wheezy/updates/main/binary-amd64/Packages 503 DNS error for hostname security.debian.org: Name or service not known. If security.debian.org refers to a configured cache repository, please check the corresponding configuration file.
I have tried changing repos, also i have verified with iceweasel the availability of the repo.
Ihave changed aldo the network setting from dhcpd to static.
I am using Debian wheezy, gnome desktop enviroment, although the DE is irrelevant.
My conections details:
Code: Select all eth0 Link encap:Ethernet HWaddr 50:46:5d:b2:1b:2a inet addr:192.168.2.14 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::5246:5dff:feb2:1b2a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:376446 errors:0 dropped:0 overruns:0 frame:0
I upgraded to Ubuntu 10.04 from 9.10 and when I try to boot into ubuntu now it goes to a screen where it says "waiting for /windows" and even after the loading bar is fully loaded it stuck on that screen. BTW I don't know if this will help but when I restarted it wouldn't work because grub was broken and I booted it 9.10 live CD and reinstalled it.
Forgive the terseness. I'm frazzled with this issue, perhaps I should have asked earlier. Every weekend for the past 2 months has been an endless cycle of 'repair broken system' off the install disk.
Installed from Ubuntu server 10.04LTS x86_64, + xfce-desktop Here is uname -a Linux ournas 2.6.32-25-server #45-Ubuntu SMP Sat Oct 16 20:06:58 UTC 2010 x86_64 GNU/Linux If I add my raid + lvm to the fstab file, the boot stalls, (no error it, just hangs waiting, forever). So that's a not very user friendly to start with.
I've tried the suggestions about UUID in fstab tried using LABEL instead, or even /dev/xxx. Every time it hangs. I've googled this endlessly and not found a solution. So don't ask why... since I seem to have tried every odd suggestion to fix this, I've lost track. There seems to be some consensus that whoever gave us plymouth laid an egg. Forgive me if I'm wrong, but did we need a better graphical boot if it breaks everything else?
I was editing my fsck at etc/fstab/ after removing a hard drive and i think i commented out the wrong drive . now i just get a blank screen on boot. I have the ability to use my ubuntu cd for a recovery console, live desktop, etc.
I have a 2TB file-system and when the machine reboots it fails the fsck, halts and goes into maintenance mode.Stats: I have have RHEL 5, 2.6.18 kernel, the file-system is an ext3. The file-system is on an EMC AX4 connected with fiber channel HBA.So far my reading tells me this should work because under 2.6 4TB is OK. Any ideas why this fails?If I take it out of the fstab file and mount it manually the boot is OK and the file-system behaves well. I can change the fsck check option in the fstab to 0 but I don't think I should have too. Everything I read says that 2TB ext3 file-systems are OK.
I have installed Fedora 11 recently on a new system. Sphinx speech recognition was working fine on my old system. When i run the same project on my new system, the system does not respond as it is waiting for microphone voice input.
Then I checked the microphone and have set it properly and its working now. The details how i made my microphone working is at the following link: [url]
Though, I can record and play any sound, but it is not working with sphinx project.
I have tried different methods to auto start wpa_supplicant at boot on Ubuntu Lucid server on a laptop which can't be connected to Ethernet.
The only thing that worked is adding the wpa_supplicant command before exit0 in rc.local. It solve my problem of wpa_supplicant auto start and annoyance on not be able to ssh before local login. But the screen stuck at Ubuntu Logo. How can i get pass Ubuntu logo screen to regular tty or xbmc in future?
For some reason my new F12 install can print one document, then its seems to hang.
It never clears the print queue even when the document has printed, which I guess is why the next job never gets through. Even if I cancel the finished job, the next one won't start because the status in cups is "waiting for job to complete".
To fix it I have to kill cupsd and any print processes, reboot the printer and print server.
I guess F12 must do something to hang the print server (uses IPP) as I can't even print from a known-working F10 machine after F12 has printed.
I don't really think the below is relevant as its a F12/CUPS 1.4.2 issue I'd say (as its works fine on F10 and Ubuntu 9.04) but here you go:
I am running 9.04 Server (standalone). It had been running fine since I installed in last autumn. Upon reboot, fsck of the root filesystem was forced and it hangs at the same point (16.5%) every time. I was able to break out somehow with cntl-alt-del but the boot was to a read-only filesystem. So I couldn't disable the forced fsck. Instead, I tried to fsck there. It started, but hung. I couldn't do e2fsck -v as it needed the device and, although I worked on UNIX systems for decades, I am not familiar with the /dev/mapper stuff.
Looking at other threads, all involving the desktop GUI Ubuntu, I tried some of the suggestions. Went into the BIOS to see what I could disable. I killed the serial port and similar. (Some said that onboard modems interfered with the checks in /dev.) I also tried to boot from my original installation disk. That does work.The suggestion is to choose "Try without any change to your computer". The problem is that is not available on the server installation, apparently only the desktop (GUI). I had install, check CD for defects, test memory, boot from first hard disk, and something like repair or recover a broken disk. I started the last of them, as it seemed to be the only option. It failed because it couldn't get a dhcp address. I could manually configure it (as it is hard addressed anyway), but I didn't want to start screwing up configurations not knowing where it was going, whayt it would ry to do, and risk losing months of hard work.
Without help, I think I will be forced to install the OS on a second drive, use that install to fsck the original filesystem on the original disk, edit the fstab (or whichever has the config) on the original disk to disable fsck, and return to the original boot.I am building this server for a nonprofit and have put in many hours writing mysql/perl apache cgi code for them as a free service and hate to lose it all and set back everything.
I have a file server that has a raid array with a jfs file system attached. Whenever there is a power cut (quite frequently in our house), and the server is not shutdown cleanly, then the raid array is not automatically mounted since ubuntu doesn't know if the journal is clean. I have to then manually run fsck and remount the partition by hand which is a bit annoying. Basically, does anybody know if fsck can be setto run if a non-clean shutdown has been detected, or failing that, on every boot?
When I was upgrading my system (ubuntu server edition) today from 8.10 to 10.04 (of course in small steps: upgrade version after version) everything seemed running smoothly. But when I restarted it, it gave an error message: Gave up waiting on root device. Screenshot of error and grub menu attached. I've read some information about it and applied the possible workaround given here: [URL]. My system is very old and so is the HDD: it uses an IDE connector. Typing 'exit' doesn't work either.
I'm curious if anybody can shed some light for me in this department. We're in a large environment with a Windows DHCP Server. We have been tinkering with LTSP on Edubuntu as thin and fat clients. It works great, but right now we just have 1 server handling the lab, which works fine unless we want to expand, which may be very possible.
These are the instructions I received: Login to your windows server and load the DHCP configuration screen Create a DHCP reservation for the MAC address you obtained Add the configuration options below to enable the machine to boot from the LTSP server 017 Root Path: /opt/ltsp/i386 066 Boot Server Host Name: <ip address> 067 Bootfile Name: ltsp/arch/pxelinux.0 # Specify CPU architecture in place of 'arch', for instance 'i386'
I'm curious, what if I want to have multiple Ubuntu servers on the network that I want to have bootable? For example, let's say I have 3 labs, and 3 servers. Server A to Lab A, Server B to Lab B, and Server C to Lab C. I want all C's computers to boot to C, and B to B, A to A, etc.
1 - How would I add multiple entries on the Windows DHCP Server to allow all 3 (A B C) servers to boot?
2 - How would I be able to isolate the clients so ONLY Lab A clients boot to Server A, etc?
I am wondering if there is a way to manually trigger a file system check during boot by pressing/holding a key. Maybe there is already a keyboard shortcut built in to do this?I know that using tune2fs you can modify the number of boots (mounts) between file system checks, or even use "shutdown -rF" to reboot the system and force a file system checkAlso, I do not want to force the user to choose to run/skip the file system check during boot. For example, prompting the user with, "Do you want to run a file system check [y/n]?" each boot (or even each time the system thinks it should run a file system check),s not desirable
I need to boot in WXP just because the guys at the company don't want to update for Linux drivers in the TS so I can't connect from home unless I do it in Windows XP. But today WXP refuses to boot, when the progress bar appears, the system boots automatically. The WXP CD doesn't help, the repair console doesn't let me run chkdsk or anything (dir C: gives an error about listing addresses or something like that). Is there any way to use fsck or anything in Linux to repair the WXP NTFS partition?
i have the same issue but with a real install, not a vmware.every reboot fsck says that my main partition was not cleanly unmounted and check is forced.during shutdown the ubuntu does not show messages in a clear way but in random places. however, i am able to see the "/ is busy" message 1 second before reboot/off.my distribution is 10.10 upgraded from 9.10, 10.04
The system is an old AMD Duron 650MHz that was dug out of the garbage, trying to set it up as a light duty server. I installed ubuntu 10.04 with no errors or troubles during the install, however whenever the system is booted it sits at a cursor for about a minute then goes into busybox giving the error "Gave up waiting on root device." and says that the hard drive does not excist. If I sit at busybox for about another minute and type exit it then boots ubuntu 10.04 with no errors or issues.
Recently setup Ubuntu Server 10.10 on an old Dell Poweredge 2650. It seemed to be working perfectly until I did my first reboot. I tried changing the 'root' reference on the linux line at the grub menu with no luck. I suspect the problem is something else but I have no clue.
So far the behavior seems completely consistent. If I physically power the machine down and start it back up everything works perfectly. However, if I do a sudo reboot now I'll end up at the initramfs prompt. I'm not comfortable setting up my dev environment on this box until I'm sure it will be stable. In case it matters the machine is running a single scsi drive and doesn't have a raid controller.
I have my drives set to run fsck on boot up. This is the default setting for Fedora but if there is a problem it prompts me to run fsck manually. Is there a way to have Fedora just run fsck and fix any errors it finds on boot up?w in Debian distros you can put FSCKFIX=yes in the /etc/default/rcS file to do this. But I can't find the equivalent on Fedora.
I've just upgraded my wife's netbook to UNR 9.10. This seemed to go well and the netbook has been working fine since. Yesterday my daughter used the netbook with out any issues, but when my wife tried it halted during boot with:
Swap waiting for UUID: xxxxxxxxxxxxxx
After a couple of reboots it started working fine, but looking at /etc/fstab the entry for swap is different to the UUID shown in blkid Do I just update fstab with the UUID from blkid?
The case is that I've got 2 harddisks. On the one windows xp(slave) - and on the other one ubuntu (master). During the boot I get these errors... "Gave up waiting for boot device" "Boot args(cat /proc/cmdline)" "Missing modules (cat /proc/modules; 1s , dev)" "/dev/disk/by-uuid/f96603ce - does not exist"
These problems occured because of this: After using ubuntu I tried to reset my bios, because else it couldn't have found the disk with xp. And I didn't disconnect the disk with xp while resetting the bios. And now the system can't find the disk with xp any more when booting. Is there a way to finding the disk..? And I'm in doubt about IF I've resetted the bios at all. I miss a manual for PCCHIPS M851. May be it can take 20 minutes for the bios to be resetted? The shop where I bought the motherboard doesn't exist any more... and don't know the manufacturer. Could I damage the motherboard if I tried rebooting lots of times to get it work?