New answers tagged

0

Uncommenting the line, as already mentioned, would surely solve the problem (and, as you confirmed, it actually did). As this might be someone else's problem, and the title says fstab is alright, I'll add something else that I think might be relevant for people looking for the same question. I'm uncertain whether the errors=remount-ro is a standard on your ...


3

exfat behaves just like vfat and since it has no concept of permissions, chown and chmod both won't work. You have to specify mount options such as uid, fmask and dmask, e.g. defaults,noatime,nofail,uid=1000,fmask=0133,dmask=0022 (run id to find out what your ID is).


1

/media/user/apps/opt /opt none bind,x-systemd.requires=/media/user/apps Should do the trick. There are two more options that help doing a safe successive mounting, because when we need to specify order dependencies between mount commands and other units. x-systemd.after x-systemd.before So we can add /media/user/apps/opt /opt none bind,x-systemd.after=/...


3

You are mounting all three NTFS partitions to the same mount point (/media/data). You probably want to modify the entries in your /etc/fstab like so: UUID=B28691348690F9D5 /media/data1 ntfs defaults 0 0 UUID=228C52CC8C5299DD /media/data2 ntfs defaults 0 0 UUID=40D6A802D6A7F676 /media/data3 ntfs defaults 0 0 Don't forget to create the ...


0

You are running a verbose rsync inside a cronjob. That generates huge messages that will be emailed to you. Check the size of /var/spool/mail. If you do not have local delivery setup, then you could have a very big file named dead.letter in your /root or /home/YOUR_USER Anyway, your best be now might be to run baobab for example, to know what's eating up ...


Top 50 recent answers are included