Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #179340 > unrolled thread

Encrypted flash drives

Back to article view | Back to linux.debian.user

Contents

  Encrypted flash drives Mark Fletcher <mark27q1@gmail.com> - 2017-03-26 11:10 +0200
    Re: Encrypted flash drives Nicolas George <george@nsup.org> - 2017-03-26 11:20 +0200
      Re: Encrypted flash drives Mark Fletcher <mark27q1@gmail.com> - 2017-03-26 11:30 +0200
        Re: Encrypted flash drives Nicolas George <george@nsup.org> - 2017-03-26 11:40 +0200
          Re: Encrypted flash drives Mark Fletcher <mark27q1@gmail.com> - 2017-03-26 12:00 +0200
            Re: Encrypted flash drives <tomas@tuxteam.de> - 2017-03-26 12:10 +0200
            Re: Encrypted flash drives Nicolas George <george@nsup.org> - 2017-03-26 12:30 +0200
              Re: Encrypted flash drives Mark Fletcher <mark27q1@gmail.com> - 2017-03-27 01:40 +0200
                Re: Encrypted flash drives <tomas@tuxteam.de> - 2017-03-27 10:10 +0200
                  [off topic] Re: Encrypted flash drives "Thomas Schmitt" <scdbackup@gmx.net> - 2017-03-27 10:30 +0200
                    Re: [off topic] Re: Encrypted flash drives <tomas@tuxteam.de> - 2017-03-27 11:50 +0200
                      [off topic] Re: Encrypted flash drives "Thomas Schmitt" <scdbackup@gmx.net> - 2017-03-27 13:00 +0200
                        Re: [off topic] Re: Encrypted flash drives kAt <giathnygeia@openmailbox.org> - 2017-03-28 00:30 +0200
                          Re: [off topic] Re: Encrypted flash drives "Thomas Schmitt" <scdbackup@gmx.net> - 2017-03-28 12:50 +0200
                            Re: [way off topic] Re: Encrypted flash drives David Wright <deblis@lionunicorn.co.uk> - 2017-03-28 16:10 +0200
                  Re: Encrypted flash drives Mark Fletcher <mark27q1@gmail.com> - 2017-03-27 16:10 +0200
                    Re: Encrypted flash drives <tomas@tuxteam.de> - 2017-03-27 16:40 +0200
                  Re: Encrypted flash drives Mark Fletcher <mark27q1@gmail.com> - 2017-03-27 17:00 +0200
                    Re: Encrypted flash drives <tomas@tuxteam.de> - 2017-03-27 21:40 +0200
                      Re: Encrypted flash drives Mark Fletcher <mark27q1@gmail.com> - 2017-04-03 14:10 +0200
                        Re: Encrypted flash drives <tomas@tuxteam.de> - 2017-04-03 15:10 +0200
                          Re: Encrypted flash drives Mark Fletcher <mark27q1@gmail.com> - 2017-05-01 09:50 +0200
                        Re: Encrypted flash drives Cindy-Sue Causey <butterflybytes@gmail.com> - 2017-04-03 18:40 +0200

Page 1 of 2  [1] 2  Next page →

#179340 — Encrypted flash drives

Hello the list!

This is a problem of repairing an encrypted USB drive that isn't playing 
nice with Gnome after setup although it is basically working and no data 
has been lost.

Today I opened my desk drawer and found the USB flash drive I have used 
to back up my GPG private keys, revokation keys etc had _something 
sticky_ growing on it. Not nice. And bizarre because nothing around it 
in the drawer was affected.

So I bought 2 identical relatively small new USB drives, with the intent 
of copying the content of the 
rapidly-becoming-unfit-for-human-consumption drive onto both of them, 
and keeping one offsite. And this seemed like a great time to make my 
first experiment with volume encryption.

I'm running Jessie and Gnome on the desktop, so my machine's default 
behaviour when I plug in a flash drive is to pop up a, erm, pop-up 
asking if I want to open the drive in Files (nautilus) or eject it. I 
clicked Open with Files. Next I right-clicked on the drive in the left 
pane and chose "Format..." To my rather pleasant surprise support for 
encrypting the volume was right there in the Format dialog. I proceeded 
to provide a label and passphrase for the drive and went through the 
confirmation stages warning me I was about to lose data and so on.

Then, nothing apparently happened. Turns out it was creating the ext4 
file system in the just-created encypted volume, but it didn't _say_ 
that, and I thought it was done, and had unmounted the volume, so I 
removed it. D'oh!

I've filed a bug on Files for that because although I was stupid to 
remove the device without doing SOMETHING to check if it was still being 
used, the fact is Files gave me zero feedback that it was doing 
anything.

After this Files couldn't do anything with the drive so I dropped to the 
command line. There I executed the following as root:

cryptsetup luksFormat /dev/sdg1

(for 'twas /dev/sdg1 where the now-messed-up drive was). This completed 
successfully, asking me for the passphrase on the way. Then:

cryptsetup luksOpen /dev/sdg1 SECRETKEY1

Which also completed successfully. Finally:

mkfs.ext4 /dev/mapper/SECRETKEY1

which took a bit longer to complete than I expected, but eventually 
completed successfully. That was what tipped me off to what I had done 
wrong in the first place in Files.

After this, I ejected the device, and plugged it back in. Gnome does not 
respond, but if you manually start Files, you can see "8.1GB Encypted" 
in the left hand pane. Clicking on that triggers the request to supply 
the password and on correctly supplying the password you have access to 
the device. However, can't write to it, and I have to drop to the 
command line and su to root before I can do so.

I then used Files to format and encrypt the second device, and this time 
was more patient to wait until it was finished, at which point the 
device was mounted with the label I'd chosen and I could safely eject it 
the normal way. After this, re-inserting the second device is 
automatically detected by Gnome and I am prompted for the password, and 
on supplying it, I get the usual "Open in Files or Eject" prompt and 
everything operates after that as if it were not encrypted, including 
non-root writes.

With both drives mounted, I compared the /etc/mtab entries for the two 
and this is what I found:

/dev/mapper/luks-378947be-2ef0-452e-8d80-04064aec5bc7 /media/mark/138b9d59-b0cd-49cc-a738-8fecea5f0035 ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
(that's the first drive, that I used the command line to fix after 
messing it up in Files)

/dev/mapper/luks-0dfd326a-10ea-4f1f-8ca3-4ab492ebd62e /media/mark/SECRETKEY2 ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
(That's the second one that everything works properly for).

>From here, how can I fix the first one to play nice? (Wiping it and 
re-formating from scratch is an option, but I figure I will learn more 
from fixing it)

Thanks!

Mark

[toc] | [next] | [standalone]

#179341

[Multipart message — attachments visible in raw view] — view raw

Le sextidi 6 germinal, an CCXXV, Mark Fletcher a écrit :
>	      However, can't write to it, and I have to drop to the 
> command line and su to root before I can do so.

Obvious guess: it has nothing to do with encryption and only to do with
permissions on the root directory. So I would suggest: chmod or chown.

Regards,

-- 
  Nicolas George

[toc] | [prev] | [next] | [standalone]

#179343

On Sun, Mar 26, 2017 at 11:14:02AM +0200, Nicolas George wrote:
> Le sextidi 6 germinal, an CCXXV, Mark Fletcher a écrit :
> >	      However, can't write to it, and I have to drop to the 
> > command line and su to root before I can do so.
> 
> Obvious guess: it has nothing to do with encryption and only to do with
> permissions on the root directory. So I would suggest: chmod or chown.
> 
Yeah I guess so, but chmod or chown of WHAT, though? Since the device 
only exists when the drive is plugged in, and I would guess making 
ownership changes to that would only last until the drive was ejected...

Also, for some reason I can't reply-list to your mails, so I'm afraid 
you are going to get a direct copy of this message whether you want it 
or not. Apologies in advance, not sure what I can do about that. You've 
got something unusual in your mail headers that is confusing mutt...

Mark

[toc] | [prev] | [next] | [standalone]

#179344

[Multipart message — attachments visible in raw view] — view raw

Le sextidi 6 germinal, an CCXXV, Mark Fletcher a écrit :
> Yeah I guess so, but chmod or chown of WHAT, though?

Of the root directory of the drive, i.e. the directory where it is
mounted: chown you /media/mark/drive while it is mounted.

> Also, for some reason I can't reply-list to your mails, so I'm afraid 
> you are going to get a direct copy of this message whether you want it 
> or not. Apologies in advance, not sure what I can do about that. You've 
> got something unusual in your mail headers that is confusing mutt...

No apologies required, you did the right thing automatically.
"reply-list" is a stupid design that requires human attention for
something that can, and therefore should, be automated. For some reason
that I will not hazard to discuss here, this mailing-list is not
configured to set the headers that would actually automate it for
everybody. Instead, I have configured my own client to set it.

Regards,

-- 
  Nicolas George

[toc] | [prev] | [next] | [standalone]

#179348

On Sun, Mar 26, 2017 at 11:31:19AM +0200, Nicolas George wrote:
> Le sextidi 6 germinal, an CCXXV, Mark Fletcher a écrit :
> > Yeah I guess so, but chmod or chown of WHAT, though?
> 
> Of the root directory of the drive, i.e. the directory where it is
> mounted: chown you /media/mark/drive while it is mounted.
> 
Thanks for the quick reply. I've got mixed success to report from that.

When I plug in the device, open Files manually, click on "8.1GB 
Encrypted" and supply the passphrase, it mounts the drive at 
/media/mark/really-long-string-of-letters-and-numbers

That was owned by root. I did chown mark:mark <same really long string 
of letters and numbers> and verified the ownership had changed. 
Everything inside that directory, ie on the drive, is already owned by 
user mark. And to confirm, I am logged into Gnome as mark.

After executing that chown command and before ejecting the drive, the 
"New Folder" etc commands on the Files right-click menu were enabled, 
where previously they had been disabled, suggesting Files now felt it 
could write to the disk.

I ejected the volume. The really long string of letters and numbers in 
/media/mark disappeared, as expected.

I removed the drive and re-inserted it. No response from Gnome. I fired 
up Files again manually, and saw "8.1GB Encryted" as before. Clicking on 
that and supplying the passphrase mounted the device, as before. Again 
it is mounted in /media/mark/blahdiblahdiblah (this time it was 
/media/mark/138b9d59-b0cd-49cc-a738-8fecea5f0035 to be precise, I am not 
sure if that is identical to before but suspect so).

That directory in /media/mark was owned by... mark this time! BUT, Files 
has the New Folder command greyed out, indicating it does NOT think it 
can write to this device. And I cannot paste anything into the device's 
pane in Files. BUT AGAIN, at the command line, as mark, I went into 
/media/mark/138b9d59-b0cd-49cc-a738-8fecea5f0035 and typed touch 
test.txt and lo and behold the file was created. So now I have a 
confused Files / Nautilus on top of everything else...

So perms are fixed in fact but not according to the Files application. 
And detection and auto-prompting for the passphrase on connect is not 
working for this device but is working for the identical one I formatted 
properly with Files. I'd like to un-confuse Files and get autodetection 
working.

Mark

[toc] | [prev] | [next] | [standalone]

#179350

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, Mar 26, 2017 at 06:53:15PM +0900, Mark Fletcher wrote:

[...]

> So perms are fixed in fact but not according to the Files application. 
> And detection and auto-prompting for the passphrase on connect is not 
> working for this device but is working for the identical one I formatted 
> properly with Files. I'd like to un-confuse Files and get autodetection 
> working.

I think the ghost working in the background is udev: it gets notified
by the kernel of something happening (in this case of the just decrypted
volume "appearing", after you successfully entered your passphrase) and
arranges for the rest to happen.

In your case, having a desktop-heavy environment, I'd guess [1] that
udisks is the part actually concerned with managing disks, wrapping
things thickly in DBus and other "amenities". So I'd look for some
place where udisks is configured.

[1] I'm a desktop Luddite, as many might know around here :-)

regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAljXkc8ACgkQBcgs9XrR2kYOBACfdYPHmn9NysYzdfkOorHFcJqU
tDYAnA/ksFD7LUpuXy+fbL1AMhowWMiT
=BiGp
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#179352

[Multipart message — attachments visible in raw view] — view raw

Le sextidi 6 germinal, an CCXXV, Mark Fletcher a écrit :
> That directory in /media/mark was owned by... mark this time! BUT, Files 
> has the New Folder command greyed out, indicating it does NOT think it 
> can write to this device. And I cannot paste anything into the device's 
> pane in Files. BUT AGAIN, at the command line, as mark, I went into 
> /media/mark/138b9d59-b0cd-49cc-a738-8fecea5f0035 and typed touch 
> test.txt and lo and behold the file was created. So now I have a 
> confused Files / Nautilus on top of everything else...

Well, I am sorry to say that the extents of the advice I can give on
handling troubles with Gnome or other desktop environments is "apt-get
purge gnome nautilus; apt-get install fvwm zsh". I can still suggest two
basic generic things to test: first, look carefully at the differences,
in ownership, permissions, etc., of the mounted filesystems. Second, try
with a clean account to see if the keys still show different behaviours
(and if that fails, try with a brand new install).

Hope this helps.

Regards,

-- 
  Nicolas George

[toc] | [prev] | [next] | [standalone]

#179416

On Sun, Mar 26, 2017 at 12:28:33PM +0200, Nicolas George wrote:
> 
> Well, I am sorry to say that the extents of the advice I can give on
> handling troubles with Gnome or other desktop environments is "apt-get
> purge gnome nautilus; apt-get install fvwm zsh". I can still suggest two
> basic generic things to test: first, look carefully at the differences,
> in ownership, permissions, etc., of the mounted filesystems. Second, try
> with a clean account to see if the keys still show different behaviours
> (and if that fails, try with a brand new install).
> 
Thanks, I appreciate the advice. I will check those things. But I feel 
that still leaves the question of why there is no reaction to the 
initial insert of the drive in the "semi-broken" case, whereas with the 
other there is an immediate reaction in that the screen pops up asking 
me to enter the passphrase. Obviously this moment is before there is a 
mounted filesystem to look at.

Tomas has tried to give me pointers on that but I'm afraid I don't 
understand where to take that. Is there any chance someone who isn't a 
self-proclaimed "desktop luddite" could comment?

At this point this is a "interesting, wonder what is wrong with this" as 
opposed to "oh god I'm dying" thing, but I'd appreciate pointers in 
figuring out how to resolve it. I think it boils down to differences 
between the commands I executed on the command line and what Files is 
doing in the background if you use the GUI. It doesn't sit well with me, 
as it may with many others, that the GUI does a better job that I can't 
replicate on the command line -- means there is something happening that 
I don't understand.

Thanks

Mark

[toc] | [prev] | [next] | [standalone]

#179426

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Mar 27, 2017 at 08:31:45AM +0900, Mark Fletcher wrote:

[...]

> Tomas has tried to give me pointers on that but I'm afraid I don't 
> understand where to take that. Is there any chance someone who isn't a 
> self-proclaimed "desktop luddite" could comment?

There *must* be some place in your shiny desktop environment "disks"
or something like that where you configure media "known" to your
desktop environment.

Insert your "semi-correct" disk and try to enter the labyrinth
through "properties".

Don't forget Ariadne and the yarn, and give my greetings to the
Minotaur ;-)

regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAljYxxMACgkQBcgs9XrR2ka+5gCdHbbHh392pSEr0Zz4RYCoPbrL
GAkAn2cLXEFXXFt3rOpZZMtNEFSGhMZX
=c9VW
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#179427 — [off topic] Re: Encrypted flash drives

Hi,

tomás wrote:
> Don't forget Ariadne and the yarn, and give my greetings to the
> Minotaur ;-)

Minotaur XP was replaced by the incompatible cyclops-scylla 2.0.
You will have to replace your old Theseus desktop by the new
Oddity Experiencer which gives the look-and-feel of a smartphone
and comes with its own wooden horse emulator.


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#179429 — Re: [off topic] Re: Encrypted flash drives

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Mar 27, 2017 at 10:24:47AM +0200, Thomas Schmitt wrote:
> Hi,
> 
> tomás wrote:
> > Don't forget Ariadne and the yarn, and give my greetings to the
> > Minotaur ;-)
> 
> Minotaur XP was replaced by the incompatible cyclops-scylla 2.0.
> You will have to replace your old Theseus desktop by the new
> Oddity Experiencer which gives the look-and-feel of a smartphone
> and comes with its own wooden horse emulator.

Not forget the Daedalus framework, supporting the Icarus client.
Beware of the Sun!

> Have a nice day :)

You often *make* my day, Thomas :-)

regards
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAljY3lMACgkQBcgs9XrR2kbm9QCfUg/smKZn/OpDbDC0Mot7xVRv
qhUAnja2uL/VC4by9Cbd76FG45nRp0Wz
=B3BZ
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#179431 — [off topic] Re: Encrypted flash drives

Hi,

tomás wrote:
> Beware of the Sun!

Says the Oracle ...

> You often *make* my day, Thomas :-)

Just wait until you read my alternative facts about the raison d'être
of systemd.


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#179502 — Re: [off topic] Re: Encrypted flash drives

Thomas Schmitt:
> Hi,
> 
> tomás wrote:
>> Beware of the Sun!
> 
> Says the Oracle ...
> 
>> You often *make* my day, Thomas :-)
> 
> Just wait until you read my alternative facts about the raison d'être
> of systemd.

I want to read it
Except for the last two lines

> Have a nice day :)
> Thomas

U2

[toc] | [prev] | [next] | [standalone]

#179518 — Re: [off topic] Re: Encrypted flash drives

Hi,

i wrote:
> > Just wait until you read my alternative facts about the raison d'être
> > of systemd.

kAt wrote:
> I want to read it

If you test

  http://scdbackup.webframe.org/make_isombr_part

as described in
  https://lists.debian.org/debian-user/2017/03/msg01215.html
on your USB stick and afterwards check by some partition editors,
then i will try to compile an exclusive report about the true
origin of systemd.


In exchange for a physically plausible explanation of a light mill,
i would make up a story about why a mirror exchanges left and right
but not up and down.
(Crooke radiometer: turns wrong way around, needs thin gas filling
 and temperature gradient between wheel and glass to work, gaps are
 much too large for any thermal transpiration, ...)


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#179530 — Re: [way off topic] Re: Encrypted flash drives

On Tue 28 Mar 2017 at 12:46:18 (+0200), Thomas Schmitt wrote:
> Hi,
> 
> i wrote:
> > > Just wait until you read my alternative facts about the raison d'être
> > > of systemd.
> 
> kAt wrote:
> > I want to read it
> 
> If you test
> 
>   http://scdbackup.webframe.org/make_isombr_part
> 
> as described in
>   https://lists.debian.org/debian-user/2017/03/msg01215.html
> on your USB stick and afterwards check by some partition editors,
> then i will try to compile an exclusive report about the true
> origin of systemd.
> 
> 
> In exchange for a physically plausible explanation of a light mill,
> i would make up a story about why a mirror exchanges left and right
> but not up and down.

When you look in the mirror, it doesn't exchange left and right,
but fore and aft. To make a mirror exchange up and down, lay it
down on the floor.

> (Crooke radiometer: turns wrong way around, needs thin gas filling
>  and temperature gradient between wheel and glass to work, gaps are
>  much too large for any thermal transpiration, ...)

When I was a child, many things in the street were painted black and
white (for the blackout), and I remember feeling how hot the black
parts got in the sun (even in England) compared with the white.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#179460

On Mon, Mar 27, 2017 at 10:02:27AM +0200, tomas@tuxteam.de wrote:
> On Mon, Mar 27, 2017 at 08:31:45AM +0900, Mark Fletcher wrote:
> 
> [...]
> 
> > Tomas has tried to give me pointers on that but I'm afraid I don't 
> > understand where to take that. Is there any chance someone who isn't a 
> > self-proclaimed "desktop luddite" could comment?
> 
> There *must* be some place in your shiny desktop environment "disks"
> or something like that where you configure media "known" to your
> desktop environment.
> 
> Insert your "semi-correct" disk and try to enter the labyrinth
> through "properties".
> 
> Don't forget Ariadne and the yarn, and give my greetings to the
> Minotaur ;-)
> 
I honked my mouse up into the top left corner of the screen, as you do 
in Gnome, and typed "disks" in the search box. And, to quote General 
Melchett, "Well bugger me with a fishfork" if there wasn't an application 
called Disks just waiting for me.

(there was, so no need to... anyway)

It reports that my correctly working disk has a partition type of 83 
(linux) while the partly-broken one reports a partition type of W95 
FAT32 (LBA) -- suggesting it really is in a bit of an old mess after my 
half-assed initial format. I've seen enough -- I'll wipe and re-format 
it, and have patience this time (doing that now).

Mark

[toc] | [prev] | [next] | [standalone]

#179463

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Mar 27, 2017 at 11:01:57PM +0900, Mark Fletcher wrote:
> On Mon, Mar 27, 2017 at 10:02:27AM +0200, tomas@tuxteam.de wrote:
> > On Mon, Mar 27, 2017 at 08:31:45AM +0900, Mark Fletcher wrote:
> > 
> > [...]
> > 
> > > Tomas has tried to give me pointers on that but I'm afraid I don't 
> > > understand where to take that. Is there any chance someone who isn't a 
> > > self-proclaimed "desktop luddite" could comment?
> > 
> > There *must* be some place in your shiny desktop environment "disks"
> > or something like that where you configure media "known" to your
> > desktop environment.
> > 
> > Insert your "semi-correct" disk and try to enter the labyrinth
> > through "properties".
> > 
> > Don't forget Ariadne and the yarn, and give my greetings to the
> > Minotaur ;-)
> > 
> I honked my mouse up into the top left corner of the screen, as you do 
> in Gnome, and typed "disks" in the search box. And, to quote General 
> Melchett, "Well bugger me with a fishfork" if there wasn't an application 
> called Disks just waiting for me.
> 
> (there was, so no need to... anyway)
> 
> It reports that my correctly working disk has a partition type of 83 
> (linux) while the partly-broken one reports a partition type of W95 
> FAT32 (LBA) -- suggesting it really is in a bit of an old mess after my 
> half-assed initial format. I've seen enough -- I'll wipe and re-format 
> it, and have patience this time (doing that now).

Note that you can change the partition type with a partition editor.
It's just the value of a specific byte in the partition table with
no further effects whatsoever (excluding some gullible desktop
environments, but those believe in file endings too, snark, snark ;)

So no need to reformat (not telling you what to do, but if you're
still in investigative mood, this would be a candidate).

Regards
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAljZIiUACgkQBcgs9XrR2kZ30wCfZPljNBzi3J4C/X/IkdB5QoIy
LNAAn1RJwDfpM1f1/zVb/ESwtfLe1VSn
=raQP
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#179466

On Mon, Mar 27, 2017 at 10:02:27AM +0200, tomas@tuxteam.de wrote:
> On Mon, Mar 27, 2017 at 08:31:45AM +0900, Mark Fletcher wrote:
> 
> [...]
> 
> > Tomas has tried to give me pointers on that but I'm afraid I don't 
> > understand where to take that. Is there any chance someone who isn't a 
> > self-proclaimed "desktop luddite" could comment?
> 
> There *must* be some place in your shiny desktop environment "disks"
> or something like that where you configure media "known" to your
> desktop environment.
> 

Update -- it *almost* worked. I now have a clean flash drive with the 
right partition type and file system, which I get the right permissions 
to everywhere, including in Files, when it is mounted. BUT it still is 
not auto-detecting when I plug it in.

In Disks, I notice the following:

Even before I do anything, when neither working nor almost-working 
drives are plugged in, Disks shows me an entry for one of the USB flash 
drives.

If I plug in the almost-working one, it occupies that entry and 
populates it with information. If I plug in the working one, a new item 
is created for it. If I unmount and remove both usb drives, one of the 
two entries disappears and the other one doesn't.

Comparing the two with the drives plugged in and mounted, they look 
extremely similar, except for the following. In the working one: 

Model: hp v250x (1100)
Size: 8.1GB (8,103,395,328 bytes)
Partitioning: Master Boot Record
Serial Number: <serial number>

In the almost-working one:

Model: hp v250w (1100)
Media: --
Size: --
Partitioning: Master Boot Record
Serial Number: <serial number, of course different from above)

I think I need to persuade this entry to disappear when the device is 
not plugged in, then I suspect I will be good.

Any thoughts where this information, which shows even when the 
almost-working drive is not plugged in, could be stored, and what would 
be a safe way to get rid of it? (Please don't say "reboot", this is 
Linux, should be a way to clean up without rebooting)

Thanks

Mark

[toc] | [prev] | [next] | [standalone]

#179492

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Mar 27, 2017 at 11:58:51PM +0900, Mark Fletcher wrote:
> On Mon, Mar 27, 2017 at 10:02:27AM +0200, tomas@tuxteam.de wrote:
> > On Mon, Mar 27, 2017 at 08:31:45AM +0900, Mark Fletcher wrote:
> > 
> > [...]
> > 
> > > Tomas has tried to give me pointers on that but I'm afraid I don't 
> > > understand where to take that. Is there any chance someone who isn't a 
> > > self-proclaimed "desktop luddite" could comment?
> > 
> > There *must* be some place in your shiny desktop environment "disks"
> > or something like that where you configure media "known" to your
> > desktop environment.
> > 
> 
> Update -- it *almost* worked [...]

This looks bizarre. I think I must leave that to the DE gurus. I guess
it has to do with udisks (I think in its current incarnation it's
called "udisks2"), but it's beyond my depth.

Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAljZaNEACgkQBcgs9XrR2kZp+ACfcmZDwTnVrWYQZQMd4k2Bl8jI
L/AAn3eE86fTZ/VybNOscLRQ9APoGMT7
=9sJM
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#179728

On Mon, Mar 27, 2017 at 09:32:33PM +0200, tomas@tuxteam.de wrote:
> On Mon, Mar 27, 2017 at 11:58:51PM +0900, Mark Fletcher wrote:
> > On Mon, Mar 27, 2017 at 10:02:27AM +0200, tomas@tuxteam.de wrote:
> > > On Mon, Mar 27, 2017 at 08:31:45AM +0900, Mark Fletcher wrote:
> > > 
> > > [...]
> > > 
> > > > Tomas has tried to give me pointers on that but I'm afraid I don't 
> > > > understand where to take that. Is there any chance someone who isn't a 
> > > > self-proclaimed "desktop luddite" could comment?
> > > 
> > > There *must* be some place in your shiny desktop environment "disks"
> > > or something like that where you configure media "known" to your
> > > desktop environment.
> > > 
> > 
> > Update -- it *almost* worked [...]
> 
> This looks bizarre. I think I must leave that to the DE gurus. I guess
> it has to do with udisks (I think in its current incarnation it's
> called "udisks2"), but it's beyond my depth.
> 

Any way to reset udev? (in a way that doesn't nuke the system and 
require a reboot anyway)

I'm still trying to find a way to make that ghost disk disappear. I am 
fairly sure a reboot will sort it but solving the problem without 
understanding it is something I only do when there is a good reason, 
like some needed service is compromised or something. Not the case here.

Mark

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web