Fedora :: Hangs On Boot (mounting Local Filesystems)
Feb 13, 2010
I'm using Fedora 12 on my Thinkpad X200 and had no major problems since Installation of the Release Candidate. Unfortunately, since a week Fedora makes trouble when booting:
The system boots some times without any problems, some other times it hangs in the following way:
Code:
Gdracut: Mounted root filesystem /dev/sda1
dracut: Switching root
Welcome to ^[[0;34mFedora
Press 'I' to enter interactive startup
Recently i've upgraded my fedora 11 to 12 using the preupgrade command and now I have a problem booting! when i start the interactive boot it hangs after trying to run the service local, it looks as if its trying to boot because the cursor blinks really fast then blinks normally after a few seconds. no error was stated during the event. what seems to be the problem here?
When I try to start up 9.10 I can get past GRUB but not fsck. A file check will be started but no progress will be made and finally I get the 'General error mounting filesystems'.Trying in recovery mode I get this just before the fsck check
Quote: fsck from util-linux-ng 2.16 [8.016378] ACPI: I/O resource piix4_smbs [0xb00-0xb07] conflicts with ACPI region SOR 1 [0x0b00-0xb0f] /dev/sda1 goes fine Quote: /dev/sda3 has been mounted 34 times without being checked, check forced mountall: canceled
[Code]...
This seems to be slightly different than the other threads I've seen discussing this issue. It just all of a sudden happened, I didn't upgrade anything or have any crashes immediately prior.
What are others' views and experience regarding automatically checking filesystems (running fsck) at boot time?To be more clear, I have left the ext3 filesystems on this machine set to require checking after a fixed number of mounts by using tune2fs with the '-c' option. I've done this mainly because of the following (from the tune2fs man page):
Code:Youshould strongly consider the consequences of disabling mount-count-dependentchecking entirely. Bad disk drives, cables, memory, and kernel bugs could all corrupta filesystem without marking the filesystem dirty or in error.e using journalingon your filesystem, your filesystem will never be marked dirty, so it will not normallybe checked. A filesystem error detected by the kernel will still force an fsck on the nextreboot, but it may already be too late to prevent data loss at that pointBut what does anyone else do? Is there really much risk to disabling this automatic checking
Originally posted in Launchpad yesterday [Question #129083]:
Quote: System froze in mid-upgrade from 10.04 to 10.10 and now fails to boot, giving a 'general error mounting filesystems' message when loading [in either normal or recovery mode.] However, the boot menu remains accessible with the F8 key and is functional.
While in the 10.10 Live CD, using the chroot method in the grub2 help proved unsuccessful and returned this pastebinned result. The system is 10.04 64-bit running an nvidia card and sporadically froze with increasing frequency. No resolution to the freezing could be found online, which seemed associated with any of nvidia, usb, flash or even firefox. Can someone suggest an alternative to restore to bootable condition and resume upgrade without having to reinstall and wipe the drive? I also followed the copy alternative to the chroot method in the grub2 help and still get the same core dump for chroot and device not found error for upgrade-grub as posted in pastebin. I'm still running off of the 64-bit 10.10 Live CD.
Skimming other "general error mounting filesystems" topics in this section, I realise I may have to bite the bullet and cut my losses, since those other users seemed to settle for a reinstall. Any final advice out there I can try out?
I booted my laptop from the FC 13 Live CD.I'd like to mount the local disk while booted from the Live CD.In older versions of Linux, this used to be as simple as "mount /dev/sda2 /mnt/whatever".But, no longer Progress. When I do "fdisk -l /dev/sda", while booted from the FC13 Live CD, the /dev/sda2 partition shows up as "Linux LVM". My question: how can I mount the partition containing home directories from the "Linux LVM" partition?
I'm getting this error on boot of Mint 9 64bit. It gets to the grub boot screen (dual boot - Mint 9 32 & 64 bit) and I can boot into the 32 bit version, but the 64 bit results in that error. If I go into the maintenance shell & try fdisk -l, I get: fdisk: error while loading shared libraries: libuuid.so.1: cannot open shared object file: no such file or directory
My ubuntu stops when mounting system hdd. The screen display the following messages :
mountall:/etc/fstab: No such file or directory fsck from util-linux-ng 2.16 WARNING: couldn't open /etc/fstab: No such file or directory init: mountall main process (545) terminated with status 1 General error mounting filesystems. A maintenance shell will now be started. CONTROL-D will terminate this shell and re-try. udevd[560]: can not read '/etc/udev/rules.d/z80_user.rules. Ubuntu: clean, 474879/24231936 files/28016581/96898047 blocks root@i7:~# exit_
I suspect the disk manager pysdm that i had just installed today and it had crash during the previous session. The /etc/fstab file does not exist anymore and i cant rename the fstab.bak because the disk is read-only even for my root user
When I go to 'Places' on my panel, my windows drives are listed. I can click on one, it then asks me for password, then it puts a hard drive icon on my desktop. This is excellent.They are listed as '200 GB Filesystem' etc.My only problem, is how to make these icons stay after I shut down. I don't want to do this every time I boot up.
Just the last day or so, I've noticed a long pause when I boot my laptop, with lots of disk activity. dmesg says:
[Code]...
Why would there be a 15-second pause (during which the disk is slammed) between mounting root and mounting swap? During this time I see nothing but a blank purple screen, there are no cycling dots or text scroll. Is this normal and I'm just freaking out over nothing because there's no indicator of progress? GRUB default boot options: quiet splash nomodeset video=uvesafb:mode_option=1920x1200-24,mtrr=3,scroll=ywrap vt.handoff=7
I am using disk utility to partition an external hard disk. My intention is to boot linux off of the partition. However, I am unsure of which format to make the partition. Disk Utility in OS X only allows Mac OS X Journaled, Mac OS X, FAT, exFAT, and free space. Which one should I use?
I have been using F10 since its release and have not had any trouble until now. During my last session, I ran an update. Today when I boot my desktop (single boot btw), it hangs just after the boot loader. The only sort of warning is:
eth0: link up, 100Mbps, full-duplex, 1pa 0x45E1
I have browsed the forums to no avail. Other have the same issue, but with no posted solution. I have tried disabling NetworkManager, but I think it may be the service that runs after NetworkManager.
Boot-up hangs at black screen with blinking cursor in upper left corner for over 2 minutes before continuing. I select F 14 with grub hit the enter key and go straight to a black screen with blinking cursor. Hitting the esc key does nothing until boot-up actually starts. Afterwards, boot-up is perfect. I had this problem a few upgrades ago and the fix was simple but I can't remember what I did. I've searched every phrase I can think of and can't find a thread that addresses my problem.
I have a F 13 kernel on my machine and have no problem booting it.
After doing a reinstall, and then upgrading, I have a problem: as the boot script comes to ATD, it hangs. Someone suggested doing an interactive start ---- and it worked! Just say no to ATD, and boot goes well. Of course, I don't really want to do that each time. How do I remove it? That is, get it out of the init.d or rc.d boot procedure
I've got a semi-retired hdd (with a few bad sectors my disk utility tells me) formatted in ext4 that can be mounted onto the Desktop after boot provided root password is offered first. I thought it would be straight forward to mount it at boot with something in etc/fstab like :
Code:
/dev/sdb /home/Jo/Desktop ext4 But this doesn't work, is there a glaring error here ?
Various threads suggest permission restrictions could be the cause but i have had no success with them
Whenever I boot fedora core 13 it starts Plymouth and a txt progress bar starts at the bottom. Whenever it gets to 100% it flickers a little bit then does nothing. The system doesn't hang I can still crrl-alt-delete and it shows the processes stopping. When it displays the programs starting it gets to jexec and nothing happens.
The situation is say all I have is a windows machine and I remotely connected via ssh to a Linux machine. Is there a way I can mount my local CD-rom on the remote Linux machine?
I have just completed a dual boot installation of FC10. The install was done from CD's I downloaded from the Fedora website. The installation (seemed to have) went fine, and the machine still boots into XP if selected from the menu. The Fedora installation does not complete the boot process. I have three bars that move across the bottom of the screen, and the Fedora 10 graphic tuns white, and then the system hangs. I have let it sit at this screen for as long as 30 minutes. The screen will blank occasionally, but returns to the same place if I hit a key on the keyboard.
I have it installed on an old HP E800 netserver, running dual P3-866mHz processors, 2GB ram, a ATI Radeon 7000 video card, and three 36GB SCSI drives, non-raid. I know FC10 will run on this machine, as I have a friend running it on another E800 without any problems. This machine does have on-board video that is disabled only by plugging a different video card in (Phoenix BIOS).
In F10 the boot sequence hangs just after loading anacron. I booted with interactive mode and after saying 'yes' to starting anacron I'm prompted to start 'local'. When I say yes, my system hangs.
I've seen quite a few posts regarding very similar issues that people were having. None of them seem to have a clear cut solution.
Some posts mentioned about the wrong video drivers, however I've been using the same video drivers for a couple of months now and never experienced this problem.
I looked at /etc/rc.local and all it has in it is 'touch /var/lock/sybsys/local'
I also looked at the file above and there is nothing in it.
Any ideas/solutions? Everything was working just fine the other day. so I'm completely baffled.
This is one of those newbie questions about where I look to find error messages so that I can understand what the issues might be. My Fedora 12 setup invariably always hangs whenever I login following a cold boot. I login to x/g-nome, the screen clears and the initial background appears and then that's it.
I've been getting out of this by switching to another TTY (CTRL + ALT + 2), login as root and issue "shutdown -r now". System re-boots and I can login normally. I can see a stream of messages, I think relating to x scroll up the screen rapidly after the shutdown command. I'm not fast enough on the Pause button to read them. My question(s) then is... is there somewhere I can look to see what those messages might be? From the symptoms described initially, anyone have any thoughts on what the issue is likely to be?
I have just upgraded my F11 x86_64 system using the DVD ISO.
After rebooting as requested: 1) Cupsd fails to start - it can't find libaudit.so.1 (this doesn't worry me in itself). 2) Boot process proceeds until starting hald. This gets an OK response, but then the process hangs. No further output appears on the console. Pressing [ENTER] just causes a blank line to appear on the console. Pressing CTRL-ALT-DEL causes a reboot, and the same symptoms re-occur.
I'm tempted to boot with the rescue disk, save a few critical data directories, then start afresh with a clean install, but is there anything I can do to salvage the upgrade?
I currently dual-boot Windows Vista and Suse 11.2 on my Gateway desktop machine. I'd like to try out Fedora in a triple-boot situation.
My trouble is that the F13 Live CD hangs during boot. I've checked the hashes of the downloaded ISO files, and done burns on multiple media. During booting with the Live CD, my box hangs and I have to use the physical power button to turn off the box.
I've tried the 64-bit KDE spin (my preferred choice), the 64-bit GNOME version, and also the 32-bit KDE spin, and all of them hang at the same point. Removing the "quiet" boot option shows that it hangs after setting up my built-in card reader. When I installed Suse 10.3 on this same machine, I had to use the flags "acpi=off" and "brokenmodules=pata_it821x". Would the syntax be the same if I wanted to try with those boot options with the F13 Live CD?
Using the ISO files in VirtualBox inside my working Suse install works just fine.
After Gnome logon it may hangs in any moment (window scroll, app start, opening url)
If sound was playing in that moment it continuously repeats last sample (about 1 second length), but do not respond to mouse move/click or keyboard. If to let it stay in this state nothing change - sound sample still repeats and no response to input. I need to reboot it by reset button. Sometime when I press reset nothing happen then after couple of seconds computer turns off, after 1-2 sec on and then starts booting.
During first 15-20 minutes after booting it may hangs multiple times but after that it works without problems.
Tried do not logon 20 minutes after boot - do not help, it hangs anyway. Only helps logon and do nothing for awhile.
This behavior have started after F12 installation. F13 installation changed nothing, only F11 worked perfectly.
I recently upgraded through 'YUM' from Fedora 14 to Fedora 15. The upgrade appeared to be successful until it re booted, ever since then it hangs at Code: Started SYSV: Enable monthly update of smolt. I have downloaded the ISO and burned it to DVD on another system which I used to try to rescue the installation, so far to no avail. My system specs are in my signature below (Laughlin is what I upgraded from).
I am installing Fedora 15 as a guest machine on virtual box. the installation completes fine, but it gets hanged on the date and time screen during first boot. Even on clicking "Forward" button it doesn't work and just gets stuck there. I am using windows 7 as the host machine and I have given 1 GB ram and 8 GB hard disk to guest fedora OS. Before the installation, I checked the media also it was shown to be correct. The media I am using is virtual clone drive for DVD ISO image. VirtualBox version 4.1.2 was used.
