LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 03-11-2014, 04:25 AM   #1
jmsb
LQ Newbie
 
Registered: Mar 2014
Distribution: Slackware 14.1 x86
Posts: 9

Rep: Reputation: Disabled
Unhappy Kernel compile problems after reboot


i tried to compile the kernel in slackware 14.1, and reboot the machine.
and there're something problems like these:
http://slackware.im/media/cache/page...56408749f.jpeg

http://slackware.im/media/cache/page...57c6dd554.jpeg

and this my /etc/fstab:

/dev/sda3 swap swap defaults 0 0
/dev/sda2 / ext4 defaults 1 1
/dev/sda1 /boot ext4 defaults 1 2
/dev/sda4 /home jfs defaults 1 2
#/dev/cdrom /mnt/cdrom auto noauto,owner,ro,comment=x-gvfs-show 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
debugfs /sys/kernel/debug debugfs defaults 0 0

how can i make it ?
thx..
 
Old 03-12-2014, 11:42 AM   #2
estabroo
Senior Member
 
Registered: Jun 2008
Distribution: debian, ubuntu, sidux
Posts: 1,117
Blog Entries: 2

Rep: Reputation: 113Reputation: 113
Well it kind of looks like that first screenshot is telling you that you need to recompile the kernel and add that particular config option, which I personally can't read, but starts with CONFIG_ in the line:

Filesytem with huge files cannot be mounted RDWR without CONFIG_...
 
Old 03-12-2014, 12:00 PM   #3
jpollard
Senior Member
 
Registered: Dec 2012
Location: Washington DC area
Distribution: Fedora, CentOS, Slackware
Posts: 4,599

Rep: Reputation: 1241Reputation: 1241Reputation: 1241Reputation: 1241Reputation: 1241Reputation: 1241Reputation: 1241Reputation: 1241Reputation: 1241
That first screenshot appears to be indicating a disk failure... It just "successfully" ran an fsck on the disk, but the attempt to remount failed...

And that would appear to be a disk failure.

Another possibility is a cable is a bit loose - disks are nearly always read/write unless there is a hardware switch to disable it - since it appears to be disabled, it is possible a cable has come loose.
 
Old 03-13-2014, 09:00 AM   #4
jmsb
LQ Newbie
 
Registered: Mar 2014
Distribution: Slackware 14.1 x86
Posts: 9

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by estabroo View Post
Well it kind of looks like that first screenshot is telling you that you need to recompile the kernel and add that particular config option, which I personally can't read, but starts with CONFIG_ in the line:

Filesytem with huge files cannot be mounted RDWR without CONFIG_...

thx,
the problem has been solved.

The error message "Filesystem with huge files cannot be mounted RDWR without CONFIG_LBDAF" says it all.

i msut chose this "Support for large (2TB+) block devices and files" when i "make menuconfig" .
because:

This option is required to support the full capacity of large
(2TB+) block devices, including RAID, disk, Network Block
Device, Logical Volume Manager (LVM) and loopback.

This option also enables support for single files larger than
2TB.
The ext4 filesystem requires that this feature be enabled in
order to support filesystems that have the huge_file feature
enabled. Otherwise, it will refuse to mount in the read-write
mode any filesystems that use the huge_file feature, which is
enabled by default by mke2fs.ext4. The GFS2 filesystem also requires this feature....
 
Old 03-13-2014, 09:02 AM   #5
jmsb
LQ Newbie
 
Registered: Mar 2014
Distribution: Slackware 14.1 x86
Posts: 9

Original Poster
Rep: Reputation: Disabled
Wink

Quote:
Originally Posted by jpollard View Post
That first screenshot appears to be indicating a disk failure... It just "successfully" ran an fsck on the disk, but the attempt to remount failed...

And that would appear to be a disk failure.

Another possibility is a cable is a bit loose - disks are nearly always read/write unless there is a hardware switch to disable it - since it appears to be disabled, it is possible a cable has come loose.

problem has been solved.
look at #4
 
  


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
Kernel compile problems draggin Linux - Software 4 02-11-2006 04:41 PM
problems after kernel compile rangalo Slackware 9 01-27-2006 11:06 AM
Problems with kernel compile BNI Debian 3 05-31-2005 04:50 AM
reboot error after new kernel compile tiluu Linux - Newbie 14 06-23-2004 01:29 PM
Kernel Problems. Howto Compile a new kernel from 4.2 with backwards compatibility ? ShoCkwave Linux - General 2 06-19-2004 07:02 AM


All times are GMT -5. The time now is 08:26 PM.

Main Menu
Advertisement
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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration