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..

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_...

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.

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....

problem has been solved.
look at #4