Debian Hardware :: Boot Warning Fsck.ext4: Unable To Resolve UUIDs?
May 15, 2011
I have $ uname -a
Linux kub 2.6.32-5-amd64 #1 SMP Mon Mar 7 21:35:22 UTC 2011 x86_64 GNU/Linux
Most of the time when I boot my PC I get an error about fsck.ext4: Unable to resolve... I don't know why it's happening.
The problem is happening with my external drive that has 3 partitions:
About 90% of the time I boot I do get the error. Sometimes after getting the error I can login and the external drive (/dev/sdc) is already mounted:
$ df -H
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 15G 8.0G 5.8G 58% /
tmpfs 1.9G 0 1.9G 0% /lib/init/rw
udev 1.9G 246k 1.9G 1% /dev
tmpfs 1.9G 738k 1.9G 1% /dev/shm
The UUID's in the error file match the output of the command blkid. And the UID's of blkid match the fstab UUID's. I don't know what to do at this point.
fsck.ext3: Unable to resolve 'UUID=theUUID' where "theUUID" (without the quotes) is the UUID
I believe this is caused by me trying to get lvm to use the external /boot because when I had unmounted the external /boot, it was creating a /boot in root. So, I booted a live cd and mounted the external /boot where /boot in the root volume is supposed to be. Basically, I think the problem is that I need to make my /boot (which is the only ext3 partition in the entire system and I want it that way) "relate itself" to the lvm root so that it boots into the system. As mentioned earlier, in the live CD, I made the external /boot mount itself in the root's /boot but I don't know how to tell the system to do this on its own while booting without my assistance. I chrooted from the live cd which involved a lot of tedious stuff but basically the important stuff I did were:
Seems like I misplaced this topic. Should have been in general help. Sorry! Any moderator feel free to move this topic. As I was creating a swap partition, something went wrong and I ended creating a much bigger file which consumed all my empty space. Ubuntu stopped working and now I can't seem to fsck / mount my disk. Currently I'm on a live cd. fsck will give:
Code: e2fsck 1.41.12 (17-May-2010) fsck.ext4: Device or resource busy while trying to open /dev/sda2 Filesystem mounted or opened exclusively by another program? However, the file system is not mounted.
Code: Select alldone. Setting parameters of disc: (none). Setting preliminary keymap...done. Activating swap...done. Checking root file system...fsck from util-linux-ng 2.17.2
An automatic file system check (fsck) of the root filesystem failed. A manual fsck must be performed, then the system restarted. The fsck should be performed in maintenance mode with the root filesystem mounted in read-only mode. ... failed!
The root filesystem is currently mounted in read-only mode. A maintenance shell will now be started. After performing system maintenance, press CONTROL-D to terminate the maintenance shell and restart the system. ... (warning).
Give root password for maintenance (or type Control-D to continue): _
For now, I just don't know what I should to do next to my system has started to work again...
OS: Debian unstable 32bit, kernel 2.6.32-2, grub 1.98 from late january 2010 (only have working net-access from work now, so I am grabbing information from memory). EXT3 and EXT4 support is compiled into the kernel along with chipset/scsi/sata support (not as modules), and I have tested to boot ext3 with it before proceeding. Prereq: my old disk started to have too much S.M.A.R.T errors, so I bought another one, put in a USB cabinet, added swap and ext4 partition/filesystem to it, and copied over all data from the old system to the new that was mounted at /dest using the command "find ./ -xdev -print0 | cpio -paV0 /dest". Swiched disks, so I now have the ext4 disk sitting at /dev/sda (partitions: sda1 => ext4, sda2 => swap), and booted into rescue-mode from cdrom, using /dev/sda1 as root with a shell on. After doing this, I performed the following commands:
mount --bind /dev /dest/dev chroot /dest
modified the /etc/default/grub to instruct the kernel to boot using ext4, ran grub-install --recheck /dev/sda ran update-grub to modify /boot/grub/grub.cfg (which looks as it should) After doing this, grub finds my partition and mounts it. It however stalls with the message: "warning: unable to open an initial console" and does nothing after this point. I have no ramdisk, but my old kernel booted fine from ext3 (and still does if I copy it to a ext3 partition), and since the ext4 support is compiled into the kernel - should I really need a ramdisk?
I go to bed and my computer is fine and working. I come home from work, no signs of a power outage, and my computer has errors regarding a corrupt disk. Drops to Cmd prompt. My problem is that I want to do the proper recovery on it, and my googling doesn't seem to help. All I see is stuff about how FAST fsck is, but no one wants to talk about how to use it. Besides, I better check with people before I mess everything up.
I have the FC12 install disk I used loaded up now, at the cmd prompt. I have my system mounted, an EXT4 LVM. Do I unmount and then run fsdk.ext4 -fp /dev/mapper/vg_mysys-lv_home ? (lv_home is the one reported as corrupt during boot)
My openSUSE 11.2 system has periodic running of fsck disabled for ext4 filesystems (Maximum mount count = -1, Check interval = 0). What is the reason for this? Is it because fsck is not necessary on a periodic basis with ext4, and only necessary when errors are detected? Or is it because fsck has problems working on ext4 filesystems?
The ext3 filesystems do have it set (Maximum mount count = 500, Check interval = 5184000 (2 months)). I would like to know why fsck is not set to be activated for ext4.
I recently downloaded Ubuntu 10.10 and installed it onto a 250gb removable disk using a 240gb ext4 partition and a 10gb swap space.
I am using a Sony VAIO (VPCF115FM) and it would appear that my BIOS is very limited as to bootup options. I can only choose internal HDD/external device/network/CD Drive. I cannot check whether or not my BIOS is able to recognize the external ext4 (but from experiences so far it would seem that it cannot)
After much tinkering i got my internal windows 7 to recognize the drive as ext3 (Used ext2 volume manager to add a registry entry for the drive). However, I need to unplug and replug in the drive for it to be recognized, if i leave it plugged in from booting it shows up as unrecognized.
Summary: I would like to be able to boot up Ubuntu off this external drive, but as of now it would appear that my BIOS is unable to recognize the drive. Windows can recognize it as ext3, and I can access contents of the ubuntu partition from windows.
how I could get this working that would be fantastic, i've tried formatting the drive to other filesystems (ext3,ext2,XFS) but none of them would work either, so any information would be sweet
I'm using 10.10 (updated from 10.04) and from the 10.04 I had problems when the system updated the kernel. After a kernel upgrade I can't boot to my other linux(Backtrack) due to wrong uuids. I must go to /boot/grub/grub.cfg and remove the uid and put /dev/sda5 for example. If I don't edit backtrack loads to busybox. Is there any way to fix that parameteres permantly? Because I don't want to make this change every time.
I am running the latest debian lenny OS and with kernel 2.6.26-2-686. I have a common /data partition for both Ubuntu and Debian which is ext4 file system. I am not able to mount this volume. The error message reads "unknown filesystem type ext4". How do I fix this. I searched the net and there was a link talking about this
i am new to linux . i have the basic knowledge of networking. a week ago i installed debian Lenny version on an old pentium 3.in addition i installed a ddclient configured it according to many tutorials....i searched google a few days but didnt find my case.i ran the folowing command :
how do I tell grub to stop trying to boot based on UUIDs? I've been dealing with this for about two years now. I have this one system, a PowerEdge 1550, that for some reason WILL NOT boot using a UUID, and will only boot if I edit the first entry in grub, remove everything to do with UUIDs (completely delete the search line, replace root=uuid=[uuid] with root=/dev/sda1). I can't seem to make these settings stick and now with 10.10 there's no longer a menu.lst to edit. So, in short, I need grub to stop trying to boot based on a UUID. Absolute paths, baby. That's what I need.
i have the basic knowledge of networking. a week ago i installed debian Lenny version on an old pentium 3. in addition i installed a ddclient configured it according to many tutorials.i searched google a few days but didnt find my case. i ran the folowing command :
I am trying to run a file called MFSTOOL from mfstools.sourceforge.net
It its a program for backing up tivo images
when i drop into a shell account and go to the dir of the program then type mfstool I get -bash: mfstool: command not found
now if I run it by typing ./mfstool
it will give me a list of options and switches for the program, but if i try to use the options and switches with ./mfstools it will just give me the switches and options again IE Typed as ./mfstool backup -6 -o /tivofiles/images/sddvr40/3510/tivo.bak /dev/hdc/
I know the program works as I can boot with a live cd mount my /dev/hda1 and store files to the images dir, i think i am missing something in a config file to let this program run.
Somehow I got libjpeg out of my system, and can't get it back working. I have installed jpeg-8b package, applications installed by it work, but not "system-wide" support for jpeg. Eg. I can use "cjpeg", but Eye of Gnome (image viewer) gives me "Unrecognized image file format" error.
Could you please point me to some right solution? Where does Debian look for this library?
I have /dev/sda with Squeeze and Win 7 on it, and /dev/sdb with Squeeze. I've managed to get Grub 2 to boot from /dev/sdb1, but only by disabling /dev/sda from being a boot option in the BIOS. When it is available to boot, and lower priority than /dev/sdb, grub does not recognize the UUIds of the disks. So, I've disabled it for now and can boot from /dev/sdb no problems. Trouble is I cannot get Win7 to boot. Grub prints:
error: no such device: f0903a3a903a081c error: invalid signature
When I boot into Squeeze and run 'blkid' I can see that:
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.
It then says an automatic fsck failed and a manual fsck must be performed, then the system restarted. I have done a manual fsck and it did nothing. I booted up the system with knoppix and did it, nothing.
I'm using sid and Gnome3 since two months. This morning I was operating an upgrade on my system with "aptitude update && aptitude safe-upgrade", and after rebooting gnome crash and tell me to restart my session.code...
Is there any others log files where gnome3 writes errors ?
/dev/sda 74.53gb. Here are two partitions sda1 243.13mib (33.92 used), flags 'boot', and sda2 74.29gb flags 'lvm'. Filesystem for sda1 is ext2, for sda2 'unknown' and it gives a warning "Unable to detect filesystem". At last shut down I also notices red text that said something about logical volumes and lvm.
I have proftpd set up on my linux home server. As I have a dynamic IP at home, I am using DynDns.org to provide a hostname for me. I have told proftpd to use this address as the MasqueradeAddress, to allow passive FTP connections through my NAT router.
However, whenever I boot my server, proftpd fails to start saying it cannot resolve this address. I assume this is due to the boot order, as something network or DNS related hasn't started up by then and it can't find the address. How should I deal with this problem? Can I get proftpd to do its checking for the address later on? Or can I change the startup order so that proftpd is started as the final item in the boot sequence?
I am travelling so would really appreciate a few tips that should hopefully get my pc running again. (I have internet access via a kiosk, and can burn a disk if necessary, but the smaller the download the better)I have a few ideas that with some help I should be able to fix the partition.1. Is there a simple way to use use grub, to mount all partitions read only and not to fsck them so I can logon in normal user and sudo and hopefully fix the parition?or 2. Download a small version of ubuntu or something that I can burn to CD (my machine cannot boot from usb) so that I can repair the machine.3. Download the ubuntu installer (alternative) and try and reinstall the necesary usr partition?
I have my drives set to run fsck on boot up. This is the default setting for Fedora but if there is a problem it prompts me to run fsck manually. Is there a way to have Fedora just run fsck and fix any errors it finds on boot up?w in Debian distros you can put FSCKFIX=yes in the /etc/default/rcS file to do this. But I can't find the equivalent on Fedora.