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:
I have a problem partitioning an Hard Disk Drive on a server, and I hope someone can help me with this. Here is the system configuration: Operating System Linux localhost.localdomain 126.96.36.199-64.fc11.x86_64 #1 SMP Fri Sep 25 04:43:32 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
Hardware: RAID bus controller: Hewlett-Packard Company Smart Array G6 controllers (rev 01)
The system mounts one hard disk (120 Gb) with the OS, and four 1.5Tb Hard Disks mounted on RAID 10 for a total of ~3 Tb I need to create several partitions on this RAID drive, but I have some trouble doing it. I need a total of 10 partitions of different sizes:
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?
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 $ 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: /dev/sdc1 /dev/sdc3 /dev/sdc2
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 code....
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.
I Tarred and GZipped most of the data on one 1Tb partition and stuck the archives on a second 1Tb partition on a separate disk. I then proceeded to format the first partition with NTFS (from Linux.) The only problem is that I completely forgot that I had a CD drive and formatted sdc1 instead of sdd1! I began doing a full NTFS format and after a minute or two I cancelled it and decided to do a quick format. I then realized my mistake. I managed to find a copy of the superblock and began trying to recover the disk. fsck -t ext3 recognized the partition as NTFS but I luckily didn't have fsck.ntfs installed so it didn't touch it. I managed to get it working with fsck.ext3 (with -b,-B and -y) fsck.ext3 didn't mind that it was an NTFS partition.
Roughly how long will this take? It's running from Knoppix within a virtual machine to a USB hard drive which is 100% full. Days? Being that for a few minutes I attempted a full format am I going to end up with a bunch of corrupted archives? If I do end up with file corruption can anyone recommend a way of recovering the data / sorting it out? Is it likely to be just a few old files that are corrupt (It's my understanding that filesystems like to keep files in the same area on the disk to minimize the amount of head travel.) This might just be wishful thinking but as the filesystem fills up will ext3 put the newer files towards the end of the disk? If so then I'm hoping that a full NTFS format starts at the beginning of the disk.
I've done a search thru the forums on a recent headache but couldn't find anything. now we all know that windows installations knackers the grub boot-up, and it becomes modus-operandi to repair the boot loader, with a live distro. however, in my current dual boot system (vista.sp2/fedora12), i've done a clean install of windows7 over the current windows ntfs partition. as standard, the boot menu would vanish. but when i put in the live-linux cd, gparted now shows the fedora partition (sda6) as LVM2. i'm somewhat of a neophyte with linux, but fedora12, suse11.2 and ubuntu don't seem to yet support this file system.
since i don't have critical data on the fedora partition yet, i usually wouldn't mind reformating this part', but the wireless chipset on my laptop cost a fortune on cups of coffee and beer to install, and in addition i used the fedora12 FEL spin and want to keep the installation intact. is there anyway to make the LVM2 indentifier back to ext3 or 4 and repair grub form there (without loosing the current partition kernal etc.)?
I need to boot in WXP just because the guys at the company don't want to update for Linux drivers in the TS so I can't connect from home unless I do it in Windows XP. But today WXP refuses to boot, when the progress bar appears, the system boots automatically. The WXP CD doesn't help, the repair console doesn't let me run chkdsk or anything (dir C: gives an error about listing addresses or something like that). Is there any way to use fsck or anything in Linux to repair the WXP NTFS partition?
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.
I was working on my RHEL 5.2 workstation yesterday when the OS became flakey. first I noticed that some software that I had running was outputting and error that it was unable to write to log file because permission was denied - I've never seen this output before- it would have been writing to my home dir running under my user name. From an open terminal, i did "ls -al" and saw that many of the permissions the files in my home dir were listed as "????????" some were still "rwxrwxrwx", as well, many files were highlighted in the colors set for links and root privileges.
I tried to start a new terminal, and it failed. then Gnome crashed. When I reset the Machine, I got through grub, and into the startup, and after finding the Volumes, the startup failed with a Kernel panic:
giving several errors- like:
I dont have much experiencie with this stuff, but it looks obvious that somethig like the MBR or wherever the partion information is stored might have been corrupted.
What I dont understand is why I can get into GRUB (its a dual boot Windows Vista, RHEL machine). I'm guessing that this means its not a mechanical problem, because I can get RHEL to begin to boot which i think is failing somewhere around the /etc/rc.d/re.sysinit script, and also can get Vista to bring up the inital windows screen and a mouse pointer on spanning both of my screens which i think means that it must have at least loaded my ati drivers for my dual head radeon 4850. windows hangs there however.
I've tried the RHEL 5.2 rescue disc, and it doesn't recognize any Linux partitions.
I ran the system diagnostics out of the dell bios and it came back with a failed HDD : Error code 0142, but from digging around a bit I've found that this is a very broad diagnosis.
My concern over it being a mechanical problem is that I'm not sure that I want to try to run any further diagnostics, or any of the disk utility programs that i've seen listed here on linuxquestions, as it might damage it further, and there is some data that i would really like to get off this disk.
I can not use nfs from F10 client to F12 server. nfs mount on F10 to F12 times out anf nfs4 mount gives "mount.nfs4: mounting localhost:/home failed, reason given by server: No such file or directory" I have tried to close firewall and set selinux to permissive mode on both client and server with same result. Samba works fine. On server [root@flokipal ~]# mount -t nfs4 localhost:/home /media/tonlist mount.nfs4: mounting localhost:/home failed, reason given by server: No such file or directory
[root@flokipal ~]# mount -t nfs localhost:/home /media/tonlist [root@flokipal ~]#
I have a centOS 5 box with 3ware 8 port raid cards.I run fsck.ext3 -y /dev/sdb1 and it shows as clean.But after writing to the FS for about 2 minutes, it becomes read-only.When I umont -l /data, and run the fsck I get that another program is using the system an I should wait.If I reboot the server , the array comes back as clean.
I am attempting to run a fsck on a number of large ext3 filesystems. I am doing this proactively because I want to minimize reboot time and the filesystems are past the interval time of 6 months. When I run the command " fsck -f -y device" I get the following error on all of the filesystems-
fsck 1.39 (29-May-2006) e2fsck 1.39 (29-May-2006) fsck.ext3: Device or resource busy while trying to open /dev/mapper/mpath0p1
I am hosting a few customer servers now, all of which are virtual machines running on a CENTOS 5.x host. Each Centos host has a couple of extra drives. When I formatted them ext3 they automatically had a schedule of a full forced fsck after 6 months. Do I really need to do that check regularly? It results in a fairly large outage since my disks are each 1TB and there are up to three extra drives on each server. I try to reboot these servers every 6 months but this part adds a large amount of time to a routine reboot.
I have dual boot system..i.e, windows XP and ubuntu 9.10(insatlled side by side). when i try to boot ubuntu, Im gettin sh:grub > prompt
I am getting something like this.. root mount file system failed.. ext2 ext3 ext4 ....... kernel panic message and hanged at kenelthreadhelpper+ what can i do.. I cant reinstall ubuntu again.. Because I have installed nany application there..
I have setup a home based web server to host a photo blog for myself and my friends. I will be running wordpress and possibly a phpbb3 forum. I'd like to open this to discuss server administration, server setup, and server maintenance. However, I have a pretty good start on all of those but serving a domain name to my static ip. Here my static ip is 188.8.131.52. I registered a domain through [URL]... It appears that I have the domain working to forward to my ip. However, I am still getting this output file from apache.
I have tested the domain name across a few different computers on different ips. It works appropriately. I just want to make sure I have it set correctly on the (apache) server side of things. Then I can get more into Zone Editing etc.
I started up my computer and this is what it said: Mount of file system failed.A maintenance shell will now be started.CONTROL-D will terminate this shell and re-try.root@Gifted:~#The only part I recognize is the name of my computer; Gifted
I have a serious problem in booting centos 5.4 x86 as shown in the attached picture.I tried to backup before using fsck command, but I could not make a backup of damaged lvm on hard drive.First I made a rescue centos at virtualbox, and installed centos 5.4 x86 on virtual hard disk.And I attatched damaged hard drive. S I can see this damaged hard drive's lvm as attached picture.Please let me know how to backup my files and to use "fsck.ext3 --rebuild-tree using livecd".
just start Ubuntu 9.04 said: File system chek failed a long is beging saved /var/long/fsck/checkfs if that location is writable Please repair the file systmen manually A maintenance shell will now be started Ctr+ D terminate this shell and resume system boot. Give root password for maintenance or type Control +D to continue. I did Ctr+D , and after login said , that can not find /home. I starte with the live cd:
I'm currently running 11.3 and decided I'd try upgrading to 11.4 following the instructions here: SDB:System upgrade - openSUSEUnfortunately, my attempts are defeated at the point of trying to refresh the new repos; I get the following message (for the oss repo, in this case):
With 11.4 replaced by 11.3 in the repo url, it refreshes just fine. The only repository that works when I change 11.3 to 11.4 is the Packman repo. I'm not really sure why the connection fails for 11.4 but not 11.3!
Further info: I have an old router with no IPv6 support, but have IPv6 disabled system-wide. I can enter the url for the repositories into firefox and they come up just fine - it's only with zypper/YaST that I get the above error message.I also tried upgrading using the network CD but ran into the same sort of problem. In this case it may be because the CD installer doesn't disable IPv6. (I didn't want to download the DVD at my connection speed, and the KDE live CD is not listed as suitable for upgrade).
I'm trying to partition/format a new external hard disk for backup and have run into a snag that now prevents my computer from booting. In the description below of what happened please bear with me as I do my best to remember the commands and screen output (which for obvious reasons I don't have in front of me).As root.The disk was subsequently writable. However, I then realized that the default start and end cylinders had resulted in a very small partition apparently occupying some free cyclinders in the beginning of the disk.
So next I ran fdisk again, deleting the sdc4 I had just created and creating a new one instead, this time using the cylinders at the end of the disk. When I exited fdisk I got a message something like that the new tables can only be read upon a subsequent reboot. I ran mkfs again, but not e2label. Indeed using /sbin/fdisk -l, sdc4 still had the small size as defined initially. So I rebooted.
Now when it comes up I get something like "checking filesystems. fchk.ext3: can't resolve 'LABEL=/media/LaCie2TB1'" and am prompted to login as root to correct. I tried to simply delete sdc4 again but that didn't help. I also tried to edit /etc/fstab (using vi, which I don't know at all) but it kept telling me that this is a read only file, even though permissions are rw for root.Can anyone out there help me so that (1) I can boot into my computer, and (2) I can correctly partition and format the hard drive??