I've installed Debian Lenny from USB with the small 8MB netboot image. I only chose "Standard system" in Tasksel during install, to get a clean, minimal install. I also chose for LVM and a separate partition for /home. I have one 1.5TB SATA drive in this machine.
Now everything seems to install just fine, but when I reboot I get the following error:
fsck.ext2: No such file or directory while trying to open /dev/sdb1
I get offered to enter a maintenance shell, or press CTRL-D to resume booting. When I do, the system boots fine and nothing seems wrong. But it is inconvenient, because I can't reboot the machine without physically going to it to press CTRL-D on the keyboard
I have googled for this error and it is mentioned on several forums, but they were all related to other things specific to their installs/machines.
(ps. the only slightly strange thing during install is that the Debian installer included my 1GB USB thumbdrive when it shows all the drives and the partitions before formatting. I removed the USB thumbdrive directly after install, but if I plug it in, I still get the error)
These are the errors during boot: code....
I've only installed Debian on my laptops, which never had any problems.
I'm trying to compile a main.c file that contains a while statement. Embedded in the while statement are functions that are being called. After the while statement, I have 2 more functions being called, one to find the average(getaverage), and one to print the results (printstuff). I also used a header file (my.h) that contains all of the needed #define and #include, along with each of the void function() statements.
There isn't any problems with the while statement/ the functions in while, but when I try and compile main.c I get the following errors:
main.c error: conflicting types for 'getaverage' my.h error: previous declaration of 'getaverage' and then the same thing for 'printstuff'
I have a Dell Mini 12 running what I think is Ubuntu 10.10 Netbook Remix. It won't boot all of a sudden, saying 'No init found'. I've been through [URL].. which is VERY close to my problem but I cannot get Disk Utility to work when running off my Live USB. Asking it to check the hard drive results in it telling me the filesystem is 'not clean'.
Is it possible to run fsck on the root file system? My Ubuntu 10.04 seems to be checking it's fs at boot... It shows that the file system is in use and can get severely damaged! Or the only possibility is to run it from a live CD?
I've got a system that has given me problems since day one. It's my oldest kids computer and she seems to open about twenty tabs in Firefox. The computer will freeze and she'll manually hold down the switch to reset. I've instructed her to please stop shutting it down manually but kids never listen.So anyway the thing reboots into initramfs. Seems unable to do anything with the hard disk. Now heres where I run into problems. In the past I've removed the drive and put it into one of my other Ubuntu boxes then ran fsck. fsck always recovers the journel quickly and I pop it back in and all is well.First question or situation if you will. I have tried left and right to get fsck to work from the livecd. If I let the livecd boot up and open a terminal fsck /dev/sda1 comes back with device or resource busy. Apparently the livecd get stuck automounting and causes problems.
I'm really tired of putting this thing in another box. I tried downloading knoppix but it wouldn't burn off for some reason. I've tried booting into rescue mode, but that seems to be missing from the livecd these days?Can I boot into single user mode somehow? Kill off some process that is causing the resource to be busy? I'm thinking once I maybe flagged the drive as dirty and had it clean itself on reboot.. will the livecd pick up on that?ok.. so thats the first situation.. second is upon recently fsck doesn't fix the problem. The drive recovers just fine, but after using the computer for a short while the drive will somehow magically mount as read only.. and then programs will freeze and shutting down is hard to do.
I would like to know if there is a way to do an unattended check on the root file system on my servers, *and* send emails in case of errors.
I know you can schedule a root file system fsck during boot time - but the root file system will be mounted read-only - so if fsck finds any problems - it can't email away a warning, or write the result to a file - or can it?
Essentially I would like my servers to do a self-check of the root file system periodically - and to email me if it fails. I just can't think of a way to get it done.
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'm running an Acer Aspire 1830T-3721 dual-booting Windows 7 with Ubuntu 10.10 (Desktop).
Background: So first I dropped my laptop a couple feet while Windows was running. The laptop immediately shut off and then tried to boot. Booting Windows results in an unfortunate "Windows has encountered a problem communicating with a device connected to your computer. The error can be caused by ... faulty hardware ... Status: Oxc00000e9 Info: An unexpected I/O error has occurred." But Ubuntu booted fine, and could access my NTFS files fine, so I was trying to work on the problem from there. I try a few utilities, looking at the partition table, etc without actually applying any changes.
Then I run a fsck on the drive. It loudly warns me that if I continue on a mounted drive, then I'm going to mess things up. In a moment of stupidity I push on, thinking that surely it would ask me for more configuration, or confirmation, before actually starting. The fsck runs for about 1 second before I Ctrl-C it, running some preliminary stuff and then just starting pass 1.
After this, Ubuntu won't boot anymore. Instead, it hangs just after the init-bottom script runs. If I boot with init=/bin/bash, I can get to a shell, and see that my file system is still there, but not sure what else to do.
I've been running off of a SysRescCD LiveCD, from which I've looked at the drive with testdisk. Testdisk reports that "the hard disk seems too small" while showing me the partition table.
I ran a fsck on the Linux partition; it fixed a bunch of things. There has been no apparent effect on the boot behavior.
I can access all my files, back them up, and reinstall Ubuntu, but I'm hoping there's a better solution, perhaps one that will also help me repair my Windows installation (but I'm looking at one problem at a time here).
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.
I have Ubuntu 9.10 installed on my HP desktop, but I'm running an older version (8.10) on a live CD so I can at least get online to ask for some When I tried to log on earlier it went to a command prompt and said the 'file system check failed' and to run fsck manually. I entered 'sudo fsck' at the prompt and I selected "y" to fix all the bad inodes, when it was complete it told me to restart, I then entered 'sudo restart' at the prompt and it said 'sudo uuid unknown'. I have not installed anything recently and I'm not sure what to do.
loading /usr/bin/teclafsck failed. please repair manually and reboot. the root file system is currently mounted read-only. to remount it read-write do:bash# mount -n -0 remount,rw /attention: only control-d will reboot the system in this maintence mode shutdown or reboot will not work.
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?
Today I did an update on my Debian 6.0.0 installation, which included a kernel update. I also did an Nvidia driver update, afterward. All well, until upon a third boot up an fsck check was forced (34 mounts). Some odd behavior ensued. At about 19% it exited the check, printed what appeared to be a load of inode numbers with error messages, and "froze" with the caps lock and num lock lights on the keyboard flashing.I did a couple of grub recovery modes, each which advanced a little further, and all is well again. However, it concerned me. Where in var/log do I find the file of that particular fsck activity?
RHEL 5.4. I'm facing the following error after rebooting the server: /dev/VolGroup01/u04: UNEXPECTED INCONSISTENCY Run fsck Manually" *** An error occurred during the file system check. *** Dropping you to a shell: the system wil reboot *** when you leave the shell. give the root password for maintenance:
-Previously I performed a lvreduce command on a LV, after the lvreduce, I reboot the server. -After login as root I run: e2fsck -f /dev/VolGroup01/u04
But, it shows: The filesystem size (according to the superblock) is 5218304 blocks The physical size of the device is 1310720 blocks ... either the superblock or the partition table is likely to be corrupt abort<y>? no pass 1: cheking inodes, blocks, and sizes error reading block 1310722 (invalid argument) while doing inode scan inore error <y>? y
-Additionally, trying to lvdisplay, it shows: Locking type -1 initialization failed I have no important data on that LV, but I can not boot the server properly.
I want the filesystem of my external drive to be checked periodically after a numer of mounts. I put 2 in the sixth colums of fstab for this partition
Code: /dev/sdb1/mnt/hdext3rw,dev,sync,user,noauto,exec,suid02 and I use the tune2fs to set the maximum mount count to 32. Code: tune2fs -c 32 /dev/sdb
now the mount count is 34 and the date of the last check is not recent, so apparently the auto fsck has not been performed. Probably because this partition is not mounted at start-up but I usually mount it manually.
I wanted to know how can I make fsck automatically fix HDD errors when it needs to check HDD during boot up and do not ask user for it . I found some of fsck related scripts in /etc/init/ and /etc/init.d/ but I don't know what to do with them.
I have a server with Debian on it that I regularly reboot after upgrades. Sometimes (on schedule) fsck will check a disk when the computer is booting. With the exception of sitting in front of the console to observe the fsck, how can I determine the difference between a problematic halt and an fsck (besides waiting out the fsck, hoping it is an fsck)?When I send the computer down to reboot, I will usually have a terminal window open pinging the computer so I know when it has come back up. My first thoughts drifted to fantasizing about hacking fsck to respond to pings with some special magic byte so you could tell via ping that a computer was fsck-ing, but I'm thinking there have got to be easier ways..
I have two ext3 lv's of 4GB and 10GB in my hda8 partition, and they are automounted by /dev/mapper/ in my /etc/mtab files in each of the four distros (Suse9.3, OpenSuse10.2, kubuntu7.04 and Debian Lenny 5.0.3). Since ext3 is a journalled fs I feel I ought to fsck their integrity every 3 months or so, however I don't know
a) whether they must be unmounted before running fsck, b) whether I should use a live CD such as knoppix to run the fsck command, and c) whether I can and/or should run fsck /dev/hda8, or whether I should somehow fsck each lv seperately?