FSTAB Problems

[mps69]

I'm honestly pulling my hair out with this one, and I just can't get my head round it.

Little bit of background, using Ubuntu 10.04, with 2 external drives, one with movies. The second drive has to two partitions, one of these has all my music.

I have set Rhythmbox to point towards my music drive.

When re-boot the PC the drive changes and Rhythmbox can't find the music drive.

I've tried using py-Storage Device Manager to set the drives as static, but this doesn't seem to work.

All the drive are set to mount automatically at boot up, and for the best part this works.

I've done a great deal of hunting around, and research on the subject, but i just can't understand the process fully, normally I can follow tutorials but not this time :blush:

I'm hope someone throws me a life line here as I really don't want to give up on this OS over such a silly headache.

i can post the fstab if that will help.

[Lechio]

To edit your fstab correctly (if you haven't done this yet) you need to know the name of the device partitions and its file system format. To do this type in a terminal the following without quotes: "sudo fdisk -l"

Post the output here.

[Farstrider]

I'm hope someone throws me a life line here as I really don't want to give up on this OS over such a silly headache.

This I can NEVER understand! There are times in WIndows/OSX when a user battles with something, but does not "give up" on the OS!! Why should it be different when you use Linux?

Have you tried to use this: It's in the repo's: Using your Synaptic Package Manager

The basic functionalities of mountmanager are:

- Mount and unmount partitions (ext3/2, ntfs, swap, fat, reiserfs, iso9660,

udf, ...)

- Show all logical and physical disks

- Change config file /etc/fstab

- Descriptions of options and other settings of mounting

- Restoration system

- Images mounting and unmounting (Nrg, Mdf , Ccd, Bin , etc)

- Udev rules creation

- Disk wizard

- Etc...

[mps69]

Guys thanks for your offer of potential help.

I've inserted my fstab as it stands at the moment, got my information slightly wrong in my original post my music drive does not have a partition in it. This is set at /dev/sdd, if this could remain at this would be great.

@ Farstrider, I've not tried your recommendation yet, as I'm hoping to achieve the same result without installing more application, and also getting a better understanding of the file system.

Disk /dev/sda: 30.8 GB, 30750031872 bytes
255 heads, 63 sectors/track, 3738 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x1549f232

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        1913    15366141    7  HPFS/NTFS
/dev/sda2            1914        3738    14659312+   5  Extended
/dev/sda3            3739        3739           0    e  W95 FAT16 (LBA)
/dev/sda5            1914        3738    14659281    7  HPFS/NTFS

Disk /dev/sdb: 160.0 GB, 160041885696 bytes
240 heads, 63 sectors/track, 20673 cylinders
Units = cylinders of 15120 * 512 = 7741440 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x1b3e1b3d

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1         468     3538048+   c  W95 FAT32 (LBA)
/dev/sdb2   *         469        6735    47378520    7  HPFS/NTFS
/dev/sdb3            6736       20673   105371280    5  Extended
/dev/sdb5            6736       15107    63292288+   7  HPFS/NTFS
/dev/sdb6           15108       20673    42078928+   7  HPFS/NTFS

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xe8900690

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1       31871   256003776    7  HPFS/NTFS
/dev/sdc2           31872      121601   720756225    f  W95 Ext'd (LBA)
/dev/sdc5           31872       63742   256003776    7  HPFS/NTFS
/dev/sdc6           63743      121601   464752386    7  HPFS/NTFS

Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
1 heads, 63 sectors/track, 31008336 cylinders
Units = cylinders of 63 * 512 = 32256 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00aa87c3

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1   *           2    31008256   976760032+   7  HPFS/NTFS

[MR_Candyman]

That doesn't look like an fstab at all to me. I'm used to an fstab like this:

/dev/sda1 /windows vfat iocharset=iso8859-1,codepage=850,umask=000 0 0

/dev/hdd /media/cdrecorder auto pamconsole,exec,noauto,managed 0 0

/dev/hdc /media/cdrecorder1 auto pamconsole,exec,noauto,managed 0 0

^physical address ^mounting location

edit: This is the place I recommend going to learn about the fstab

[cybertimber2008]

edit: This is the place I recommend going to learn about the fstab

That's because it's the output of "fdisk -l" command which lists all connected drives, partitions, and other information.

the *file* /etc/fstab is what you are reffering to, but haivn the fdisk -l output helps to understand how his system is set up and how the /etc/fstab needs to be written to get everything working.

[MR_Candyman]

That's because it's the output of "fdisk -l" command which lists all connected drives, partitions, and other information.

the *file* /etc/fstab is what you are reffering to, but haivn the fdisk -l output helps to understand how his system is set up and how the /etc/fstab needs to be written to get everything working.

wow, first I've heard of this command. It seems pretty counter-intuitive to me actually