Re: [PLUG] Challenges in the Troubleshooting Process

2019-10-21 Thread Ben Koenig
One of the problems you were having were these ephemeral mount folders in /media. It was causing a lot of general confusion by duplicating your mountpoints. You should really consider moving your lines in fstab from /media to /mnt. This would clear up issues with things not working as expected. Fro

Re: [PLUG] Challenges in the Troubleshooting Process

2019-10-21 Thread Tomas Kuchta
Good point with the labels John, there are other ways to skin the cat. You can give timeout option on your mount line to avoid excessive boot times when your drive is not attached. Something longer than it takes to wake up your drives. On Mon, Oct 21, 2019, 21:02 John Jason Jordan wrote: > On M

Re: [PLUG] Challenges in the Troubleshooting Process

2019-10-21 Thread John Jason Jordan
On Mon, 21 Oct 2019 16:34:48 -0700 wes dijo: >/media is managed by the GUI. the GUI reads the volume name when it's >connected, and mounts it on /media/[username]/[volume name]. If there >is already something there, you will end up with a second filesystem >mounted on the same mount point. A lon

Re: [PLUG] Challenges in the Troubleshooting Process

2019-10-21 Thread Tomas Kuchta
The thing about /dev/sd[a-z][0-9] and older ata /dev/hd[a-z][0-9] as well as NVMe and USB device names is that they are controller, port and/or plug-in order dependent. If you have bunch of drives connected to any of these interfaces at boot time. They are enumerated by controller/port/partition o

Re: [PLUG] Challenges in the Troubleshooting Process

2019-10-21 Thread wes
/media is managed by the GUI. the GUI reads the volume name when it's connected, and mounts it on /media/[username]/[volume name]. If there is already something there, you will end up with a second filesystem mounted on the same mount point. It's not a problem until it is. -wes On Mon, Oct 2

Re: [PLUG] Challenges in the Troubleshooting Process

2019-10-21 Thread John Jason Jordan
On Mon, 21 Oct 2019 08:45:20 -0700 Ben Koenig dijo: >There is a sequence of steps used to troubleshoot a given issue. >Sometimes when running through these steps, you may appear to have >"fixed" the problem, when all you did was poke it to do what you >wanted. A good example is one of the Ubuntu

[PLUG] Challenges in the Troubleshooting Process

2019-10-21 Thread Ben Koenig
Hopefully it lets me change the subject to start a new conversation. You bring up some interesting points but it's very off topic. On 10/21/19 6:34 AM, Tomas Kuchta wrote: In one of the weekend posts you learned how to obtain disk and partition uuid - is there any technical reason to not use uu