FSTAB Problems


Recommended Posts

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.

Link to comment
https://www.neowin.net/forum/topic/934862-fstab-problems/
Share on other sites

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...

Link to comment
https://www.neowin.net/forum/topic/934862-fstab-problems/#findComment-593104718
Share on other sites

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

Link to comment
https://www.neowin.net/forum/topic/934862-fstab-problems/#findComment-593113940
Share on other sites

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

Link to comment
https://www.neowin.net/forum/topic/934862-fstab-problems/#findComment-593115692
Share on other sites

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.

Link to comment
https://www.neowin.net/forum/topic/934862-fstab-problems/#findComment-593115712
Share on other sites

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

Link to comment
https://www.neowin.net/forum/topic/934862-fstab-problems/#findComment-593115722
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I bought one of these last year. I really hope I won't have to deal with this crap. My drive is in good condition at the moment.
    • Umm, read my answer again! If you have something to add or contribute, feel free. Otherwise my point was that you apparently dont want faster updates... so you want slower updates by process of elimination. If you have something to contribute, meaningful answers are better.
    • These features described above are good, but far from what developers will like the most. The main feature that developers will care and love the most it's called "Bring Your Own Models". It gives us the ability to connect to LOCAL AI models running on Ollama. The feature it's located on GitHub Copilot tab -> On the model picker where you can select "manage models" instead of paid models and then it will show you the "Bring your own models" window where you can now select Ollama and the endpoint of your local server. So if you have a beefy spec machine you can now use your own model 100% local inside Visual Studio 2026 18.7.0
    • Microsoft Teams is getting a controversial location tracking feature that users may hate by Usama Jawad Image generated with Microsoft Copilot Earlier this year, Microsoft planned to roll out a controversial location tracking feature in Teams, but following customer feedback, it decided to delay its release. The bad news is that the company has decided to launch it later this year, but it's based on roughly the same design that was shared earlier, which means that many users still have good reason to worry. Basically, Microsoft Places and Teams have received workplace check-ins via Wi-Fi. The idea is that if an employee arrives at the office and connects to their enterprise network, their profile status indicator will show them as being present in the office. For example, if you arrive at work, open Teams on your PC, and connect to the "Studio B" company Wi-Fi network, your Teams profile will indicate that you are present in "Studio B", as shown below: Microsoft says that this feature is basically a replacement for physical workplace check-in peripherals, it reduces the need to manually update your status, and it also enables co-workers to know that you're at work so that they can coordinate in-person meetings with you. IT admins can enable this workplace check-in capability at a tenant level, and users have the ability to control whether they want to enable it or not. Of course, all of that sounds great on paper, but naturally, many Teams customers may still have concerns, as they did before. This is because it enables your reporting manager and other members of the organization to track if you are at the office, when you arrive at the office, and where you are right now. This could be problematic for people who work in what they consider to be flexible work environments or hybrid setups, and this kind of location tracking could be considered an invasion of privacy. Microsoft has tried to alleviate some of these concerns by letting users know that they can manually set their location easily, which essentially overrides workplace check-in if they feel uncomfortable with it. However, that doesn't really solve the problem because your organization could enforce a workplace policy that mandates that this feature remains enabled. The Redmond tech giant has also assured users that this capability does not store historical data and is only a real-time indicator of location. Finally, it only generates a signal when you connect to a corporate network, which means that if you are working from home and connect your PC to your personal Wi-Fi, it won't broadcast your location to your employer; you will simply be shown as "Remote". Microsoft has encouraged IT admins to prepare for this change and begin informing users so they know what to expect once it begins rolling out later this year.
  • Recent Achievements

    • Very Popular
      AndrewSteel earned a badge
      Very Popular
    • Veteran
      Taliseian went up a rank
      Veteran
    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      516
    2. 2
      +Edouard
      162
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      82
    5. 5
      ATLien_0
      81
  • Tell a friend

    Love Neowin? Tell a friend!