Only Since 19.2

Questions about other topics - please check if your question fits better in another category before posting here
Forum rules
Before you post please read how to get help
Post Reply
mbott001
Level 1
Level 1
Posts: 27
Joined: Thu Feb 07, 2019 8:51 am
Location: EN80nd

Only Since 19.2

Post by mbott001 »

I've been using LM 19.1 for probably close to 6 months without issue. When 19.2 was released, I upgraded. However, once or twice a day I receive the attached message when I try to access the Music partition on my 1TB hard drive.
Question.png
To access the Music partition, I have to unmount the partition and then remount it. The dismount involves this step.
Authorize.png
Again, did not encounter this situation at any time with 19.1.

Any ideas as to what is happening here? I am the only user.

--
Mike
User avatar
all41
Level 16
Level 16
Posts: 6424
Joined: Tue Dec 31, 2013 9:12 am
Location: Computer, Car, Cage

Re: Only Since 19.2

Post by all41 »

Hi Mike,
Just to verify, did you do an in-place upgrade from 19.1 using the Update Manager, as opposed to a fresh install?
Light travels faster than sound.
That's why some people appear smart until you hear what they are saying.
User avatar
smurphos
Level 17
Level 17
Posts: 7332
Joined: Fri Sep 05, 2014 12:18 am
Location: Britisher
Contact:

Re: Only Since 19.2

Post by smurphos »

It is an internal drive, or an always connected external drive?

If so consider giving it a permanent mount point under your ownership.

To be able to guide you how to do that we'd need the output of

Code: Select all

blkid
and

Code: Select all

cat /etc/fstab
For custom Nemo actions, useful scripts for the Cinnamon desktop, and Cinnamox themes visit my Github pages.
gm10
Level 20
Level 20
Posts: 10999
Joined: Thu Jun 21, 2018 5:11 pm

Re: Only Since 19.2

Post by gm10 »

smurphos wrote:
Sun Aug 11, 2019 1:48 am
If so consider giving it a permanent mount point under your ownership.

To be able to guide you how to do that we'd need the output of

Code: Select all

blkid
and

Code: Select all

cat /etc/fstab
blkid needs sudo. But personally I find it safer to just go Mint menu > Disks, then
  • select the partition you want to permanently mount
  • click the cogs icon > Edit Mount Options
  • De-select User Session Defaults
  • Check Mount at system startup
User avatar
smurphos
Level 17
Level 17
Posts: 7332
Joined: Fri Sep 05, 2014 12:18 am
Location: Britisher
Contact:

Re: Only Since 19.2

Post by smurphos »

gm10 wrote:
Sun Aug 11, 2019 2:26 am
blkid needs sudo.
:?: I get one extra line of output with sudo blkid vs plain blkid....

Code: Select all

steve@steve-Inspiron-5580:~$ blkid
/dev/nvme0n1p1: UUID="0C7C-3863" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="175a6183-73de-4619-bde3-6e05f074809f"
/dev/nvme0n1p2: UUID="d3abb04b-9d93-4004-a247-eff8481481d3" TYPE="ext4" PARTUUID="62ca4657-31e2-4048-a3cc-d5a289265461"
/dev/nvme0n1p3: UUID="464812ce-bfe2-4aae-8e50-66fc77f13bc2" TYPE="ext4" PARTUUID="caa02f1d-42ff-4a34-b8b3-9b83137107e5"
/dev/nvme0n1p4: UUID="0dd54e55-0107-41e5-9c73-6dff95358456" TYPE="ext4" PARTUUID="9dc173b5-ce11-43db-a725-f5db33a127b0"
/dev/nvme0n1p6: UUID="398e2ad0-3f28-414f-a71e-ea46c9b8a3a0" TYPE="ext4" PARTUUID="f80a24c4-d5fb-4244-ac40-abb7c01e16b4"
/dev/sda1: LABEL="Backup" UUID="7f5c52d4-a3ee-44b1-bbbe-230bdb1e6d13" TYPE="ext4" PARTUUID="6df205b9-01"
/dev/sdb1: LABEL="Timeshift" UUID="62e134d6-6d08-4119-8b02-f3ba9edd7c96" TYPE="ext4" PARTUUID="c6410ccf-01"
/dev/sdb2: UUID="f49f2e58-ee53-4ffe-9448-fc1081cde8b8" TYPE="ext4" PARTUUID="c6410ccf-02"
/dev/sdb3: UUID="c06d5d28-c822-43f6-9d15-b64a72e4b63e" TYPE="ext4" PARTUUID="c6410ccf-03"
steve@steve-Inspiron-5580:~$ sudo blkid
[sudo] password for steve:               
/dev/nvme0n1p1: UUID="0C7C-3863" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="175a6183-73de-4619-bde3-6e05f074809f"
/dev/nvme0n1p2: UUID="d3abb04b-9d93-4004-a247-eff8481481d3" TYPE="ext4" PARTUUID="62ca4657-31e2-4048-a3cc-d5a289265461"
/dev/nvme0n1p3: UUID="464812ce-bfe2-4aae-8e50-66fc77f13bc2" TYPE="ext4" PARTUUID="caa02f1d-42ff-4a34-b8b3-9b83137107e5"
/dev/nvme0n1p4: UUID="0dd54e55-0107-41e5-9c73-6dff95358456" TYPE="ext4" PARTUUID="9dc173b5-ce11-43db-a725-f5db33a127b0"
/dev/nvme0n1p6: UUID="398e2ad0-3f28-414f-a71e-ea46c9b8a3a0" TYPE="ext4" PARTUUID="f80a24c4-d5fb-4244-ac40-abb7c01e16b4"
/dev/sda1: LABEL="Backup" UUID="7f5c52d4-a3ee-44b1-bbbe-230bdb1e6d13" TYPE="ext4" PARTUUID="6df205b9-01"
/dev/sdb1: LABEL="Timeshift" UUID="62e134d6-6d08-4119-8b02-f3ba9edd7c96" TYPE="ext4" PARTUUID="c6410ccf-01"
/dev/sdb2: UUID="f49f2e58-ee53-4ffe-9448-fc1081cde8b8" TYPE="ext4" PARTUUID="c6410ccf-02"
/dev/sdb3: UUID="c06d5d28-c822-43f6-9d15-b64a72e4b63e" TYPE="ext4" PARTUUID="c6410ccf-03"
/dev/nvme0n1: PTUUID="0ab4e6d6-8041-4289-af6f-9b083980164a" PTTYPE="gpt"
For custom Nemo actions, useful scripts for the Cinnamon desktop, and Cinnamox themes visit my Github pages.
gm10
Level 20
Level 20
Posts: 10999
Joined: Thu Jun 21, 2018 5:11 pm

Re: Only Since 19.2

Post by gm10 »

smurphos wrote:
Sun Aug 11, 2019 2:46 am
gm10 wrote:
Sun Aug 11, 2019 2:26 am
blkid needs sudo.
:?: I get one extra line of output with sudo blkid vs plain blkid....
I get zero output without sudo. I just verified in an installed 19.2 VM and zero output there, too. In the live environment I do get /dev/sr0 output but not the loop device unless I add sudo. Interesting that you would get the full thing. I shall have to investigate another day. I know that lsblk -f always works though (and is easier to read).
User avatar
Pjotr
Level 22
Level 22
Posts: 15765
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland)
Contact:

Re: Only Since 19.2

Post by Pjotr »

gm10 wrote:
Sun Aug 11, 2019 2:57 am
smurphos wrote:
Sun Aug 11, 2019 2:46 am
gm10 wrote:
Sun Aug 11, 2019 2:26 am
blkid needs sudo.
:?: I get one extra line of output with sudo blkid vs plain blkid....
I get zero output without sudo. I just verified in an installed 19.2 VM and zero output there, too. In the live environment I do get /dev/sr0 output but not the loop device unless I add sudo. Interesting that you would get the full thing. I shall have to investigate another day. I know that lsblk -f always works though (and is easier to read).
blkid works without sudo for me, as well:

Code: Select all

pjotr@proefbak:~$ blkid
/dev/sda1: UUID="2D4C-7AG1" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="79a8fb59-9b7c-42bd-8404-8d233d34630e"
/dev/sda2: UUID="b0edbd05-2e1b-4a23-65df-4ac7536d6a49" TYPE="ext4" PARTUUID="7427ae27-7ef1-4146-63d8-12f399e32101"
Tip: 10 things to do after installing Linux Mint 20 Ulyana
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
gm10
Level 20
Level 20
Posts: 10999
Joined: Thu Jun 21, 2018 5:11 pm

Re: Only Since 19.2

Post by gm10 »

Pjotr wrote:
Sun Aug 11, 2019 4:49 am
blkid works without sudo for me, as well:
Weird again. Even the manual says that it needs root permissions:
man blkid wrote: It is recommended to use lsblk(8) command to get information about block devices, or lsblk --fs to get an overview of
filesystems, or findmnt(8) to search in already mounted filesystems.
lsblk(8) provides more information, better control on output formatting, easy to use in scripts and it does not
require root permissions to get actual information. blkid reads information directly from devices and for non-
root users it returns cached unverified information. blkid is mostly designed for system services and to test
libblkid functionality.
Some further investigation (or actually the first google result :P) got me to this bug report:
It seems that when run without root, it reads from the cached results in /etc/blkid.tab, which are only populated if blkid was previously run as root. That could explain why it worked for chrissss, if he had previously run as root.
I can confirm that if I run sudo blkid then later blkid calls without sudo will yield a result. But on a freshly booted system I get nothing without sudo, as would be the expected result as per the manual. Maybe you guys ran the elevated form first?
Last edited by gm10 on Sun Aug 11, 2019 5:01 am, edited 1 time in total.
User avatar
Pjotr
Level 22
Level 22
Posts: 15765
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland)
Contact:

Re: Only Since 19.2

Post by Pjotr »

gm10 wrote:
Sun Aug 11, 2019 4:59 am
Maybe you guys ran the elevated form first?
Possibly.... But having read the manual I'll use sudo from now on. :lol:
Tip: 10 things to do after installing Linux Mint 20 Ulyana
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
mbott001
Level 1
Level 1
Posts: 27
Joined: Thu Feb 07, 2019 8:51 am
Location: EN80nd

Re: Only Since 19.2

Post by mbott001 »

all41 wrote:
Sat Aug 10, 2019 11:12 pm
Hi Mike,
Just to verify, did you do an in-place upgrade from 19.1 using the Update Manager, as opposed to a fresh install?
Yes, the Update Manage ran the show.

--
Mike
mbott001
Level 1
Level 1
Posts: 27
Joined: Thu Feb 07, 2019 8:51 am
Location: EN80nd

Re: Only Since 19.2

Post by mbott001 »

gm10 wrote:
Sun Aug 11, 2019 2:26 am

blkid needs sudo. But personally I find it safer to just go Mint menu > Disks, then
  • select the partition you want to permanently mount
  • click the cogs icon > Edit Mount Options
  • De-select User Session Defaults
  • Check Mount at system startup
I'll give this a go, thanks!

--
Mike
jglen490
Level 5
Level 5
Posts: 999
Joined: Sat Jul 15, 2017 9:57 pm

Re: Only Since 19.2

Post by jglen490 »

Respect sudo, but do not fear it.

Do some reading on the subject!
I feel more like I do than I did when I got here.
Toshiba A135-S2386, Intel T2080, ATI Radeon® Xpress 200M Chipset, 2GB RAM, 500GB
User avatar
smurphos
Level 17
Level 17
Posts: 7332
Joined: Fri Sep 05, 2014 12:18 am
Location: Britisher
Contact:

Re: Only Since 19.2

Post by smurphos »

gm10 wrote:
Sun Aug 11, 2019 4:59 am
But on a freshly booted system I get nothing without sudo, as would be the expected result as per the manual. Maybe you guys ran the elevated form first?
Mmm - still works for me without sudo on a freshly booted system.

From a recently installed vbox 19.2 - sudo blkid has never been run.

Code: Select all

steve@steve-VirtualBox:~$ blkid
/dev/sda1: UUID="d6347646-74b5-48c5-969f-fe2cd7797857" TYPE="ext4" PARTUUID="5cb85aec-01"
steve@steve-VirtualBox:~$ history | grep blkid
   12  blkid
   13  history | grep blkid

Code: Select all

steve@steve-VirtualBox:/run/blkid$ ls -l
total 4
-rw-r--r-- 1 root root 146 Aug 15 07:01 blkid.tab
Maybe something to do with groups is giving access?

Code: Select all

steve@steve-VirtualBox:/run/blkid$ groups
steve adm cdrom sudo dip plugdev lpadmin sambashare vboxsf
Anyway we have now officially hijacked the thread....
For custom Nemo actions, useful scripts for the Cinnamon desktop, and Cinnamox themes visit my Github pages.
Post Reply

Return to “Other topics”