FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
could you please help me with this problems. We have several computers running Fedora Core 1. All of them were working perfectly for some time (several months). Then last week two of them stopped booting. They start booting and then stop after message Enabling swap space. All the computers have the same fixed configuration running just plain Fedora with one custom application. After analyzing user's behaviour we think it may have something to do with use of USB key. Our users plug in USB key to transfer some data. The only commong behaviour we could identify was that if the users removed the key during shutdown or sometimes plugged it in during startup it rendered the computer unbootable.
We have tried everything, the computers don't have plugged in any peripheral, only keyboard and mouse (and we tried even without eyboard and mouse) but they will not boot anymore.
Can anybody advice me how to troubleshoot this? I would like to know if I can find out what is causing the problems or how can make the computers boot again to get to the data and make them usable again. Reinstall is not an option since as I said, the computers have fixed configuration and nothing but the data changes on them so nothing should be different from those working computers. Is there any explanation how can this happen? Any help would be really appreciated.
I'm having the same problem with a fresh install of Fedora Core 2. The system was working fine with Redhat (v7 I believe). From what I've been able to read in other places after the enableing swap space says okay then the system searches for hardware, running INIT scripts.
I have forced file system integrity check and the system still hangs during Enabling swap space? Even if I get interactive boot it still hangs before I can do anything. Any idea how to troubleshoot it?
Try booting into single user interactive... then shut-down cleanly and start-up again... I set up a fixed /etc/fstab entry for my usb-key to avoid hardware checking and fstab rewriting (makes for a faster boot-up as well).
Just a shot in the dark here.... Maybe the USB key is causing the device numbers to change? Like what used to be dev/hdc3 and was the swap space is now dev/hdc4 to the machine. But the mount line in fstab still says dev/hdc3, so initializing the swap space hangs.
Originally posted by jrittvo Just a shot in the dark here.... Maybe the USB key is causing the device numbers to change? Like what used to be dev/hdc3 and was the swap space is now dev/hdc4 to the machine. But the mount line in fstab still says dev/hdc3, so initializing the swap space hangs.
Originally posted by lupin_the_3rd Try booting into single user interactive... then shut-down cleanly and start-up again... I set up a fixed /etc/fstab entry for my usb-key to avoid hardware checking and fstab rewriting (makes for a faster boot-up as well).
I did the single user interactive and it worked perfectly for me. Thanks for the tip!!
another stuff is that it's possible to be the next thing not exactly swap related it happened to be with usb printer .. it was almost a saga till I fixed it and interactive was not applicable it still hung, but running kudzu kind of fixxed stuff
It is not because of swap space. The reason is one or more service starting-up problems during boot-up. You should go to services and select "no automatic start" for some services during boot. I suggest you start selecting "no start" for kudzu and any other network query services. Just to be sure select no-automatic start for all services and start them manually. You may also see the log's for the best candicates.
but with kudzu it was very strange with this printer.. I really spend much time initially if the printer was plugged it crashed and the "swap" thing, why is it so hard to use kudzu I mean I do not enable it for automatic but as the printer was detected for another usb hub and as I switched it it really messed up.. I had to reboot many times till it deleted previous configuration for the printer and so on.. maybe because of some timeout(meaning times of reboot till it confirms the absense of piece of HW)
In general my question is is it possible to better handle usb stuff? like usb-sticks and printers..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.