Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
I am not well versed in linux at all. I managed to get my system configured, and it has been running very nicely as a server for the past 3 weeks.
Yesterday, while transfering files, it crashed. When I try to reboot I get - no such file or directory. I fried doing a fsck but it too found nothing.
I am running RH 7.1.
As it is going through the boot cycle, it fails and gives me the following
mounting proc: file system dup2:bad file descriptor
Configuring kernel parameters: dup2: bad file descriptor
Setting Clock: dup2: bad file descriptor
then goes into
/etc/rc.sysinit : dev/null; : Input/output error - a few times and then tells me
An error Occurred during the file system check. Dropping you to shell; the system will reboot when you leave the shell. Give root password for maintenance.
If I go through the installation screens, and get to the drive partitioning are it looks like when I try to view the partitions that the names ie /home /boot etc are not there. Does that make sence.
dup2 "Bad file descriptor" in essence means "cant check, cant mount, cant read". Processes spawned tru rc.sysinit (the boot script) can't get file descriptors off of /proc, cuz the partition /proc is on isnt fsck'ed, so /proc can't be mounted in read-write mode.
try booting off the install cd with "linux rescue" or use a bootfloppy, or use a bootdisk like tomsrtbt.
run fsck with the -f (force) on /dev/(all partitions).
if any errors come tru, plz tell us exactly what.
*just my curiousity, did u have a good security scheme on ure box?
Got through all of the fsck ... here are the results
HDE1 /boot clean
HDE5 swap - The super block could not be read or does not describe a correct ext2 file system. Bad Magic Number in Super-Block while trying to open /dev/hde5
I'm also getting this on about 10 of my machines. Is it hardware? I have a auto update script running which compares RPM's on the local system to updates.redhat.com and if updates.redhat.com is newer it does a rpm -U --nodeps package name. Could this be a problem?
Here's my quick fix for this but it sucks because it keeps happeneing again and again.
boot off toms boot disk
mount /dev/hda7 /mnt (hda7 = / partition on my machine)
cd /mnt/dev
rm null
mknod null c 1 3
chmod 0666 null
cd /
umount /dev/hda7
reboot
if you have the redhat cd you can do this 2 by just gettign into the install and then pressing alt+f2 and it should bring you to a sh term.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.