LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 11-05-2010, 11:23 PM   #1
yangzhichina
LQ Newbie
 
Registered: Nov 2010
Location: China P.R.
Distribution: Slackware 13.37
Posts: 13

Rep: Reputation: 0
Is it a bug of klibc? If so, how can I update it?


Hi Guys.

I am new to Slackware. Last night, I finished my installation of Slackware, but there is a issue when system's starting-up.

I have 3 partitions for linux. (Other 3 ones for Windows)

/dev/sda8 /boot ext2
/dev/sda9 / ext4
/dev/sda10 /home ext4

These information above is listed in the /etc/fstab, actually they are true, but I get a error message during starting-up of Slackware. I am told as fellow:
"ext3-fs (/dev/sda9): error: Couldn't mount because of unsupported optional feature (240)"
"ext2-fs (/dev/sda9): error: Couldn't mount because of unsupported optional feature (240)"
"ext4-fs (/dev/sda9): Mounted filesystem with ordered data mode."

It is wired. My /dev/sda9 is truly ext4, I formatted it as ext4 by myself on the installation of Slackware. Why the system want to mount it as ext3 firstly, then ext2, eventually ext4?

After a moment on Google, I guess it is a bug of klibc because of checking "https://bugzilla.kernel.org/show_bug.cgi?id=12354". But I am not sure about it.

Could anyone help me fix it? It will be appreciated.

Jeffrey.
 
Old 11-05-2010, 11:45 PM   #2
yangzhichina
LQ Newbie
 
Registered: Nov 2010
Location: China P.R.
Distribution: Slackware 13.37
Posts: 13

Original Poster
Rep: Reputation: 0
Someone in China have fixed it using GRUB loader, but I am using LILO, the default loader on Slackware. What can I do?

The following is his solution:

menuentry "Gentoo GNU/Linux, with Linux 2.6.35.7" --class gentoo --class gnu-linux --class gnu --class os {
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set eaffe5af-76f1-4beb-abd3-5e7994c8d606
echo Loading Linux 2.6.35.7 ...
linux /vmlinuz-2.6.35.7 root=/dev/sda1 ro quiet rootfstype=ext4
}

Please pay your attention on this text of Bold Font.

Could I fix this issue using rootfstype=ext4 on LILO?
 
Old 11-06-2010, 01:28 AM   #3
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,353

Rep: Reputation: 378Reputation: 378Reputation: 378Reputation: 378
try adding this line in /etc/lilo.conf
append "rootfstype=ext4"

and re-run lilo
/sbin/lilo -v
 
Old 11-06-2010, 11:24 AM   #4
yangzhichina
LQ Newbie
 
Registered: Nov 2010
Location: China P.R.
Distribution: Slackware 13.37
Posts: 13

Original Poster
Rep: Reputation: 0
Guys, there is a good news about this question. I've got reply from Patrick, the creator of Slackware. (Of course, I sent a email to him.)

The followings are his reply:

Quote:
On 11/05/2010 11:23 PM, Jeffrey Young wrote:

Hi Patrick

I am new to Slackware. Last night, I finished my installation of Slackware,
but there is a issue when system's starting-up.

I have 3 partitions for linux. (Other 3 ones for Windows)

/dev/sda8 /boot ext2
/dev/sda9 / ext4
/dev/sda10 /home ext4

These information above is listed in the /etc/fstab, actually they are true,
but I get a error message during starting-up of Slackware. I am told as
fellow:
"ext3-fs (/dev/sda9): error: Couldn't mount because of unsupported optional
feature (240)"
"ext2-fs (/dev/sda9): error: Couldn't mount because of unsupported optional
feature (240)"
"ext4-fs (/dev/sda9): Mounted filesystem with ordered data mode."

It is wired. My /dev/sda9 is truly ext4, I formatted it as ext4 by myself on
the installation of Slackware. Why the system want to mount it as ext3
firstly, then ext2, eventually ext4?


I will guess that you are still booting with the "huge" kernel rather than with an initrd and a generic kernel. The kernel has all of those filesystems built into it, and doesn't really know what filesystem type /dev/sda9 is until it starts to examine it. So you see 2 failed mount attempts, and then it works. That's just the order the kernel happens to try.

Anyway, if you switch to an initrd/generic boot, it won't emit those messages. It's not hurting anything, though.


After a moment on Google, I guess it is a bug of klibc because of checking "
https://bugzilla.kernel.org/show_bug.cgi?id=12354". But I am not sure about
it.



Nope, we don't use klibc in Slackware.

Take care,

Pat
 
Old 11-07-2010, 12:12 AM   #5
yangzhichina
LQ Newbie
 
Registered: Nov 2010
Location: China P.R.
Distribution: Slackware 13.37
Posts: 13

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by willysr View Post
try adding this line in /etc/lilo.conf
append "rootfstype=ext4"

and re-run lilo
/sbin/lilo -v
Please forget the "rootfstype=ext4". These error messages don't matter. Nothing will be hurting there.

Last edited by yangzhichina; 11-07-2010 at 12:15 AM. Reason: A typo.
 
Old 11-07-2010, 12:18 AM   #6
yangzhichina
LQ Newbie
 
Registered: Nov 2010
Location: China P.R.
Distribution: Slackware 13.37
Posts: 13

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by yangzhichina View Post
Someone in China have fixed it using GRUB loader, but I am using LILO, the default loader on Slackware. What can I do?

The following is his solution:

menuentry "Gentoo GNU/Linux, with Linux 2.6.35.7" --class gentoo --class gnu-linux --class gnu --class os {
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set eaffe5af-76f1-4beb-abd3-5e7994c8d606
echo Loading Linux 2.6.35.7 ...
linux /vmlinuz-2.6.35.7 root=/dev/sda1 ro quiet rootfstype=ext4
}

Please pay your attention on this text of Bold Font.

Could I fix this issue using rootfstype=ext4 on LILO?
Forget it. It's not a right way. Please refer to Patrick's reply.
 
  


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
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Non bug fix update to 13.1 samac Slackware 13 06-30-2010 04:05 PM
/usr/lib klibc question Daedra Slackware 5 01-06-2010 03:25 AM
Bug buddy update - dependency problems. Micro420 Suse/Novell 6 11-17-2007 11:10 AM
how to do the Patch update and bug fix in AS 3.0? sathyguy Linux - Enterprise 3 08-31-2006 06:44 AM
Bug fix update for 10.0 akihandyman Mandriva 3 07-14-2004 04:13 PM


All times are GMT -5. The time now is 01:42 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