Dependency failed for /mnt/DATA(SOLVED)

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help
Post Reply
alynur
Level 1
Level 1
Posts: 13
Joined: Sun Jan 07, 2018 11:49 pm

Dependency failed for /mnt/DATA(SOLVED)

Post by alynur » Fri Jan 12, 2018 2:43 pm

I have installed 18.3 Cinnamon on one of my partitions and if all I do is complete the first basic software update, the system boots up fine. But I use a DATA partition and once I've completed with mounting it and making changes to fstab, the system goes into emergency mode. The journalctl shows red at Timed out, waiting for device... Dependency failed for /mnt/DATA.
How do I correct this dependency issue? The fstab addition I made is such:

# User created DATA partition, mounted at /mnt/DATA
UUID=585c3e2f-c6be-4802-885d-eead48242766  /mnt/DATA     ext4     defaults     0     2

I am completely ignorant as to what dependencies they are refering to. Any help would be appreciated. :?
Last edited by alynur on Mon Jan 15, 2018 10:57 am, edited 1 time in total.

User avatar
Flemur
Level 17
Level 17
Posts: 7073
Joined: Mon Aug 20, 2012 9:41 pm
Location: Potemkin Village

Re: Dependency failed for /mnt/DATA

Post by Flemur » Fri Jan 12, 2018 3:25 pm

alynur wrote:The journalctl shows red at Timed out, waiting for device... Dependency failed for /mnt/DATA.
How do I correct this dependency issue? The fstab addition I made is such:

Code: Select all

# User created DATA partition, mounted at /mnt/DATA
UUID=585c3e2f-c6be-4802-885d-eead48242766  /mnt/DATA     ext4     defaults     0     2
I am completely ignorant as to what dependencies they are refering to. Any help would be appreciated. :?
I would do:
1 - sudo blkid
and make sure you got the UUID correct.

2 - check the partition for errors; if you can without DATA partition mounted, just start gparted, unmount DATA and "check" it.

3 - I'm not sure what the two numbers at the end mean***: my fstab line is:

Code: Select all

LABEL=DATA  /mnt/DATA  ext4 defaults,noatime 0 0
*** The sixth field (fs_passno).
This field is used by fsck(8) to determine the order in which
filesystem checks are done at boot time. The root filesystem
should be specified with a fs_passno of 1. Other filesystems
should have a fs_passno of 2
*. Filesystems within a drive will
be checked sequentially, but filesystems on different drives
will be checked at the same time to utilize parallelism avail-
able in the hardware. Defaults to zero (don't fsck) if not
present.

*I've always been using 0, so I guess I'm bad.
Please edit your original post title to include [SOLVED] if/when it is solved!
Your data and OS are backed up....right?
Mint 19.1 Xfce/fluxbox
Manjaro openbox/fluxbox

alynur
Level 1
Level 1
Posts: 13
Joined: Sun Jan 07, 2018 11:49 pm

Re: Dependency failed for /mnt/DATA

Post by alynur » Fri Jan 12, 2018 6:00 pm

Hi Flemur, that set up came from a Mint tutorial about creating a DATA partition. I've already checked the other stuff you mention. I will change the ending to look like yours and see what happens, thanks.

User avatar
Termy
Level 5
Level 5
Posts: 764
Joined: Mon Sep 04, 2017 8:49 pm
Location: UK
Contact:

Re: Dependency failed for /mnt/DATA

Post by Termy » Fri Jan 12, 2018 6:07 pm

Yeah, I doubt it'd be that last field; it's just a priority thing for fsck. Can you post the contents of the terminal command: inxi -Fz
Here to help.

I'm LearnLinux (LL) on YouTube: https://www.youtube.com/channel/UCfp-lN ... naEE6NtDSg
I'm also terminalforlife (TFL) on GitHub: https://github.com/terminalforlife

Mute Ant
Level 14
Level 14
Posts: 5135
Joined: Tue Sep 03, 2013 7:45 pm
Location: Norfolk UK

Re: Dependency failed for /mnt/DATA

Post by Mute Ant » Fri Jan 12, 2018 8:13 pm

"what dependencies they are referring to" Things that have to exist in order to do what the line in /etc/fstab specifies...
o A visible file-system that matches... UUID=585c3e2f-c6be-4802-885d-eead48242766
o A mount point that exists... /mnt/DATA
o A kernel that understands... ext4
While you're waiting, read the free novel we sent you. It's a Spanish story about a guy named "manual".

alynur
Level 1
Level 1
Posts: 13
Joined: Sun Jan 07, 2018 11:49 pm

Re: Dependency failed for /mnt/DATA

Post by alynur » Fri Jan 12, 2018 8:18 pm

Hi Termy, if you're wondering if it's a graphics card problem, it's not. And no i can't get that for you because I can't boot up the system. But I can give you a look at the equipment.

Code: Select all

System:    Host: albert-desktop Kernel: 4.13.0-26-generic x86_64 (64 bit)
           Desktop: N/A Distro: Peppermint Eight
Machine:   Mobo: ASRock model: AM1B-M
           Bios: American Megatrends v: P1.50 date: 04/29/2015
CPU:       Quad core AMD Athlon 5370 APU with Radeon R3 (-MCP-) cache: 8192 KB 
           clock speeds: max: 2200 MHz 1: 800 MHz 2: 2200 MHz 3: 2200 MHz 4: 800 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series]
           Display Server: X.Org 1.19.5 drivers: ati,radeon (unloaded: fbdev,vesa)
           Resolution: 1024x768@75.03hz, 1024x768@75.03hz
           GLX Renderer: Gallium 0.4 on AMD CEDAR (DRM 2.50.0 / 4.13.0-26-generic, LLVM 4.0.0)
           GLX Version: 3.0 Mesa 17.0.2
Audio:     Card-1 Advanced Micro Devices [AMD] FCH Azalia Controller
           driver: snd_hda_intel
           Card-2 Advanced Micro Devices [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300 Series]
           driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.13.0-26-generic
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169
           IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 500.1GB (13.8% used)
           ID-1: /dev/sda model: WDC_WD5000AUDX size: 500.1GB
Partition: ID-1: / size: 20G used: 8.2G (45%) fs: ext4 dev: /dev/sda1
           ID-2: swap-1 size: 8.65GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 36.0C mobo: N/A gpu: 55.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 179 Uptime: 15 min Memory: 1573.2/7914.8MB
           Client: Shell (bash) inxi: 2.2.35 

Mattyboy
Level 6
Level 6
Posts: 1196
Joined: Thu Mar 26, 2015 2:17 pm

Re: Dependency failed for /mnt/DATA

Post by Mattyboy » Fri Jan 12, 2018 10:33 pm

Try

Boot the system until you get to grub.. ( press and hold shift or esc )
Select the recovery option from advanced and let it run through the checks. If the system finds a problem you could get the option to sign in as root in a shell.
Sign using your login, then type.

Code: Select all

nano /etc/fstab
Use nano to delete the fstab entry that you made and save out. Be careful you do this correctly. If you've never used nano suggest you watch a youtube vid or something.

Exit nano then type.

Code: Select all

shutdown -r now
System should now boot ok.
Last edited by Mattyboy on Sat Jan 13, 2018 9:29 am, edited 1 time in total.

User avatar
Termy
Level 5
Level 5
Posts: 764
Joined: Mon Sep 04, 2017 8:49 pm
Location: UK
Contact:

Re: Dependency failed for /mnt/DATA

Post by Termy » Sat Jan 13, 2018 6:45 am

No, I wasn't thinking it's a graphics issue. It's just someting that can help. I was also curious to see some more info about your drive/parition setup, which inxi shows. Hope it's sorted.
Here to help.

I'm LearnLinux (LL) on YouTube: https://www.youtube.com/channel/UCfp-lN ... naEE6NtDSg
I'm also terminalforlife (TFL) on GitHub: https://github.com/terminalforlife

alynur
Level 1
Level 1
Posts: 13
Joined: Sun Jan 07, 2018 11:49 pm

Re: Dependency failed for /mnt/DATA

Post by alynur » Sat Jan 13, 2018 11:27 am

Hi Termy, okay, I was able to access the partition that Mint is installed on while in Peppermint and deleted the fstab addition I had made and I am now booted into Mint. Here's the inxi -Fz you asked for

Code: Select all

albert@albert-desktop ~ $ inxi -Fz
System:    Host: albert-desktop Kernel: 4.13.0-26-generic x86_64 (64 bit)
           Desktop: Cinnamon 3.6.6  Distro: Linux Mint 18.3 Sylvia
Machine:   Mobo: ASRock model: AM1B-M
           Bios: American Megatrends v: P1.50 date: 04/29/2015
CPU:       Quad core AMD Athlon 5370 APU with Radeon R3 (-MCP-) cache: 8192 KB 
           clock speeds: max: 2200 MHz 1: 2000 MHz 2: 800 MHz 3: 1000 MHz
           4: 800 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series]
           Display Server: X.Org 1.18.4 drivers: ati,radeon (unloaded: fbdev,vesa)
           Resolution: 1024x768@60.00hz, 1024x768@60.00hz
           GLX Renderer: Gallium 0.4 on AMD CEDAR (DRM 2.50.0 / 4.13.0-26-generic, LLVM 4.0.0)
           GLX Version: 3.0 Mesa 17.0.7
Audio:     Card-1 Advanced Micro Devices [AMD] FCH Azalia Controller
           driver: snd_hda_intel
           Card-2 Advanced Micro Devices [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300 Series]
           driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.13.0-26-generic
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169
           IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 500.1GB (3.0% used)
           ID-1: /dev/sda model: WDC_WD5000AUDX size: 500.1GB
Partition: ID-1: / size: 39G used: 6.6G (18%) fs: ext4 dev: /dev/sda8
           ID-2: swap-1 size: 8.65GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 21.2C mobo: N/A gpu: 53.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 181 Uptime: 8 min Memory: 1001.5/7914.8MB
           Client: Shell (bash) inxi: 2.2.35 
albert@albert-desktop ~ $ 
I was able to remake the DATA entry in /mnt, take ownership and mount it. It all looks good to that point. I made a new fstab entry which is here

Code: Select all

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda8 during installation
UUID=88a3e321-b0eb-4c56-b996-9652f91393d1 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=8480d5c8-3e88-4c90-ae0f-0cd5ed7d040b none            swap    sw              0       0
#
# User created DATA partition, mounted at /mnt/DATA
UUID=585c3e2f-c6be-4802-885d-eead48242766 /mnt/DATA     ext4  defaults, noatime 0 1
	
and now when I reboot, it will boot up but the DATA partition does not mount and all my symlinks are X'ed. If I run

Code: Select all

sudo mount /dev/sda3 /mnt/DATA
it mounts up and looks like it should with all symlinks working. At least I can boot into the system but why won't it boot up the DATA partition?
Before you ask, here is blkid

Code: Select all

albert@albert-desktop ~ $ sudo blkid
/dev/sda1: UUID="9f51d0f7-f14a-43ba-9da1-f17accb3638d" TYPE="ext4" PARTUUID="e0a222e4-01"
/dev/sda2: UUID="47bea197-a545-4218-92e1-62a6f0bc3961" TYPE="ext4" PARTUUID="e0a222e4-02"
/dev/sda3: UUID="585c3e2f-c6be-4802-885d-eead48242766" TYPE="ext4" PARTUUID="e0a222e4-03"
/dev/sda5: UUID="8480d5c8-3e88-4c90-ae0f-0cd5ed7d040b" TYPE="swap" PARTUUID="e0a222e4-05"
/dev/sda6: UUID="816d011f-dd4e-4a8b-ac0e-5ae079899df8" TYPE="ext4" PARTUUID="e0a222e4-06"
/dev/sda7: UUID="623e8f41-8a82-4bcc-83c0-c63655a03f38" TYPE="ext4" PARTUUID="e0a222e4-07"
/dev/sda8: UUID="88a3e321-b0eb-4c56-b996-9652f91393d1" TYPE="ext4" PARTUUID="e0a222e4-08"
/dev/sda9: UUID="5af1afd6-6759-473c-a3e1-383e6eb2027f" TYPE="ext4" PARTUUID="e0a222e4-09"
/dev/sda10: UUID="46843385-2546-4220-a003-d573d48c6750" TYPE="ext4" PARTUUID="e0a222e4-0a"
I could just ignore this whole mess as long as the system mounts and just mount the DATA volume in file manager and continue about my business but I don't think a distribution like Mint should work like this.

User avatar
Flemur
Level 17
Level 17
Posts: 7073
Joined: Mon Aug 20, 2012 9:41 pm
Location: Potemkin Village

Re: Dependency failed for /mnt/DATA

Post by Flemur » Sat Jan 13, 2018 11:51 am

alynur wrote:UUID=585c3e2f-c6be-4802-885d-eead48242766 /mnt/DATA ext4 defaults, noatime 0 1
You have an extra space after "defaults,": should be

Code: Select all

UUID=585c3e2f-c6be-4802-885d-eead48242766 /mnt/DATA     ext4  defaults,noatime 0 1
Please edit your original post title to include [SOLVED] if/when it is solved!
Your data and OS are backed up....right?
Mint 19.1 Xfce/fluxbox
Manjaro openbox/fluxbox

alynur
Level 1
Level 1
Posts: 13
Joined: Sun Jan 07, 2018 11:49 pm

Re: Dependency failed for /mnt/DATA

Post by alynur » Sat Jan 13, 2018 1:47 pm

Hi Flemur, I made that change, took out the extra space but that made no change on reboot. Still not mounting.

User avatar
Termy
Level 5
Level 5
Posts: 764
Joined: Mon Sep 04, 2017 8:49 pm
Location: UK
Contact:

Re: Dependency failed for /mnt/DATA

Post by Termy » Sat Jan 13, 2018 4:59 pm

Good info. Are you able to mount the filesystem on-the-fly, like with mount, udisksctl, or a GUI file manager? Sounds like you can, but I just wanted to check. If it works normally, that should rule out any issues with the device/filesystem, which is at least something.

Any useful output from dmesg, or especially dmesg | grep "sda3"?

By the way, have you tried the LABEL="your_label_here" route, or the block device name (which for that partition seems to be /dev/sda3)? Just in-case there's some weird bug going on here. If that partition has no label, you can use e2label /dev/sda3 "your_label_here" to set/change it, for ext2, ext3, and ext4 filesystems.

Last thing, I'm a bit confused by the output you've shown. Your blkid output shows 1 storage device with 10 partitions, yet inxi shows you have just 2 partitions on that single device. I'm probably just overlooking something.
Here to help.

I'm LearnLinux (LL) on YouTube: https://www.youtube.com/channel/UCfp-lN ... naEE6NtDSg
I'm also terminalforlife (TFL) on GitHub: https://github.com/terminalforlife

alynur
Level 1
Level 1
Posts: 13
Joined: Sun Jan 07, 2018 11:49 pm

Re: Dependency failed for /mnt/DATA

Post by alynur » Sun Jan 14, 2018 12:05 pm

Termy wrote:Good info. Are you able to mount the filesystem on-the-fly, like with mount, udisksctl, or a GUI file manager? Sounds like you can, but I just wanted to check. If it works normally, that should rule out any issues with the device/filesystem, which is at least something.

Any useful output from dmesg, or especially dmesg | grep "sda3"?

By the way, have you tried the LABEL="your_label_here" route, or the block device name (which for that partition seems to be /dev/sda3)? Just in-case there's some weird bug going on here. If that partition has no label, you can use e2label /dev/sda3 "your_label_here" to set/change it, for ext2, ext3, and ext4 filesystems.

Last thing, I'm a bit confused by the output you've shown. Your blkid output shows 1 storage device with 10 partitions, yet inxi shows you have just 2 partitions on that single device. I'm probably just overlooking something.
Hi Termy, here is the info from

Code: Select all

dmesg
and

Code: Select all

dmesg | grep "sda3"

Code: Select all

UTILS +KMOD -IDN)
[    7.540216] systemd[1]: Detected architecture x86-64.
[    7.542240] systemd[1]: Set hostname to <albert-desktop>.
[    7.676454] systemd-fstab-generator[329]: Mount point ext4  is not a valid path, ignoring.
[    9.439685] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    9.439891] systemd[1]: Created slice System Slice.
[    9.440025] systemd[1]: Listening on Journal Socket.
[    9.440863] systemd[1]: Started Braille Device Support.
[    9.441151] systemd[1]: Reached target Encrypted Volumes.
[    9.441988] systemd[1]: Mounting Debug File System...
[    9.442128] systemd[1]: Listening on udev Kernel Socket.
[    9.796895] lp: driver loaded but no devices found
[    9.966521] ppdev: user-space parallel port driver
[    9.997412] parport_pc 00:03: reported by Plug and Play ACPI
[    9.997486] parport0: PC-style at 0x378, irq 5 [PCSPP,EPP]
[   10.092377] lp0: using parport0 (interrupt-driven).
[   18.436176] EXT4-fs (sda8): re-mounted. Opts: errors=remount-ro
[   18.484180] systemd-journald[351]: Received request to flush runtime journal from PID 1
[   18.701110] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   18.814590] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0
[   18.814596] piix4_smbus 0000:00:14.0: Using register 0x2e for SMBus port selection
[   18.815022] piix4_smbus 0000:00:14.0: Auxiliary SMBus Host Controller at 0xb20
[   18.841973] snd_hda_intel 0000:01:00.1: Handle vga_switcheroo audio client
[   18.858169] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:02.1/0000:

Code: Select all

albert@albert-desktop ~ $ dmesg | grep "sda3"
[    2.748843]  sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 sda10 >

Interesting, so should sda3 be in place of etc4 in the fstab file? I do think there is some sort of weird bug going on because the fstab I use in all the other ubuntu distros I have installed in this hard drive work fine with

Code: Select all

#User created DATA partition, mounted at /mnt/DATA
UUID=585c3e2f-c6be-4802-885d-eead48242766  /mnt/DATA
defaults, discard 0 2
Also, I am unfamiliar with what the fstab file would look like using the LABEL= option. Is the label indidcated in the blkid list

Code: Select all

/dev/sda3: UUID="585c3e2f-c6be-4802-885d-eead48242766" TYPE="ext4" PARTUUID="e0a222e4-03"
?

To clear up your confusion, the blkid list shows all the partitions in the hard drive whereas the inxi only shows whats being used in the Mint distro.

User avatar
Termy
Level 5
Level 5
Posts: 764
Joined: Mon Sep 04, 2017 8:49 pm
Location: UK
Contact:

Re: Dependency failed for /mnt/DATA

Post by Termy » Sun Jan 14, 2018 4:54 pm

This is really baffling me. I keep staring at your fstab file. I can't make sense of this. I assume you fixed the syntax error mentioned by the other posted, regarding the extra space; is that true? Do you have any tabs there which are perhaps messing up how the fields are recognised? Shouldn't be that, but I'm grasping at straws. The LABEL format is just like UUID, but instead of UUID=your_UUID_here, it's LABEL=your_label_here.

I'm beginning to think it's a bug as well. :( I've actually just installed the same thing as you have in a virtual machine, so I'll actually try to recreate your issue.

EDIT: It still works on my end. I did the same sort of thing with my fstab file and had it point to /mnt/DATA, with the same mount options as you. The difference is I'm using a floppy disk as I ran out of space on the virtual machine. xD I also didn't go by UUID, but instead by /dev/fd0, so maybe you should see if that works (using the right one for your setup, of course) instead of going the UUID route, at least for now. Oh, I also have auto instead of ext4, so maybe you could try that?
Here to help.

I'm LearnLinux (LL) on YouTube: https://www.youtube.com/channel/UCfp-lN ... naEE6NtDSg
I'm also terminalforlife (TFL) on GitHub: https://github.com/terminalforlife

alynur
Level 1
Level 1
Posts: 13
Joined: Sun Jan 07, 2018 11:49 pm

Re: Dependency failed for /mnt/DATA

Post by alynur » Sun Jan 14, 2018 9:52 pm

Hi Termy, Yes I've tried everything that was mentioned. I've tried it using /dev/sda3 ext4 and /dev/sda3 auto and nothing mounts up the sda3 partition. What's even stranger is to be able to boot into the system I first had to remove the entry completely as mattyboy suggested and when I tried Flemur's entry it did boot into the system but didn't mount the partition. and then I tried my original entry and it did boot into the system but without mounting the partition, this was the same entry that caused it to go to emergency mode in the first place. And it didn't matter if I was trying to boot the 4.13 kernel or the 4.10 kernel, it would go into emergency mode. So I'm sure it's a bug in the boot files which would lead me to ask how can I remove it and reinstall it?

User avatar
Termy
Level 5
Level 5
Posts: 764
Joined: Mon Sep 04, 2017 8:49 pm
Location: UK
Contact:

Re: Dependency failed for /mnt/DATA

Post by Termy » Mon Jan 15, 2018 6:34 am

So I'm sure it's a bug in the boot files which would lead me to ask how can I remove it and reinstall it?
/boot is mainly down to your bootloader (likely GRUB), and so I'm not sure whether reinstalling that would do much at this point. Since all you're wanting is to mount that partition on startup, and fstab isn't behaving, a workaround for this issue might as well be to use whatever GUI you have available to set a startup (post-login) process, that being: udisksctl mount --no-user-interaction --options noatime -b /dev/sda3 The only difference here, being it will mount to the standard /media/your_user_name, rather than /mnt/DATA. Remember, if you do this, to remove the dud entry in fstab which isn't working.

The flip side is of course that it won't be going by UUID or even LABEL, but instead by block device name, so this could change. Luckily, a small shell script could get around this issue easily enough, so if this is needed, let me know.
Here to help.

I'm LearnLinux (LL) on YouTube: https://www.youtube.com/channel/UCfp-lN ... naEE6NtDSg
I'm also terminalforlife (TFL) on GitHub: https://github.com/terminalforlife

altair4
Level 19
Level 19
Posts: 9687
Joined: Tue Feb 03, 2009 10:27 am

Re: Dependency failed for /mnt/DATA

Post by altair4 » Mon Jan 15, 2018 8:16 am

Termy wrote:Since all you're wanting is to mount that partition on startup, and fstab isn't behaving, a workaround for this issue might as well be to use whatever GUI you have available to set a startup (post-login) process, that being: udisksctl mount --no-user-interaction --options noatime -b /dev/sda3 The only difference here, being it will mount to the standard /media/your_user_name, rather than /mnt/DATA. Remember, if you do this, to remove the dud entry in fstab which isn't working.

The flip side is of course that it won't be going by UUID or even LABEL, but instead by block device name, so this could change. Luckily, a small shell script could get around this issue easily enough, so if this is needed, let me know.
Just a suggestion. Change /dev/sda3 to /dev/disk/by-uuid/585c3e2f-c6be-4802-885d-eead48242766 :

Code: Select all

udisksctl mount --no-user-interaction --options noatime -b /dev/disk/by-uuid/585c3e2f-c6be-4802-885d-eead4824276
Side note: Does anyone know what the hell this error means in dmesg:
systemd-fstab-generator[329]: Mount point ext4 is not a valid path, ignoring.
That can happen if you really screw up the syntax in fstab but I can not see it.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.

altair4
Level 19
Level 19
Posts: 9687
Joined: Tue Feb 03, 2009 10:27 am

Re: Dependency failed for /mnt/DATA

Post by altair4 » Mon Jan 15, 2018 8:37 am

Another option if you want to go with the Startup Applications route is to change your fstab entry to this:

Code: Select all

UUID=585c3e2f-c6be-4802-885d-eead48242766 /mnt/DATA     ext4  defaults,noatime,noauto,user,exec 0 2
noauto = will prevent this partition from mounting at boot time.
user = will make it so you don't have to be root / sudo to mount it.

Then your Startup Application command would be: mount /mnt/DATA

Both this and the udisks method is making a bet that the time it takes to get to and process the login sequence is enough time for the system to "find" the partition.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.

alynur
Level 1
Level 1
Posts: 13
Joined: Sun Jan 07, 2018 11:49 pm

Re: Dependency failed for /mnt/DATA

Post by alynur » Mon Jan 15, 2018 10:56 am

altair4 wrote:Another option if you want to go with the Startup Applications route is to change your fstab entry to this:

Code: Select all

UUID=585c3e2f-c6be-4802-885d-eead48242766 /mnt/DATA     ext4  defaults,noatime,noauto,user,exec 0 2
noauto = will prevent this partition from mounting at boot time.
user = will make it so you don't have to be root / sudo to mount it.

Then your Startup Application command would be: mount /mnt/DATA

Both this and the udisks method is making a bet that the time it takes to get to and process the login sequence is enough time for the system to "find" the partition.
Hi altair4, thanks for jumping in. I inserted the above code into the fstab file and it booted up, the system that is, and when I opened file manager of course all the symlinks were inop and the DATA partition volume was not in the lists of available volumes to mount.That kind of threw me, If I hadn't mounted it yet, why wasn't it in the list? I looked in the mnt folder and there existed two DATA folders both of which were empty. This also threw me, so I tried to delete one and couldn't even running sudo rm -rv. so I took possession of /mnt/DATA and then was able to remove one of the folders. By this time I had completely forgotten that I still had to mount the partition, my memory is only good for about 10 seconds, and decided that this wasn't working and that I would undo the fstab entry. But before deleting the entire entry, I looked at it and wondered what would happen if I just removed the user,exec part and I did. So I changed the tail end to read "defaults,noatime,noauto 0 2" and it works! It boots up, mounts and all symlinks are working, just like it's supposed to. I really appreciate all of your help everyone. I was almost ready to give up on Mint. :D

User avatar
Termy
Level 5
Level 5
Posts: 764
Joined: Mon Sep 04, 2017 8:49 pm
Location: UK
Contact:

Re: Dependency failed for /mnt/DATA(SOLVED)

Post by Termy » Mon Jan 15, 2018 1:23 pm

@altair4: THANK YOU. I never knew you could do that! Or at least it never occurred to me to do it that way. Definitely gonna note that down. :) I suggested the udisksctl method because it doesn't need root and saves doing anything with fstab, which seems to not work properly with the OP.
Here to help.

I'm LearnLinux (LL) on YouTube: https://www.youtube.com/channel/UCfp-lN ... naEE6NtDSg
I'm also terminalforlife (TFL) on GitHub: https://github.com/terminalforlife

Post Reply

Return to “Newbie Questions”