Linux - NewbieThis 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
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.
Hi there,
I have 2 hard drives: 160 Gb HDD with Suse 10.2 running and another 160 Gb HDD with Windows XP running. I have all my mp3s on my XP drive so naturally I want to access those in Suse. Problem was that while installing Suse I unpluged my XP drive so its not been detected by Suse now. Both drives are in the same machine. The XP drive is fat 32 (i think- is there a way to check this?)
Basically I want to be able to access my XP drive- How would I detect and mount the XP drive in Suse 10.2? Any help would help, or even a point in the right direction. Thanks.
hda = master on primary controller
hdb = slave on primary controller
hdc = master on secondary controller
hdd = slave on secondary controller
You need to create a mount point for it, like /windows in the filesystem:
mkdir /windows
as root.
Then you need to place an entry in your /etc/fstab file that connects the device to the mount point:
/dev/hdb /windows fat32 defaults,users,rw 1 1
You'll have to verify what I wrote above. Particularly the the device in the first field and the parameters in the third field. I'm not sure using "defaults" is the right thing to do for a fat32 drive, or even "users".
Then try mounting it:
mount /windows
If the entry in fstab is correct, you should be able to see /windows in your filesystem. But check the parameters in man fstab first.
Depending on how your drive is formatted, you might not want /dev/hdb, since this is the raw device for the entire drive including boot sector and partition table.
/dev/hdb1 = first partition on /dev/hdb
/dev/hdb2 = second partition on /dev/hdb
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 262 2104483+ 82 Linux swap / Solaris
/dev/sda2 * 263 2873 20972857+ 83 Linux
/dev/sda3 2874 19457 133210980 83 Linux
Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 9781 78565851 c W95 FAT32 (LBA)
/dev/sdb2 9782 17512 62099257+ f W95 Ext'd (LBA)
/dev/sdb3 17513 19457 15623212+ 77 Unknown
/dev/sdb5 9782 17512 62099226 b W95 FAT32
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
Ok all the partitions on the second sata or scsi drive is fat32. You can use the filesystem type vfat when mounting. Post contents of your current /etc/fstab file for options used by the other mounts. But from the above post the line in fstab for say /dev/sda5 would like this. Note your options like user may be user or users. Minor difference distro to distro.
You can read the manpages on fstab and mount to learn about the options I listed in more detail. The auto will automatically mount the partition at boot. Umask allows all users to read and write to the partition, just not root only. Again users maybe user just depends on what the other lines in your fstab file is like. Now for the above to work you need to have a directory created in /mnt called sdb5. You can name it to what every you wish call it drivee if you it is the E drive in windows. They just need to match.
(I changed the fat32 to vfat because it asked me if that is waht i ment during mounting)
Then I created the /sdb5 dir and typed the following as root:
Code:
# mount sdb5
mount: wrong fs type, bad option, bad superblock on /dev/sdb5,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Okay I just tried to mount after editing the fstab file. Line now reads:
Code:
/dev/sdb5 /sdb5 vfat defaults,user,rw 0 0
Will this make a difference? Is this okay.
I can now see Drive D (for windows - I had 2 partitions).
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
Check out this post on that. http://learn.clemsonlinux.org/wiki/Fstab
Or using the man command to learn about many linux commands.
ie:
man fstab
man mount
man ls
man fdisk
In your post you have unmask, it is mispelled and should be umask.
Use of default should automount on boot.
Using mount sdb5 I would think it would have produced a different error. One would use
mount /sdb5
or
mount /dev/sdb5
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.