Problem automounting FAT32 Partition

pengu · 10-07-2007, 10:18 AM

Using openSuse 10.3

When using the Yast Partitioner to assign a mount point to an existing partition (without formating), it gives this error:

Quote:

Error:
It is not allowed to assign a mount point to a device with nonexistent or unknown file system.

The Partition type is "Win95 FAT32"

I could do this fine on 10.2

Also, after starting up i can mount the partition fine from the command line, but i have to do this again every time i reboot

EDIT:
It just occurred to me that I could just add it to fstab.. but it seems the fstab is different for some reason

Code:

/dev/disk/by-id/scsi-SATA_TOSHIBA_MK1032G_665G0518T-part3 /                    ext3       acl,user_xattr        1 1
/dev/disk/by-id/scsi-SATA_TOSHIBA_MK1032G_665G0518T-part5 swap                 swap       defaults              0 0
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0

Disillusionist · 10-07-2007, 10:40 AM

Try the following link:

http://en.opensuse.org/Access_Your_Windows_Files

pengu · 10-07-2007, 10:51 AM

hm doesent explain the yast problem but im attempting to use fstab

is "/dev/disk/by-id/scsi-SATA_TOSHIBA_MK1032G_665G0518T-part5" in the suse fstab any different to "hda5"?

Disillusionist · 10-07-2007, 11:34 AM

should work the same.

Format for fstab is usually (and I believe opensuse is no different)
{device} {mountpoint} {filesystem type} {mount options} {determine if dump should be used} {determine fsck order}

pengu · 10-07-2007, 12:44 PM

well i tried adding

Code:

/dev/hda2 /home/jack/Personal vfat utf8,codepage=850,dmask=000,fmask=111,shortname=Personal 0 0

and that didnt work..

now im trying

Code:

/dev/disk/by-id/scsi-SATA_TOSHIBA_MK1032G_665G0518T-part2 /home/jack/Personal vfat utf8,codepage=850,dmask=000,fmask=111,shortname=Personal 0 0

pengu · 10-07-2007, 12:55 PM

ok, that didnt work either, im out of ideas...

Disillusionist · 10-07-2007, 03:49 PM

Quote:

Originally Posted by pengu

Using openSuse 10.3
Also, after starting up i can mount the partition fine from the command line, but i have to do this again every time i reboot

You could always create a startup script to mount the filesystem at boot time.

Other than that I'm afraid I'm also out of suggestions.

saikee · 10-07-2007, 04:28 PM

I am really puzzled by the statement that without formatting you could mount a fat32 partition in Suse 10.2 but not 10.3.

I would guess your memory may be faulty.

Suse has already complain to you that

Quote:

Error:
It is not allowed to assign a mount point to a device with nonexistent or unknown file system.

If a partition is not formatted it has no filing structure, no files, no filing index, no mechanism for an operating to read its internal content...................

When a partition is created in Fat32, or any partition type for that matter, only 16 bytes in the partition table is registered. The entire area of the hard disk defined by the partition boundaries is in fact "raw" and "untouched". No operating system in the world can mount it.

The formatting instruction actually creates a boot sector and reserve the front end of the partition for the house keeping and indexing of the filing system, leaving the big rear end for the actual storage of the data. The mounting operating acquires the filing indexing system so that files can be stored and retrieved correctly in the partition.

I known I am not answering your question but just putting the logic forward. If I am wrong then someone will point it out.

Desktop partitioning tools notoriously mix the partition creation and formatting together and users may get confused.

pengu · 10-07-2007, 07:59 PM

Quote:

If a partition is not formatted it has no filing structure, no files, no filing index, no mechanism for an operating to read its internal content...................

i guess you didnt understand me, the partition is formated already, and has all my personal files on it. When I said "without formating" i guess i meant "without RE-formating"

besides, I can mount the file fine from the command line after startup.

disilusionist, thanks for the help, yeah i thought of a start up script, but mounting the partition requires root privileges... do you know how i would get that to work?

saikee · 10-07-2007, 08:05 PM

To get root privilege in OpenSuse at terminal

Code:

su

then supply the password. The prompt will change slightly signifying you are in root.

pengu · 10-07-2007, 08:47 PM

saikee, thanks for the help, but i think you need to read better... im asking about making a startup script to mount the partition.

putting "sudo mount -t vfat /dev/sda2 /home/jack/Personal" into a startup script is not going to do anything...

Disillusionist · 10-08-2007, 12:15 AM

I was talking about system startup scripts which run as root. as opposed to logon scripts which run as the user who is logging on.

go to /etc/init.d and create a new file, example:

Code:

#!/bin/sh
# Mount/Umount fat filesystem
#
. /lib/lsb/init-functions

case "$1" in
start) log_daemon_msg "Mounting fat filesystem" "Personal"
       # code to mount filesystem here
       log_end_msg $?
       ;;
stop)  log_daemon_msg "Unmounting fat filesystem" "Personal"
       # code to umount filesystem here
       log_end_msg $?
       ;;
restart) log_daemon_msg "Remounting fat filesystem" "Personal"
         # code to umount filesystem here
         # code to mount filesystem here
         log_end_msg $?
         ;;
*)       log_action_msg "Usage: /etc/init.d/Personal {start|stop|restart}"
         exit 2
         ;;
esac
exit 0

Then create a soft link to it from the runlevel you want to start it in:

cd /etc/rc2.d
ln -s ../init.d/Personal S99Personal

saikee · 10-08-2007, 04:44 AM

What's wrong with adding the red line in fstab?

Code:

/dev/disk/by-id/scsi-SATA_TOSHIBA_MK1032G_665G0518T-part3 /                    ext3       acl,user_xattr        1 1
/dev/disk/by-id/scsi-SATA_TOSHIBA_MK1032G_665G0518T-part5 swap                 swap       defaults              0 0
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0
/dev/hda5            /mnt/sda5            fat32      defaults              0 0

You need to create the directory /mnt/sda5 first though, using "nkdir /mnt/sda5" command.

After kernel 2.6.20 and newer kernels when all disks are controlled by libATA driver OpenSuse "likes" to use the "by-id" notation for the hard disk partitions because Pata disk hda, hdb, hdc and hdd names are no longer supported, although during the interim period some kernels may have been arranged to use the Pata disk names still. The standard device name in Linux is still usable. Ubuntu uses the "by-uuid" method. You can see all of them and how they are related in the /dev directory. To a kernel you can use any of the "by-id", "by-uuid", "by-label"...names. It doesn't matter to its operation. You can mix them as well.

To find out if Suse calls your partition hda5 or sda5 just type in a root terminal

Code:

fdisk -l