SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It's something in kernel compile options that I keep missing. My NTFS filesystem on sda1 works perfectly with the default 2.4.33.3 kernel. At first I recompiled to 2.6.16.43. After that I couldn't mount ntfs anymore.
Code:
sda1 is not a valid block device
(if i remember correctly)
NTFS support is compiled into the kernel. Today I tried 2.6.20.1, still no gain, same problem. I figure it has something to do with sata drivers. The harddrive itself is Seagate Barracuda 7200.10 320GB (Slack is on the other drive). I hope you have some hints, what options I should look out for.
I've tried mounting both sda1 and sda (as someone suggested somewhere) yet nothing. /proc/filesystems shows that ntfs is available.
Also with the new kernel (I compiled some new SATA options in there that I haven't used before and might cause the following) during boot up when it checks for SCSI it gets a "NEW:" prompt. I can enter whatever there without anything happening, then after about a minute it continues booting. What might that be?
please show your fstab entry or your mount command.
mine:
Code:
# windows stuff
/dev/hda2 /mnt/windows ntfs ro 1 0
double check your ntfs support options, also that the correct SATA modules are compiled in or loaded before trying to mount the ntfs partition.
are there any linux partitions on the same HD? Is your linux HD the same model?
if so can you mount them?
a brute force approach: recompile your kernel with 'auto module loading' enabled. then select every thing SATA that is even close to what you have as modules (except where you are currently booting to). reboot and try and mount the drive. then do lsmod and see what got loaded.
please show your fstab entry or your mount command.
mine:
Code:
# windows stuff
/dev/hda2 /mnt/windows ntfs ro 1 0
I'm currently in windows, but as I remember it, it's:
Code:
/dev/sda1 /mnt/win ntfs ro,umask=000 1 0
I'm only not sure in the last two numbers, but thay shouldn't make a difference anyway. Also 2.4.33.3 loads perfectly with the same fstab.
I mount with
Code:
mount -t ntfs /dev/sda1 /mnt/win
Quote:
Originally Posted by bioe007
double check your ntfs support options, also that the correct SATA modules are compiled in or loaded before trying to mount the ntfs partition.
NTFS support is on, SATA modules is what I'm not sure of and what I suspect. Kmod is also on so if the necesarry stuff was in modules, it should still work, but it isn't, everything exept alsa is compiled in.
Quote:
Originally Posted by bioe007
are there any linux partitions on the same HD? Is your linux HD the same model?
if so can you mount them?
Linux is fully on hda and it's partitions, windows is on sda1, can mount in 2.4.33.3, can boot, just can't mount in 2.6. Linux hd is not the same model. It's ATA while sda is SATA.
Quote:
Originally Posted by bioe007
a brute force approach: recompile your kernel with 'auto module loading' enabled. then select every thing SATA that is even close to what you have as modules (except where you are currently booting to). reboot and try and mount the drive. then do lsmod and see what got loaded.
Yup, that's pretty much what I intended on doing. Unfortunately I'm gonna have to call it a night but if I don't get any other suggestions, I'll try it. Thanks for your reply.
I've compiled half of the kernel in modules, still nothing. I think I'm going to put it to a rest for now, I can access my stuff with the 2.4 kernel and pretty soon I'm going to get rid of XP anyway. Just hope that there won't be any problems when I'm finally going to install on that same sda disk. If you have any ideas, let me know, if not, let it be.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.