LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Password
Fedora This forum is for the discussion of the Fedora Project.

Notices

Reply
 
Search this Thread
Old 08-16-2006, 02:25 AM   #1
salil.mehta
LQ Newbie
 
Registered: Jun 2006
Posts: 15

Rep: Reputation: 0
Exclamation Getting Error "fsck.ext3 Unable to resolve 'LABEL=boot'" during Booting...


Hi,

PROBLEM:
On Booting FC4 just after successful initializaton of Hardware 'fsck' is launched which detects no errors but suddenly I see an ERROR being reflected after that...
"fsck.ext3 Unable to resolve 'LABEL=boot'"

DETAILS:

I have created a Dual Booting system between Windows XP and Fedora Core 4 on my Laptop (HP dv2000-SATA based HDD); such that NTLDR is launched first and Displays its OS Selection Menu (b/w Windows XP and FC4) and then on selecting FC4 GRUB Menu is launched.

Partitioning done is as follows-
sda1- Windows XP
sda6-/boot (ext3)~200 Mb
sda7-swap~2Gb
sda8-/ (ext3)~20Gb

Windows XP was installed first on "sda1" partition sector therefore NTLDR was already there on the MBR. I have installed GRUB on my Boot sector (sda6) rather than MBR.

Initialy, I had created a copy of my boot sector as "linux.bin" using command
"dd if=/dev/sda6 of=linux.bin bs=512 count=1"

Then copied linux.bin in my c: drive i.e sda1 and updated configuration file of NTLDR i.e boot.ini as follows-

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /noexecute=optin /fastdetect
c:\linux.bin="Fedora Core 4"

Below is my menu.lst/grub.conf file-

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,5)
# kernel /vmlinuz-version ro root=/dev/sda8
# initrd /initrd-version.img
#boot=/dev/sda6
default=1
timeout=5
splashimage=(hd0,5)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core 4 (2.6.11-1.1369_FC4)
root (hd0,5)
kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.11-1.1369_FC4.img
title Windows XP
rootnoverify (hd0,0)
chainloader +1


NOTE: I needed above style of booting so that my Windows XP is always in bootable condition and i could independently do programming of Linux Kernel
I am new to compilation of Linux Kernel and Kernel programming, this is to avoid messing up with Windows XP which is freaquently required for other for other purposes,


Please extend your helping hands...it is really urgent for me to solve this problem.


Thanks In Anticipation
Salil
 
Old 08-17-2006, 03:33 AM   #2
live_dont_exist
Member
 
Registered: Aug 2004
Location: India
Distribution: Redhat 9.0,FC3,FC5,FC10
Posts: 257

Rep: Reputation: 30
Hi Salil,
This means that there's some kind of filesystem corruption on your Linux partitions.If its LABEL=boot then I think it means your boot partition namely
sda6-/boot (ext3)~200 Mb
is corrupted or has some bad sectors. What you probably need to do is to pop in the Linux CD...go into Rescue mode and manually run an fsck on /boot which should clean up whatever problems there are.

Reboot into Linux and see what happens....If this doesnt work just put in your /etc/fstab file contents here....along with what other error messages you get.

Cheers
Arvind
 
Old 08-21-2006, 03:54 AM   #3
salil.mehta
LQ Newbie
 
Registered: Jun 2006
Posts: 15

Original Poster
Rep: Reputation: 0
Thanks Arvind,

It really came out to be a Trivial problem....I was able to solve it. Actually during installation I had given wrong LABEL=\boot to boot partition; it should have been LABEL=/boot.

This caused a mess up when "fsck" ran initially during startup; actually it was not able to recognize the boot partition by the LABEL name present within "fstab",since partition with LABEL=\boot never existed; what was existing LABEL=/boot.

I simply corrected LABEL name with "e2label" utility by going in "linux rescue" mode....and bing it worked....

Thanks for the help extended...
 
Old 08-21-2006, 09:39 AM   #4
live_dont_exist
Member
 
Registered: Aug 2004
Location: India
Distribution: Redhat 9.0,FC3,FC5,FC10
Posts: 257

Rep: Reputation: 30
Good stuff .. hmm e2label ... new one there .. and the learning continues...

Cheers
Arvind
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
unclean shutdown causes "Couldn't find matching filesystem: label=" error irnerdette Red Hat 3 06-02-2006 02:44 PM
FSCK.EXT3 "error allocating inode bitmap" arfon Linux - Software 6 05-15-2006 11:48 AM
fsck.ext3: Unable to resolve 'LABEL=/home' Azzath Linux - General 14 04-03-2005 05:45 AM
fsck.ext3 unable to resolve 'LABEL=/home yeehi Linux - General 2 10-20-2004 09:15 AM
dump + restore to backup linux ; "Couldn't find matching filesystem: LABEL=/" on boot markus1982 Linux - General 4 09-21-2002 02:16 PM


All times are GMT -5. The time now is 12:40 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration