Mount drive at boot up problem.

[SteveRiley]

Hm. findmnt should be showing your entire mount hierarchy, like this:

TARGET                        SOURCE       FSTYPE      OPTIONS
/                             /dev/sda2[/@]
                                           btrfs       rw,noatime,compress=lzo,ssd,space_cache
├─/sys                        sysfs        sysfs       rw,nosuid,nodev,noexec,relatime
│ ├─/sys/fs/cgroup            none         tmpfs       rw,relatime,size=4k,mode=755
│ │ └─/sys/fs/cgroup/systemd  systemd      cgroup      rw,nosuid,nodev,noexec,relatime,release_agent=/run/cgmanager/agents/cgm-release-agent.systemd,name=systemd
│ ├─/sys/fs/fuse/connections  none         fusectl     rw,relatime
│ ├─/sys/kernel/debug         none         debugfs     rw,relatime
│ ├─/sys/kernel/security      none         securityfs  rw,relatime
│ ├─/sys/firmware/efi/efivars none         efivarfs    rw,relatime
│ └─/sys/fs/pstore            none         pstore      rw,relatime
├─/proc                       proc         proc        rw,nosuid,nodev,noexec,relatime
│ └─/proc/sys/fs/binfmt_misc  binfmt_misc  binfmt_misc rw,nosuid,nodev,noexec,relatime
├─/dev                        udev         devtmpfs    rw,relatime,size=4016888k,nr_inodes=1004222,mode=755
│ └─/dev/pts                  devpts       devpts      rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000
├─/run                        tmpfs        tmpfs       rw,nosuid,noexec,relatime,size=805560k,mode=755
│ ├─/run/lock                 none         tmpfs       rw,nosuid,nodev,noexec,relatime,size=5120k
│ ├─/run/shm                  none         tmpfs       rw,nosuid,nodev,relatime
│ ├─/run/user                 none         tmpfs       rw,nosuid,nodev,noexec,relatime,size=102400k,mode=755
│ └─/run/rpc_pipefs           rpc_pipefs   rpc_pipefs  rw,relatime
├─/tmp                        tmpfs        tmpfs       rw,noatime
├─/boot/efi                   /dev/sda1    vfat        rw,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
└─/home                       /dev/sda2[/@home]
                                           btrfs       rw,noatime,compress=lzo,ssd,space_cache

I have no clue why it shows only one line for you. Try findmnt -A

And I see the unmount didn't work for you -- some other process is using the device. What's the output of fuser -vm /media?

[kdeuser]

@SteveRiley,

Requested data :

reel@BM2LTSR66RBin:/media/hd/home/reel$ findmnt
TARGET   SOURCE FSTYPE OPTIONS
/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000
reel@BM2LTSR66RBin:/media/hd/home/reel$ cd ~
reel@BM2LTSR66RBin:~$ sudo umount /media
[sudo] password for reel: 
umount: /media: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))
reel@BM2LTSR66RBin:~$ findmnt
TARGET   SOURCE FSTYPE OPTIONS
/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000
reel@BM2LTSR66RBin:~$ ls -al /
total 116
drwxr-xr-x  23 root root  4096 Feb 16 16:32 .
drwxr-xr-x  23 root root  4096 Feb 16 16:32 ..
drwxrwxr-x   2 root root  4096 Feb 12 11:16 bin
drwxr-xr-x   3 root root  4096 Feb 16 17:10 boot
drwxr-xr-x   2 root root  4096 Nov 15 11:10 cdrom
drwxr-xr-x  15 root root  4600 Feb 18 20:04 dev
drwxrwxr-x 205 root root 12288 Feb 18 21:39 etc
drwxr-xr-x   5 reel reel  4096 Feb 15 12:52 home
lrwxrwxrwx   1 root root    39 Feb 14 21:09 initrd.img -> /boot/initrd.img-3.15.10-031510-generic
lrwxrwxrwx   1 root root    39 Feb 14 21:09 initrd.img.old -> /boot/initrd.img-3.15.10-031510-generic
drwxr-xr-x  25 root root  4096 Feb 16 17:05 lib
drwx------   2 root root 16384 Nov 15 11:08 lost+found
drwxrwxrwt   9 root root   180 Feb 18 21:21 media
drwxr-xr-x   2 root root  4096 Feb 17 23:00 mnt
drwxr-xr-x   9 root root  4096 Feb  4 14:49 opt
dr-xr-xr-x 245 root root     0 Feb 18 20:02 proc
drwx------  31 root root  4096 Feb 16 20:22 root
drwxr-xr-x  36 root root  1380 Feb 18 20:04 run
drwxr-xr-x   2 root root 12288 Feb 16 17:06 sbin
drwxr-xr-x   3 root root  4096 Dec 19 01:11 srv
dr-xr-xr-x  13 root root     0 Feb 18 20:02 sys
drwxr-xr-x   2 root root  4096 Nov 10 21:32 tftpboot
drwxrwxrwt  12 root root 20480 Feb 19 00:05 tmp
drwxr-xr-x  10 root root  4096 Oct 15 13:15 usr
drwxr-xr-x  16 root root  4096 Jan  3 16:17 var
lrwxrwxrwx   1 root root    36 Feb 14 21:10 vmlinuz -> /boot/vmlinuz-3.15.10-031510-generic
lrwxrwxrwx   1 root root    36 Feb 14 21:10 vmlinuz.old -> /boot/vmlinuz-3.15.10-031510-generic
lrwxrwxrwx   1 root root    14 Nov 16 19:10 vtx -> /tmp/tmpfs/vtx
reel@BM2LTSR66RBin:~$ ls -al /media
total 16
drwxrwxrwt  9 root root  180 Feb 18 21:21 .
drwxr-xr-x 23 root root 4096 Feb 16 16:32 ..
drwxrwsr-x  2 root root  120 Feb 18 20:02 configs
d---------  2 root root   40 Feb 18 20:02 dvd
drwxrwsrwx 13 root root 4096 Feb 15 12:39 hd
drwxr-xr-x 43 root root 4096 Feb  1 11:02 hd1
drwxr-xr-x  8 root root   48 Jul 10  2014 hd2
drwxr-xr-x  8 root root   48 Jul 18  2014 hd3
drwxrwsr-x  2 root root  120 Feb 18 21:21 reel
reel@BM2LTSR66RBin:~$

[SteveRiley]

I do not understand how a tmpfs mount point can contain subdirectories that appear to persist between reboots?? Look at the dates for some of those.

Try this. Type the following. Reply here with the output of each one.

findmnt

cd ~

sudo umount /media

findmnt

ls -al /

ls -al /media

Could it be possible that there is also an actual /media directory under / on the drive, and it is this directory that contains the subdirectories we see, and that mounting /media on tmpfs doesn't affect the visibility of subdirectories underneath the on-drive /media? This exercise will tell us.

[kdeuser]

@SteveRiley,

Output of ls -al :

reel@BM2LTSR66RBin:/media/hd/home/reel$ ls -al /media
total 16
drwxrwxrwt  9 root root  180 Feb 18 21:21 .
drwxr-xr-x 23 root root 4096 Feb 16 16:32 ..
drwxrwsr-x  2 root root  120 Feb 18 20:02 configs
d---------  2 root root   40 Feb 18 20:02 dvd
drwxrwsrwx 13 root root 4096 Feb 15 12:39 hd
drwxr-xr-x 43 root root 4096 Feb  1 11:02 hd1
drwxr-xr-x  8 root root   48 Jul 10  2014 hd2
drwxr-xr-x  8 root root   48 Jul 18  2014 hd3
drwxrwsr-x  2 root root  120 Feb 18 21:21 reel
reel@BM2LTSR66RBin:/media/hd/home/reel$

[SteveRiley]

I misread -- that ls -ld won't tell us what's inside the directory. What's the output of ls -al /media?

[SecretCode]

It has no subdirectories according to ls -ld /media.

How do you deduce that? I'd say it has 8 hard links therefore 6 subdirectories.

Not that this makes the puzzle any simpler.

[SteveRiley]

So. /media is in RAM (because it's a tmpfs). It has no subdirectories according to ls -ld /media. Yet according to mount three devices are mounted to subdirectories in /media.

What is this I don't even

Don`t really want to go that route.

If you want a Kubuntu that is in a predictable state and that we can help you with, I don't think you have an alternate option. That other distro deviates so much from normal Ubuntu that trying to shoehorn Kubuntu onto it is likely to be fraught with problems.

[kdeuser]

@SecretCode,

Readout of mount right after boot :

reel@BM2LTSR66RBin:/media/hd/home/reel$ mount
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
tmpfs on /media type tmpfs (rw,relatime,size=10240k)
/dev/sda4 on /media/hd type ext4 (rw,_netdev)
/dev/sdb1 on /media/hd1 type jfs (rw,_netdev)
/dev/sdd1 on /media/hd2 type jfs (rw,_netdev)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw)
systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd)
nfsd on /proc/fs/nfsd type nfsd (rw)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=reel)

Readout from /etc/fstab :

reel@BM2LTSR66RBin:/media/hd/home/reel$ cat /etc/fstab
# /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>
proc            /proc           proc    nodev,noexec,nosuid 0       0

# / was on /dev/sda1 during installation
/dev/sda1 	/               ext4    errors=remount-ro 0       1

# swap was on /dev/sda3 during installation
/dev/sda3	 none            swap    sw              0       0
UUID=eb459c80-7168-4749-aab3-36ae9d4eb6e8	/media/hd	auto	defaults,nofail	0	2
UUID=c36f1885-62ea-4fcc-9570-1cf15d96bc3a	/media/hd1	auto	defaults,nofail	0	2
UUID=77dcd436-432a-43d1-8a74-789bb27a672e	/media/hd2	auto	defaults,nofail	0	2

Readout from ls -ld /media :

reel@BM2LTSR66RBin:/media/hd/home/reel$ ls -ld /media
drwxrwxrwt 8 root root 160 Feb 18 20:03 /media

@oshunluvr,

"An alternate solution would be to mount all the HDs to subfolders of /mnt then use bind mounts via a login script to mount them to /media. What a PITA though."

If no solution is found , this seems feasible but would need some guidance.

@SteveRiley,

"rebuild with Kubuntu as the base (to obtain a standard Ubuntu setup) and then install the multimedia bits on top of that. Reverse engineering this weird build so that Kubuntu will run sounds brittle and will likely be a continual source of problems."

Don`t really want to go that route.

[SteveRiley]

If I remember correctly, kdeuser is not using Kubuntu. He's using Kodi or XMBC or something with Kubuntu-desktop installed on top of it. No doubt the /media as tmpfs originates there. I'd start with XSession scripts and see what's there.

Or, as suggested in another thread I read after posting last night, rebuild with Kubuntu as the base (to obtain a standard Ubuntu setup) and then install the multimedia bits on top of that. Reverse engineering this weird build so that Kubuntu will run sounds brittle and will likely be a continual source of problems.

[oshunluvr]

I'm sure it can be solved - but from what you've posted it's not obvious where this is being triggered.

Can you do a fresh boot, and before mounting anything or indeed running anything manually, copy and post the output of mount?
And maybe the /etc/fstab as it is straight after booting.
And output of ls -ld /media

If mount shows /media as tmpfs right from boot time I'm guessing we might have to go digging through startup scripts.

If I remember correctly, kdeuser is not using Kubuntu. He's using Kodi or XMBC or something with Kubuntu-desktop installed on top of it. No doubt the /media as tmpfs originates there. I'd start with XSession scripts and see what's there.

An alternate solution would be to mount all the HDs to subfolders of /mnt then use bind mounts via a login script to mount them to /media. What a PITA though.

[SecretCode]

I'm sure it can be solved - but from what you've posted it's not obvious where this is being triggered.

Can you do a fresh boot, and before mounting anything or indeed running anything manually, copy and post the output of mount?
And maybe the /etc/fstab as it is straight after booting.
And output of ls -ld /media

If mount shows /media as tmpfs right from boot time I'm guessing we might have to go digging through startup scripts.

[kdeuser]

how are you editing the file ,,,,,,,,,,,do you save and close ,,,,,,,,,then reopen and see if your edit took .

strange

and yes @SecretCode ,,,, that seems strange .

VINNY

The answer is yes, i check to see by closing fstab and then reopening .

The edit is there , on reboot it is not.

@SteveRiley,

Can this /media as tmps anomaly be solved ?

[SteveRiley]

Wait ... you have tmpfs mounted on /run and /media? That seems very very odd. Does this seem normal to anyone else?

Mounting /media as tmpfs explains why none of the subdirectories inside it persist across reboots. /media should be a standard subdirectory in /.

[vinnywright]

@ VINNY,

Doesn`t work , again the line gets thrown out at boot.

how are you editing the file ,,,,,,,,,,,do you save and close ,,,,,,,,,then reopen and see if your edit took .

strange

and yes @SecretCode ,,,, that seems strange .

VINNY

[SecretCode]

Print of df -h :

reel@BM2LTSR66RBin:/media/hd/home/reel$ df -h 
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1        13G  8.4G  3.7G  70% /
none            4.0K     0  4.0K   0% /sys/fs/cgroup
udev            2.0G   12K  2.0G   1% /dev
tmpfs           406M  1.4M  404M   1% /run
none            5.0M     0  5.0M   0% /run/lock
none            2.0G  148K  2.0G   1% /run/shm
none            100M   28K  100M   1% /run/user
/dev/sda4       445G  4.8G  417G   2% /media/hd
/dev/sdd1       1.9T  1.8T   49G  98% /media/hd1
/dev/sdb1       1.9T  1.3T  557G  71% /media/hd2
tmpfs            10M     0   10M   0% /media
/dev/sdc1       2.8T  2.4T  385G  87% /media/hd3

Wait ... you have tmpfs mounted on /run and /media? That seems very very odd. Does this seem normal to anyone else?