Failed to start Mount removable media on sda1

[ydar]

But that line isn’t even needed, see the discussion I linked to.

[soundofthunder]

@ydar

But that line isn’t even needed, see the discussion I linked to

Without checking the link, I presume it was @Aragorn’s post; which I tend to agree with. which doesn’t detract from my comment, regardless of whether its needed. However, I still don’t understand the OP’s apparent need for the mask.

On the possibility of delay mounting: This could be a job for @scotty65 who seems to enjoy a scripting challenge.

[Aragorn]

@soundofthunder

However, I still don’t understand the OP’s apparent need for the mask.

It’s a default, created by some utilities — possibly some partition manager, or calamares.

---

@Mirdarthos

Just add noauto to the mount options in fstab, and mount in rc.local.

If the drive is removable, then I would certainly also add nofail. Saves the system from stalling if polling the drive times out.

[soundofthunder]

Opening another avenue of investigation, I just found this:

Unable to mount fat or ntfs drives after updating

After the last update, I had the same problem. At the moment, the only solution I found was to install ntfs-automount, from AUR.

… which might possibly be related, given the timeframe.

[scotty65]

I’m afraid that I have no experience at all in mounting disks - my PC has 1 internal HDD & 1 external HDD that is mounted by Plasma upon login. And I am still quite inexperienced with systemd - I can write a timer to run a job as a user, but I’ve never written anything to do with the system.

These links may help (if you haven’t already had a look at them):

[root tip] [How To] systemd mount unit samples

Difficulty: ★★☆☆☆ Example mount units for systemd The examples here are a supplement to the guide on systemd mount units Remember to remove the comments placed in the units - they are not writing for copy-paste but as examples. (comments is text beginning with a #) [root tip] [How To] Use systemd to mount ANY device Only use an automount unit if the device is not readily available at boot like removable devices and network locations. Important rule …

[root tip] [How To] Use systemd to mount ANY device

Difficulty: ★☆☆☆☆ Disk device recognition Manjaro uses udev (see Arch Wiki) to load devices at boot time. The loading of devices is arbitrary and therefore you cannot predict which device will be available at a given path. But static device names do exist and you can assign specific locations to your device and thus ensure e.g. scripts will work as expected. What to learn Overview of system mount units Structure and Content of a mount unit Mount at boot (immediate mount) Mount on demand (m…

systemd.mount — Mount unit configuration

[Arikania]

For clarity’s sake: the disks do get mounted. I can access all data on them, and mount -a confirms this by not making any changes.

The problem is that Manjaro seems to think that my internal disks are removables, like USB sticks or something, and that the mount service doesn’t start.

As a result, accessing the disks consumes several seconds.

[Mirdarthos]

@Aragorn

If the drive is removable, then I would certainly also add nofail. Saves the system from stalling if polling the drive times out.

Since the possibility is that there is simply a timeout,

[soundofthunder]

@Mirdarthos

Scroll up even further.

[Mirdarthos]

Nope. That’s why I added the quote. Makes scrolling unnecessary.

[Arikania]

I’d need to find out why the media-mount service doesn’t start, or why Manjaro thinks that my hard disks are external. That is the actual culprit, I think.

[Mirdarthos]

What’s the output of:

systemctl list-units | grep --ignore-case sda

[Arikania]

systemctl list-units | grep --ignore-case sda gives:

  sys-devices-pci0000:00-0000:00:02.1-0000:02:00.1-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda1.device  loaded active plugged   TOSHIBA_MG09ACA18TE 1
  sys-devices-pci0000:00-0000:00:02.1-0000:02:00.1-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda2.device  loaded active plugged   TOSHIBA_MG09ACA18TE 2
  sys-devices-pci0000:00-0000:00:02.1-0000:02:00.1-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda3.device  loaded active plugged   TOSHIBA_MG09ACA18TE 3
  sys-devices-pci0000:00-0000:00:02.1-0000:02:00.1-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda4.device  loaded active plugged   TOSHIBA_MG09ACA18TE 4
  sys-devices-pci0000:00-0000:00:02.1-0000:02:00.1-ata1-host0-target0:0:0-0:0:0:0-block-sda.device       loaded active plugged   TOSHIBA_MG09ACA18TE
● media-mount@sda1.service                                                                               loaded failed failed    Mount removable media on sda1
● media-mount@sda2.service                                                                               loaded failed failed    Mount removable media on sda2
● media-mount@sda3.service                                                                               loaded failed failed    Mount removable media on sda3
● media-mount@sda4.service                                                                               loaded failed failed    Mount removable media on sda4

[Arikania]

I re-installed the system, and the problem is over now.

Another rather minor issue popped up, but I’ll start a new thread about it later, since it’s totally not related to this one.

[soundofthunder]

@Arikania

I re-installed the system, and the problem is over now.

The drives are now showing as internal; is that right?