Can't see Windows Partitions

[Topha]

With Suse 9.1 and the Reiser file system, Linux can't see my windows drives.

It could before, but I had Suse installed on the same disk then.

I'm guessing the problem is that it only mounts the hard drive linux is on, but I dont know how I can make it mount the other disk. Can anyone tell me how to do that?

[KeiFront]

If you want to automount your windows partitions when Suse starts ups you will have to add some additional lines to the /etc/fstab file.

First create a directory called /mnt/windows.
Assuming the Windows partition is on hda1, add the following line to /etc/fstab:
/dev/hda1 /mnt/windows ntfs ro, defaults, umask=0222 0 0 (this would mount a ntfs partition and it would mount it as read only)

Check the mount manual (man mount) for the appropiate mount options. And probably Suse also has this documented somewhere on their website.

[VJ]

If it is a SCSI harddisk, chances are the driver isn't automatically loaded (some are automatically loaded, like the Adaptec 7xxx driver, but others aren't, like the Adaptec 79xx drivers), even though the required files should be present in the system.
insmod 79xx (not 100% about this driver name, but tabcompletion should sort it out) installs it, after which you can mount it as Keifront mentioned.


Jörg

[Wombat]

If it is a SCSI harddisk, chances are the driver isn't automatically loaded (some are automatically loaded, like the Adaptec 7xxx driver, but others aren't, like the Adaptec 79xx drivers), even though the required files should be present in the system.
insmod 79xx (not 100% about this driver name, but tabcompletion should sort it out) installs it, after which you can mount it as Keifront mentioned.


Jörg

The adaptec drivers are aic. A modprobe of aic79xx should also load the aic7xxx driver for you.

[Topha]

OK, have been gone for a few days. Thanks for the replies, I'll try them later this day. Dont have scsi though

[VJ]

The adaptec drivers are aic. A modprobe of aic79xx should also load the aic7xxx driver for you.

Right on the drivernames!

Perhaps, but not the other way around:
On my system, at bootup, Knoppix loads the aic7xxx (for my 2940UW) automatically but it doesn't load the aic79xx (for my onboard U320), even though all the required files are present in the system (if I just enter modprobe aic79xx it loads the driver).

And contrary to what one might derive from the drivernames, the aic7xxx driver does not work when the device needs an aic79xx driver.



Jörg

[Wombat]

Right on the drivernames!

Perhaps, but not the other way around:
On my system, at bootup, Knoppix loads the aic7xxx (for my 2940UW) automatically but it doesn't load the aic79xx (for my onboard U320), even though all the required files are present in the system (if I just enter modprobe aic79xx it loads the driver).

And contrary to what one might derive from the drivernames, the aic7xxx driver does not work when the device needs an aic79xx driver.



Jörg

The way I understand those modules is that the aic79xx driver depends upon the 7xxx driver. So if you didn't have either loaded, a modprobe of 79xx would cause both modules to be loaded.

That's the behavior I see with my FC cards. I have a QLogic 2200 in one of the PCs at work, and it loads qla22xx and qla2xxx.