Slack fstab -- fat32 folder contents disappearing after hardware install

gbonvehi · 02-04-2006, 02:11 AM

Maybe you accidentally removed kernel-modules package. You should find vfat and ntfs modules in /lib/modules/2.6.12.4/kernel/fs/

Drone4four · 02-05-2006, 06:57 PM

Also I noticed when booting my Slackware distro, I saw these three commands:

Code:

unkonwn filesystem type "vfat"
unkonwn filesystem type "ntfs"
unkonwn filesystem type "vfat"

MacIver also from #Slackman suggests I try:

Code:

bash-3.00$ grep vfat /proc/filesystems
bash-3.00$ grep ntfs /proc/filesystems
bash-3.00$

And that's what gbonvehi was asking in essence...MacIver suggested I try this one too:

Code:

bash-3.00$ zgrep -i vfat /proc/config.gz
CONFIG_VFAT_FS=m

So without changing kernels, my system has stopped recognizing vfat and ntfs even though i've accessed those drives last week! MacIver has narrowed down the problem to the /fs/ dir missing from my kernel modules dir:

Code:

 bash-3.00$ cd /lib/modules/2.6.11.10/kernel/
bash-3.00$ ls
drivers  sound

Fron that, MacIver says my problem is that the file system module is no absent for some reason. Regardless, my options now are to either recompile a new kernel from source, OR just configure and make the old fs module from the existing kernel i'm using. The command for that, MacIver says is:

Code:

zcat /proc/config.gz > .config
make oldconfig && make modules &&  make modules_install

Before I try that, I'm going to need the 2.6.11 kernel. Here is the link for my 2.6.11 kernel [HTML]ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-2.6.11.tar.bz2[/HTML]

Drone4four · 02-05-2006, 08:34 PM

The dirs are still not showing vfat/ntfs even though my /kernel/fs exists in modules:

Code:

bash-3.00$ cd /lib/modules/
bash-3.00$ ls
bash-3.00$ cd 2.6.11
2.6.11/    2.6.11.10/
bash-3.00$ cd 2.6.11
bash-3.00$ ls
build  kernel  source
bash-3.00$ cd ..
bash-3.00$ cd 2.6.11.10/
bash-3.00$ ls
kernel          modules.dep          modules.isapnpmap  modules.usbmap
modules.alias   modules.ieee1394map  modules.pcimap
modules.ccwmap  modules.inputmap     modules.symbols
bash-3.00$ cd kernel/
bash-3.00$ ls
drivers  sound
bash-3.00$ cd ..
bash-3.00$ cd ..
bash-3.00$ cd 2.6.11
2.6.11/    2.6.11.10/
bash-3.00$ cd 2.6.11
bash-3.00$ ls
build  kernel  source
bash-3.00$ cd kernel/
bash-3.00$ ls
arch  crypto  drivers  fs  lib  net  sound
bash-3.00$ cd fs/
bash-3.00$ ls
adfs    autofs4  cifs    efs       freevxfs  hpfs   msdos  nfsd  qnx4   ufs
affs    befs     coda    exportfs  hfs       jfs    ncpfs  nls   smbfs  vfat
autofs  bfs      cramfs  fat       hfsplus   lockd  nfs    ntfs  sysv   xfs
bash-3.00$ cd /winXP-C/
bash-3.00$ ls
bash-3.00$ cd /winXP
winXP-C/      winXP120Dump/ winXPbacks/
bash-3.00$ cd /winXP
winXP-C/      winXP120Dump/ winXPbacks/
bash-3.00$ cd /winXPbacks/
bash-3.00$ ls
bash-3.00$ cd /winXP-C/
bash-3.00$ ls

gbonvehi · 02-05-2006, 09:55 PM

2.6.11 is not the same as 2.6.11.10, you got the wrong kernel from the ftp, you need the one you're loading and make the modules for THAT version (2.6.11.10): ftp://ftp.kernel.org/pub/linux/kerne....11.10.tar.bz2

Drone4four · 02-05-2006, 11:15 PM

I suppose I could recompile the 2.6.11.10 kernel, or I could just compile the latest stable kernel @ 2.6.14.7. I think what I'm going to end up doing is nuking my partition and reinstalling Slamd64 from CD. I'll learn to compile a kernel later, when I have more patience. I just want to listen to my music and edit school documents on these vfat and ntfs drives!

=D

gbonvehi · 02-06-2006, 02:44 AM

Heh, do as you feel better. I recommend to try what was suggested, you did it fine, except for choosing the wrong kernel number, downloading the correct one and repeating the steps should led you to build the correct modules

By the way, you've to run zcat /proc/config.gz > .config in the kernel source directory that was created when uncompressing the file you downloaded.

Drone4four · 02-14-2006, 10:06 PM

Quote:

Originally Posted by gbonvehi

Heh, do as you feel better. I recommend to try what was suggested, you did it fine, except for choosing the wrong kernel number, downloading the correct one and repeating the steps should led you to build the correct modules

By the way, you've to run zcat /proc/config.gz > .config in the kernel source directory that was created when uncompressing the file you downloaded.

From the link you gave me I downloaded and untared the correct Linux Kernel. I inputed the same commands from earlier. It took a real long time to compile. I rebooted Slamd64. I noticed in the commands scrolling my vfat and ntfs drivers got mounted. That was the first good sign. And then X11 wouldn't load. I did a CTRL + F3 and cd'ed into the dir with my old NVIDIA drivers. I exectued the .run file from nVidia. I exited root and then tried startx. Then I could check my vfat partitions and they are all readable. Thanks gbonvehi for yopur pateince. Slackers on irc also deserve a big hollar!

THANKS

=D

edit: sp + grammar

Kahless · 02-15-2006, 01:20 AM

Before you added the drive, did it work?

Did it definatly stop working when you added the drive, or not sure?

The drive isnt being mounted Possibly because you dont have it set up to mount automatically, or possibly because you changed the jumper on the hard drive, or moved it to a different contoller, which would make its name in the system change.

Ill try to explain this here.

X is the partition number on the drive

If its the primary master, it is hdaX
If its the primary slave, its hdbX
if its the secondary master, its hdcX
If its the secondary slave, its hddX

If you changed the jumper or moved the drive from one cable to another, the third letter in the above designations would have changed. use my guide above to see what it would be now (you can tell if its primary or secondary, and master or slave, in the bios) to correct your fstab.

If the above is all correct, mabey you just need to mount it manually, or find the script to mount it automatically. google and the forums can help you if thats all you need, or if you cant figure it out post back and ill research further (but i might take a week, so look yourself first)