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 am hosting a few customer servers now, all of which are virtual machines running on a CENTOS 5.x host. Each Centos host has a couple of extra drives. When I formatted them ext3 they automatically had a schedule of a full forced fsck after 6 months. Do I really need to do that check regularly? It results in a fairly large outage since my disks are each 1TB and there are up to three extra drives on each server. I try to reboot these servers every 6 months but this part adds a large amount of time to a routine reboot.
I had a server with CentOS 5.5 and Asterisk fail today most likely due to the power failure. I guess the stupid electrician turned the power ON and OFF multiple times while changing the burned out fuse without unplugging the PBX. It was set in CMOS to power back on when there is power outage so my two HDDs which were set in RAID-1 now shot.
Trying to start the system and it goes through some check and fixes and then tells me to do Ctrl+D or enter password and run fsck. I have tried both methods and I don't think they yeild anything.
Ctrl+D reboots and same store again with the system fixing and asking me to Ctrl+D again. Putting the password and doing "fsck -y" gives many errors and it fixes it and then it just keeps looping. I am afraid this is making it worst than better. So, after few loops I did few more restarts and just give up. Took out the HDDs and installed new ones and install CentOS+Asterisk so business runs as usual on Monday.
However, I am kind f*ked if I don't get the files out of these HDDs. This is my first time using fsck and also encountering this type of a problem. What is the normal procedure when fixing inodes misplaced in a case like this? and what should I do to at least be able to grab my files?
I have already connected one of the drives to Windows and used Disk Internals (which maps Linux drives) but I see only folders with no contents except for /tmp/ which has contents. While the HDDs were in the system I could actually browse files and they were fine. I am really keen to get the drives fixed but I am also afraid that bad usage of fsck might replace lots of files and burn it all.
My centos machine suddenly stuck, the hdd LED flashes constantly, and the system reacts to all my operations very slow. I even cannot log in to a native terminal (always timeout). I had no choice, I pressed the power button. Reboot once failed. The system failed to find mount points.
I inserted the installation disk into computer and entered rescue mode. But I found everything was there. And another reboot brought up the system. I wonder what was the process that stuck my system.
When I put my computer running Ubuntu 9.10 into suspend or hibernate the screen goes black with a little flashing underscore in the corner and when I try to bring the computer out of suspend or hibernate nothing happens and I am forced to manually reboot.
I know I can force a fsck run at next reboot using
Code: shutdown -rF now
or
Code: touch /forcefsck
can I force the fsck to more indepth checks such as doing directory optimisations, bad blocks checks, etc. maybe by passing parameters to the fsck call during startup?
I just installed 10.04 from the minimal install cd (twice), and when I boot it up, it runs fsck on the 3 partitions, shows they are clean, and then nothing. I can't even get to recovery mode. I had previously installed 9.10 fine on this computer. I can't even find out what the real problem is, even with the quiet splash disabled. It just stops after successfully running fsck.
I have a server that said a volume was dirty and to check it at reboot, so someone did a shutdown -rF now. Only problem is the other volumes are HUGE and it will take forever, which I cant have happen. The volume with the trouble is non-critical so I could take it offline and check it that way if i can get this to boot quickly. How can I do that if its going to auto check every volume on reboot now?
16GB RAI've been running the Debian-based Proxmox VE on it for six months or so with no problems.Today I loaded Centos 5.5 x64. During a reboot, the file system crashed and fsck couldn't repair.I loaded it again, did all the updates, and loaded my applications. On about the third reboot, it crashed again and fsck couldn't fix it.I don't really know where to begin. I doubt seriously that any hardware has went bad since yesterday.
My old laptop has a broken screen. I tried using an external flat screen and win-xp would not run this screen. This is how I came to learn about Ubuntu. I loaded Ubuntu 9.4 and the computer worked with the external screen. The only problem was that during the boot process the (kernel text?) the white text on black screen over ran the edges of the external screen. Once the Ubuntu was loaded the window fit the screen perfect. Now my new problem. After a year of perfect use, the battery ran down and the computer shut itself off.
When I put the charger back on and rebooted the laptop, the ubuntu partly opens then hangs up on the kernal (white text on black screen) because of the screen overrun problem I can not read the text. I can boot still boot from the 9.4 CD. Is there anyway I can correct the problem by re-installing 9.4 but not wiping out my person data and files. In other words is there any way to repair the O/s that is defective, without losing my work?
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?
I am using Ubuntu 9.10. Every time I try to reboot my system it hangs. Shutdowns work properly. I've done multiple re-installations. Nothing I've tried fixes the problem. Does anyone have any suggestions?
I have set up certain portions of my web site to be forced https:// How do I force, non https:// protocols. I know this sounds confusing, so let me give you an example.
I'm on an HP Pavillion dv1000 laptop. I used a live CD to install Ubuntu 10.10 to an external USB hard drive. The install completed successfully, but after a reboot I am stuck on a black screen with a white cursor. Before that I see nothing but the initial HP startup screen. I am able to run the live CD without problems, and I have been running Ubuntu from a 4GB thumb drive (which I installed on using the same live CD that I used to install on my current external hard drive). I had no problems whatsoever running from the CD or thumb drive, so I can't figure out why the external hard drive would be so different.
Also when the machine boots up I get a message saying something about IOMMU should be set in BIOS, but I can not find any such setting in BIOS. I do not know if this is related to the hanging.
I thought I had a hard drive problem at first so I tried a different hard drive. Same problem.
The mother board is an ASRock N68C-S.
One other thing, where is the file located that boot up messages are written to?
fedora 14 did an automatic update and on reboot it hangs displaying the "f" before the login menu. The "f" is how I now feel......... I do "fn+f2" as it is booting and it displays the sequence of loading items which report all is "ok" until it gets to "jexec services" and then it hangs. I beleive the "jexec service" is a Sun Java item but I am not sure. I have been using Fedora successfully for a number of months and need to get data from the machine.
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 )
Have openSUSE 11.1 and (AFAIK) KDE 4 on an older notebook; worked OK for weeks, then booting became a problem and the OS seemed to go to sleep between keystrokes: now the cursor stops blinking, the clock stops running, and nothing happens after clicking a radio button until the mouse moves. Am now 25 minutes into a reboot, hung at "Unmounting file systems" but it also hung for a while when changing run levels. Is this related to the stability problems with 11.1 I've read about? Possibly KDE? Where would I adjust a config to use kde 3.5 rather than 4?
The server hangs or reboots when I install Fedora 13 x86 (32-bit) from DVD onto a quad core server (64GB of mem, 16 cores). Sometimes it gets as far as starting anaconda before the hang or reboot. I've been trying different combinations of kernel options, such as vesa, pci=msi, irqfixup, max_add=3072M, noapic, nolapic, noirqbalance, maxcpu=2... But whatever I do, it hangs or it reboots. The 64 bit versions of RHEL5.5 and RHEL 6 Beta2 installs without problems.
I installed Ubuntu in my PC alongside winXP. I downloaded the ISO and mounted it using a virtual image software (PowerISO used in winXP). I installed Ubuntu using wubi in a 20GB partition. During installation it asked me how much space should I give, I gave it 11gb. Everything went fine. I rebooted but now the computer hangs during startup. I went to verbose mode to see what the error is and found out that everything is ok. The last line that apears is "Setting sensors limit [OK]" and then nothing happens. I have tried every option (safe graphic mode/ demo mode etc etc) but the computer hangs.
Having a problem with my system hanging after updating Fedora 12. Here are my system specs:
Gigabyte MA770-UD3 motherboard AMD Phenom 9950 Quad Core 6 gig Corsair DDR 800 1 x 160 gig SATA (OS) 1 x 500 gig SATA (data)
I have my system configured for dual boot with Windows 7. After installing F12, I can reboot with no problem. However, after I install the kmod-nvidia drivers, my system hangs on reboot. If I press any key on the keyboard, it will start to load, the freeze until I press a key again. I have tried both Fedora 12 x64 and i386 with the same results. Here are the steps that I took to install the kmod-nvidia drivers code...
Does anyone have any suggestions as to what I am doing wrong?
Ubuntu server hangs when I boot with a wired Ethernet connection. The last thing I see in the console is code...
I have no problem when I boot to a Wifi connection even when Samba and openssh-server are installed. I see the same sequence of lines in the console as I reported initially (including Reloading, Restarting), but then the output continues with
* Starting the Winbind daemon winbind
Both the wired and wireless connections use dhcp. Obviously, I installed the OS using a wired connection, so it worked reliably once. I'm stuck.
P.S. I tried dhclient -r before rebooting. The machine did not shut down correctly and when I forced a reboot it appeared to hang at the usual place. However, after a long delay it proceeded to boot. Perhaps I am observing a delay due to a very long timeout. I will try another reboot now and check again in the morning.
I was using Ubuntu 9.10 and was using fireftp ( firefox plugin ) to do some ftp operation. And then I noticed firfox is fozen so I reboot my pc by switching off the power ( restart doesn't work ). When I turn it back on again, no GUI anymore. I was taken to ttyl login commend.
