I misread -- that ls -ld won't tell us what's inside the directory. What's the output of ls -al /media?
-
-
@SteveRiley,
Output of ls -al :
Code: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$
Comment
-
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.
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.Code:findmnt cd ~ sudo umount /media findmnt ls -al / ls -al /media
Comment
-
@SteveRiley,
Requested data :
Code: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:~$Comment
-
Hm. findmnt should be showing your entire mount hierarchy, like this:
I have no clue why it shows only one line for you. Try findmnt -ACode: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
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?Comment
-
Readouts :
Code:reel@BM2LTSR66RBin:/media/hd/home/reel$ findmnt -A findmnt: invalid option -- 'A'
Code:reel@BM2LTSR66RBin:/media/hd/home/reel$ fuser -vm /media USER PID ACCESS COMMAND /media: root kernel mount /media reel@BM2LTSR66RBin:/media/hd/home/reel$Comment
-
Wow, whatever version of Ubuntu this distro uses is weird... -A is normally allowed.
My bad on the fuser. It should be sudo fuser -vm /mediaLast edited by SteveRiley; Feb 22, 2015, 12:50 AM.Comment
-
@SteveRiley,
Output of sudo fuser -vm /media ;
Code:reel@BM2LTSR66RBin:/media/hd/home/reel$ sudo fuser -vm /media [sudo] password for reel: USER PID ACCESS COMMAND /media: root kernel mount /media reel@BM2LTSR66RBin:/media/hd/home/reel$Comment
-
Then I am flummoxed. Note that the access type is simply MOUNT. No process appears to have open files. The umount should work.
This distro you're running is very nonstandard.Comment
-
There seems to be several other filesystems mounted under media, you can't unmount /media from under (or rather over) them...the user's $HOME seems to be there too <-- "reel@BM2LTSR66RBin:/media/hd/home/reel$"Originally posted by SteveRiley View Post
It looks like an embedded installation (or semi-embedded), some of them have quite complex set-ups (sometimes for good reasons, other times not)...it can be quite a tedious task to figure one out without documentation, especially remotely via a forum).Originally posted by SteveRiley View PostComment
-
You know, you're right... I'm so wrapped around this tmpfs thing and the totally weird outputs from fuser that I overlooked that.
I'm not sure there's much value in trying to deconstruct this system any longer. I'm fairly confident in stating that trying to get Kubuntu running on it will be a lost cause, because so much of the underlying configuration deviates from what Kubuntu expects. Kubuntu expects a mostly standard Ubuntu base. This distro is definitely not that.Comment
-
I've said that on this thread -> https://www.kubuntuforums.net/showth...l=1#post366559Originally posted by SteveRiley View Post
If kdeuser wasn't stubborn he's have had kubuntu installed on his multimedia machine installed all the dvb stuff and he could have watched his video/tv on the device by now.Comment
-
Mine's Utopic. What's yours?
Code:steve@t520:~$ [B]apt-cache policy mount[/B] mount: Installed: 2.25.1-3ubuntu4 Candidate: 2.25.1-3ubuntu4 Version table: *** 2.25.1-3ubuntu4 0 500 http://mirror.pnl.gov/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status steve@t520:~$ [B]findmnt --help | grep -- -A[/B] -A, --all disable all built-in filters, print all filesystemsComment
-
Trusty right now, Precise earlier. Still no -A option here. And I think kdeuser's custom build is based on Trusty, so that would explain why the same error message appears there.
Code:$ apt-cache policy mount mount: Installed: 2.20.1-5.1ubuntu20.3 Candidate: 2.20.1-5.1ubuntu20.3 Version table: *** 2.20.1-5.1ubuntu20.3 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.20.1-5.1ubuntu20 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main amd64 PackagesLast edited by SecretCode; Feb 19, 2015, 04:25 PM.I'd rather be locked out than locked in.Comment
Comment