Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

Feeling amorous, she looked under the sheets and cried, "Oh, no, it's Microsoft!"


computers / alt.os.linux.mint / Re: USB drive read-only after Mint upgrade

SubjectAuthor
* USB drive read-only after Mint upgradeHandsome Jack
+* Re: USB drive read-only after Mint upgradeBig Al
|`- Re: USB drive read-only after Mint upgradeHandsome Jack
+* Re: USB drive read-only after Mint upgradeNic
|+* Re: USB drive read-only after Mint upgradeRonB
||`* Re: USB drive read-only after Mint upgradeHandsome Jack
|| +* Re: USB drive read-only after Mint upgradePaul
|| |`* Re: USB drive read-only after Mint upgradeHandsome Jack
|| | `* Re: USB drive read-only after Mint upgradePaul
|| |  `* Re: USB drive read-only after Mint upgradePaul
|| |   +- Re: USB drive read-only after Mint upgradeHandsome Jack
|| |   `* Re: USB drive read-only after Mint upgradeHandsome Jack
|| |    `* Re: USB drive read-only after Mint upgradePaul
|| |     `* Re: USB drive read-only after Mint upgradeEdmund
|| |      `* Re: USB drive read-only after Mint upgradeNic
|| |       `* Re: USB drive read-only after Mint upgradeEdmund
|| |        `* Re: USB drive read-only after Mint upgradeNic
|| |         `* Re: USB drive read-only after Mint upgradeEdmund
|| |          `- Re: USB drive read-only after Mint upgradeNic
|| `- Re: USB drive read-only after Mint upgradeRonB
|`* Re: USB drive read-only after Mint upgradePaul
| `- Re: USB drive read-only after Mint upgradeHandsome Jack
+- Re: USB drive read-only after Mint upgradeBranimir Maksimovic
`* Re: USB drive read-only after Mint upgradeEdmund
 `* Re: USB drive read-only after Mint upgradeRonB
  `* Re: USB drive read-only after Mint upgradeEdmund
   `- Re: USB drive read-only after Mint upgradewicklowham

Pages:12
Re: USB drive read-only after Mint upgrade

<uhjebe$3dlmm$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6997&group=alt.os.linux.mint#6997

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Bea...@invalid.com (Big Al)
Newsgroups: alt.os.linux.mint
Subject: Re: USB drive read-only after Mint upgrade
Date: Sat, 28 Oct 2023 12:54:05 -0400
Organization: A noiseless patient Spider
Lines: 28
Message-ID: <uhjebe$3dlmm$1@dont-email.me>
References: <uhjdng$3b8vl$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sat, 28 Oct 2023 16:54:06 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="59f8f5db7a0236713e4a31990ad475b7";
logging-data="3593942"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/vh9GvImFY92FDc8qFrMYD9d1vFfS5A1U="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:oo1r5aJ5DqFFLcBumBhzKFUk9ww=
In-Reply-To: <uhjdng$3b8vl$1@dont-email.me>
Content-Language: en-US
 by: Big Al - Sat, 28 Oct 2023 16:54 UTC

On 10/28/23 12:43 PM, this is what Handsome Jack wrote:
> Yesterday I upgraded my Linux Mint 20.3 to 21. 2. One of the unpleasant side-effects is that my almost-permanently-plugged-in USB memory stick, which before the upgrade was readable and writable by me as user, is now read-only. Checking the permissions shows that the owner is now root, and I can't change it by doing "sudo chown ...": that gets "chown: changing ownership of 'USBdrive1': Operation not permitted"
>
>
> Any way I can fix this? The USB stick was originally formatted in Windows so I assume it is fat32.
>
> Doing an fdisk -l gives
>
> Disk /dev/sdc: 1.87 GiB, 2002780160 bytes, 3911680 sectors
> Disk model: USB DISK 2.0
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: dos
> Disk identifier: 0x6f20736b
>
> Device Boot Start End Sectors Size Id Type
> /dev/sdc1 778135908 1919645538 1141509631 544.3G 72 unknown
> /dev/sdc2 168689522 2104717761 1936028240 923.2G 65 Novell Netware 386
> /dev/sdc3 1869881465 3805909656 1936028192 923.2G 79 unknown
> /dev/sdc4 0 3637226495 3637226496 1.7T d unknown

Just curious, was it installed (plugged in) while you did the upgrade?
Is it part of fstab and auto mounts? or do you just plug it in when needed?
--
Linux Mint 21.2 Cinnamon
Al

USB drive read-only after Mint upgrade

<uhjdng$3b8vl$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6998&group=alt.os.linux.mint#6998

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!news.nntp4.net!news5.corell.dk!news.corell.dk!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Jac...@handsome.com (Handsome Jack)
Newsgroups: alt.os.linux.mint
Subject: USB drive read-only after Mint upgrade
Date: Sat, 28 Oct 2023 16:43:31 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 20
Message-ID: <uhjdng$3b8vl$1@dont-email.me>
Injection-Date: Sat, 28 Oct 2023 16:43:31 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="daf35d4205c40360430954d459557486";
logging-data="3515381"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19oooomE/ECSbOJSb40MsgFrjFGIzxTaNw="
User-Agent: tin/2.6.2-20220130 ("Convalmore") (Linux/5.15.0-87-generic (x86_64))
Cancel-Lock: sha1:YWvb1iBfsXjuUbevt1vVCRnBMQ0=
 by: Handsome Jack - Sat, 28 Oct 2023 16:43 UTC

Yesterday I upgraded my Linux Mint 20.3 to 21. 2. One of the unpleasant side-effects is that my almost-permanently-plugged-in USB memory stick, which before the upgrade was readable and writable by me as user, is now read-only. Checking the permissions shows that the owner is now root, and I can't change it by doing "sudo chown ...": that gets "chown: changing ownership of 'USBdrive1': Operation not permitted"

Any way I can fix this? The USB stick was originally formatted in Windows so I assume it is fat32.

Doing an fdisk -l gives

Disk /dev/sdc: 1.87 GiB, 2002780160 bytes, 3911680 sectors
Disk model: USB DISK 2.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6f20736b

Device Boot Start End Sectors Size Id Type
/dev/sdc1 778135908 1919645538 1141509631 544.3G 72 unknown
/dev/sdc2 168689522 2104717761 1936028240 923.2G 65 Novell Netware 386
/dev/sdc3 1869881465 3805909656 1936028192 923.2G 79 unknown
/dev/sdc4 0 3637226495 3637226496 1.7T d unknown

Re: USB drive read-only after Mint upgrade

<Vqc%M.27198$INOa.7842@fx05.iad>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6999&group=alt.os.linux.mint#6999

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx05.iad.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.13.0
Reply-To: Nic@none.net
Subject: Re: USB drive read-only after Mint upgrade
Newsgroups: alt.os.linux.mint
References: <uhjdng$3b8vl$1@dont-email.me>
Content-Language: en-US
From: Nic...@none.net (Nic)
Organization: Arm Chair Observer
In-Reply-To: <uhjdng$3b8vl$1@dont-email.me>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 22
Message-ID: <Vqc%M.27198$INOa.7842@fx05.iad>
X-Complaints-To: abuse(at)newshosting.com
NNTP-Posting-Date: Sat, 28 Oct 2023 18:30:13 UTC
Date: Sat, 28 Oct 2023 14:30:13 -0400
X-Received-Bytes: 2052
 by: Nic - Sat, 28 Oct 2023 18:30 UTC

On 10/28/23 12:43 PM, Handsome Jack wrote:
> Yesterday I upgraded my Linux Mint 20.3 to 21. 2. One of the unpleasant side-effects is that my almost-permanently-plugged-in USB memory stick, which before the upgrade was readable and writable by me as user, is now read-only. Checking the permissions shows that the owner is now root, and I can't change it by doing "sudo chown ...": that gets "chown: changing ownership of 'USBdrive1': Operation not permitted"
>
>
> Any way I can fix this? The USB stick was originally formatted in Windows so I assume it is fat32.
>
> Doing an fdisk -l gives
>
> Disk /dev/sdc: 1.87 GiB, 2002780160 bytes, 3911680 sectors
> Disk model: USB DISK 2.0
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: dos
> Disk identifier: 0x6f20736b
>
> Device Boot Start End Sectors Size Id Type
> /dev/sdc1 778135908 1919645538 1141509631 544.3G 72 unknown
> /dev/sdc2 168689522 2104717761 1936028240 923.2G 65 Novell Netware 386
> /dev/sdc3 1869881465 3805909656 1936028192 923.2G 79 unknown
> /dev/sdc4 0 3637226495 3637226496 1.7T d unknown
Maybe plugging it into a windows machine and run chkdsk might help

Re: USB drive read-only after Mint upgrade

<slrnujqp0p.fhpv.ronb02NOSPAM@3020m.hitronhub.home>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7000&group=alt.os.linux.mint#7000

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: ronb02NO...@gmail.com (RonB)
Newsgroups: alt.os.linux.mint
Subject: Re: USB drive read-only after Mint upgrade
Date: Sat, 28 Oct 2023 19:42:17 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 31
Message-ID: <slrnujqp0p.fhpv.ronb02NOSPAM@3020m.hitronhub.home>
References: <uhjdng$3b8vl$1@dont-email.me> <Vqc%M.27198$INOa.7842@fx05.iad>
Injection-Date: Sat, 28 Oct 2023 19:42:17 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="76b6fc1798e9a6e932ad1151236e47c1";
logging-data="3655134"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/5HigbGw+4kvx39cIrpy7/"
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:fcb+1f6CQceY+Ewn0KarwnIzh/M=
 by: RonB - Sat, 28 Oct 2023 19:42 UTC

On 2023-10-28, Nic <Nic@none.net> wrote:
> On 10/28/23 12:43 PM, Handsome Jack wrote:
>> Yesterday I upgraded my Linux Mint 20.3 to 21. 2. One of the unpleasant side-effects is that my almost-permanently-plugged-in USB memory stick, which before the upgrade was readable and writable by me as user, is now read-only. Checking the permissions shows that the owner is now root, and I can't change it by doing "sudo chown ...": that gets "chown: changing ownership of 'USBdrive1': Operation not permitted"
>>
>>
>> Any way I can fix this? The USB stick was originally formatted in Windows so I assume it is fat32.
>>
>> Doing an fdisk -l gives
>>
>> Disk /dev/sdc: 1.87 GiB, 2002780160 bytes, 3911680 sectors
>> Disk model: USB DISK 2.0
>> Units: sectors of 1 * 512 = 512 bytes
>> Sector size (logical/physical): 512 bytes / 512 bytes
>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>> Disklabel type: dos
>> Disk identifier: 0x6f20736b
>>
>> Device Boot Start End Sectors Size Id Type
>> /dev/sdc1 778135908 1919645538 1141509631 544.3G 72 unknown
>> /dev/sdc2 168689522 2104717761 1936028240 923.2G 65 Novell Netware 386
>> /dev/sdc3 1869881465 3805909656 1936028192 923.2G 79 unknown
>> /dev/sdc4 0 3637226495 3637226496 1.7T d unknown
> Maybe plugging it into a windows machine and run chkdsk might help

Have you tried the USB Stick Formatter application that's built into Linux
Mint? That has fixed issues for me on USB drives. (This is only if you want
to delete what's on the USB drive, of course.)

--
"Evil preaches tolerance until it is dominant, then it tries to silence good."
-- Archbishop Charles J. Chaput

Re: USB drive read-only after Mint upgrade

<uhjpi5$3fpnk$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7001&group=alt.os.linux.mint#7001

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nos...@needed.invalid (Paul)
Newsgroups: alt.os.linux.mint
Subject: Re: USB drive read-only after Mint upgrade
Date: Sat, 28 Oct 2023 16:05:23 -0400
Organization: A noiseless patient Spider
Lines: 91
Message-ID: <uhjpi5$3fpnk$1@dont-email.me>
References: <uhjdng$3b8vl$1@dont-email.me> <Vqc%M.27198$INOa.7842@fx05.iad>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Date: Sat, 28 Oct 2023 20:05:25 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="da6e5d7330f10f4df8cc01a1d23a1633";
logging-data="3663604"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX193RjcRCXsIgrmsH07tw6TEeqxLtkpiUVk="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
Cancel-Lock: sha1:eynbhUTrGcqOqD+KXl73/CAbDtM=
Content-Language: en-US
In-Reply-To: <Vqc%M.27198$INOa.7842@fx05.iad>
 by: Paul - Sat, 28 Oct 2023 20:05 UTC

On 10/28/2023 2:30 PM, Nic wrote:
> On 10/28/23 12:43 PM, Handsome Jack wrote:
>> Yesterday I upgraded my Linux Mint 20.3 to 21. 2. One of the unpleasant side-effects is that my almost-permanently-plugged-in USB memory stick, which before the upgrade was readable and writable by me as user, is now read-only. Checking the permissions shows that the owner is now root, and I can't change it by doing "sudo chown ...": that gets "chown: changing ownership of 'USBdrive1': Operation not permitted"
>>
>>
>> Any way I can fix this? The USB stick was originally formatted in Windows so I assume it is fat32.
>>
>> Doing an fdisk -l gives
>>
>> Disk /dev/sdc: 1.87 GiB, 2002780160 bytes, 3911680 sectors
>> Disk model: USB DISK 2.0
>> Units: sectors of 1 * 512 = 512 bytes
>> Sector size (logical/physical): 512 bytes / 512 bytes
>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>> Disklabel type: dos
>> Disk identifier: 0x6f20736b
>>
>> Device     Boot      Start        End    Sectors   Size Id Type
>> /dev/sdc1        778135908 1919645538 1141509631 544.3G 72 unknown
>> /dev/sdc2        168689522 2104717761 1936028240 923.2G 65 Novell Netware 386
>> /dev/sdc3       1869881465 3805909656 1936028192 923.2G 79 unknown
>> /dev/sdc4                0 3637226495 3637226496   1.7T  d unknown
> Maybe plugging it into a windows machine and run chkdsk might help

I think Al has it figured out.

The installer has put it in text file /etc/fstab, and
the OP can try commenting out the entry so that the
automounter can take over after a reboot.

I would NOT pull the stick out mid-session, in the
mess it is in right now. We're no longer in "Safely Remove" country.

Mount points (those empty things the mount goes on top of),
those are typically owned by root. That's for static mounts
of some sort. The automounter makes mount points, as needed.

Also, the place the stick is normally mounted, likely has a different name
than what is displayed by the "df" command at the moment. You can
use "df" to "see if you're still in Kansas or not". I always use
"df" to verify things like USB sticks plugged in or whatever.

I would run

sudo disktype /dev/sdc # scans device, identifies file systems by sniffing

and just check and see whether the content of the stick has been
disturbed or not. It almost looks like the stick has no MBR
(could just be a single file system laid down on it), and fdisk
is trying to read and interpret the file system header, like
it is an MBR. Don't panic over what fdisk is saying right now,
also DONT use fdisk to make changes as it is right now!

The whole thing is "a bit disturbing", and I can feel two strands
of hair falling out right now :-)

This is a violation of the cardinal rule

"upgraded my Linux Mint"

DO NOT leave unrelated storage devices in a PC, while
you do upgrades or brand new multiboot installs. The installer
can stick boot materials just about anywhere (by mistake). By
limiting storage to just the drive involved in the operation,
you can limit the choices of the installer so it stays on target.

I didn't read this in some book -- this is a rule I use my own
self, "based on ruined stuff".

Anything that is an "OS Install" or "OS Upgrade", these are the conservative rules

1) Make a backup image of the target drive, before you begin work. <=== anything of value? back up!

2) Disconnect all unrelated storage (that might include some SD in an SD slot).
That includes disconnecting the backup drive used in step (1).

Then, if the installer destroys something... restore from backup.

There are a million reasons something can go nuts, on a PC.

I have a funny feeling this adventure is not over... Unfortunately.
It would not surprise me, to find the PC now won't boot, without
that USB stick being plugged in. There could be boot materials
on it now. Who knows. Maybe the USB stick really is a royal mess
now, and there is content loss. But don't panic. And work slowly
to unravel things one bit at a time.

Actually, they put pithy textual comments in /etc/fstab, about
"things that were done". It is worth a read in a text editor, anyway.

Paul

Re: USB drive read-only after Mint upgrade

<Enf%M.99695$MJ59.59142@fx10.iad>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7002&group=alt.os.linux.mint#7002

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx10.iad.POSTED!not-for-mail
Newsgroups: alt.os.linux.mint
From: branimir...@icloud.com (Branimir Maksimovic)
Subject: Re: USB drive read-only after Mint upgrade
References: <uhjdng$3b8vl$1@dont-email.me>
User-Agent: slrn/1.0.3 (Darwin)
Lines: 32
Message-ID: <Enf%M.99695$MJ59.59142@fx10.iad>
X-Complaints-To: abuse@usenet-news.net
NNTP-Posting-Date: Sat, 28 Oct 2023 21:51:32 UTC
Organization: usenet-news.net
Date: Sat, 28 Oct 2023 21:51:32 GMT
X-Received-Bytes: 1994
 by: Branimir Maksimovic - Sat, 28 Oct 2023 21:51 UTC

On 2023-10-28, Handsome Jack <Jack@handsome.com> wrote:
> Yesterday I upgraded my Linux Mint 20.3 to 21. 2. One of the unpleasant
> side-effects is that my almost-permanently-plugged-in USB memory stick, which
> before the upgrade was readable and writable by me as user, is now read-only.
> Checking the permissions shows that the owner is now root, and I can't change
> it by doing "sudo chown ...": that gets "chown: changing ownership of
> 'USBdrive1': Operation not permitted"
>
>
> Any way I can fix this? The USB stick was originally formatted in Windows so
> I assume it is fat32.
>
> Doing an fdisk -l gives
>
> Disk /dev/sdc: 1.87 GiB, 2002780160 bytes, 3911680 sectors Disk model: USB
> DISK 2.0 Units: sectors of 1 * 512 = 512 bytes Sector size
> (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512
> bytes / 512 bytes Disklabel type: dos Disk identifier: 0x6f20736b
>
> Device Boot Start End Sectors Size Id Type /dev/sdc1
> 778135908 1919645538 1141509631 544.3G 72 unknown /dev/sdc2 168689522
> 2104717761 1936028240 923.2G 65 Novell Netware 386 /dev/sdc3 1869881465
> 3805909656 1936028192 923.2G 79 unknown /dev/sdc4 0 3637226495
> 3637226496 1.7T d unknown
If you used it like ordinary disk it is probably dead.
I killed several this way, in router, then switched to ordinary external
hdd...

--

7-77-777, Evil Sinner!
https://www.linkedin.com/in/branimir-maksimovic-6762bbaa/

Re: USB drive read-only after Mint upgrade

<uhku40$3oidk$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7003&group=alt.os.linux.mint#7003

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Jac...@handsome.com (Handsome Jack)
Newsgroups: alt.os.linux.mint
Subject: Re: USB drive read-only after Mint upgrade
Date: Sun, 29 Oct 2023 06:29:23 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 31
Message-ID: <uhku40$3oidk$1@dont-email.me>
References: <uhjdng$3b8vl$1@dont-email.me> <uhjebe$3dlmm$1@dont-email.me>
Injection-Date: Sun, 29 Oct 2023 06:29:23 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="b07e7b6850ff54b22c9832b502809f39";
logging-data="3951028"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/T7YzdtjqVd+fDk1oZPXsGrZPU+mGmkWs="
User-Agent: tin/2.6.2-20220130 ("Convalmore") (Linux/5.15.0-87-generic (x86_64))
Cancel-Lock: sha1:OT+uXOoaq6LCFHoSqoYPZC3Is/I=
 by: Handsome Jack - Sun, 29 Oct 2023 06:29 UTC

Big Al <Bears@invalid.com> wrote:
>
> Just curious, was it installed (plugged in) while you did the upgrade?

Yes.

> Is it part of fstab and auto mounts? or do you just plug it in when needed?

It lives in the USB slot and is used for regular partial backups while I'm working. I only take it out to put it in another (Windows) machine.

I'm not really sure how to answer your first question above, but the stick does appear on the desktop when you plug it in (though you then have to mount it manually through the right-click pop-up menu).

\etc\fstab contains

[begins]
# /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>
# / was on /dev/sda2 during installation
UUID=124a4408-ca61-4ee2-a9d6-06cc09e5e1be / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=4494-52DA /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
LABEL=USB\040DISK /mnt/USB\040DISK auto nosuid,nodev,nofail,x-gvfs-show,noauto 0 0
[ends]

That file is date-stamped August 2023 so it hasn't been altered by the Mint 21.3 installation.

Re: USB drive read-only after Mint upgrade

<uhku6e$3oidk$2@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7004&group=alt.os.linux.mint#7004

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!news.chmurka.net!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Jac...@handsome.com (Handsome Jack)
Newsgroups: alt.os.linux.mint
Subject: Re: USB drive read-only after Mint upgrade
Date: Sun, 29 Oct 2023 06:30:40 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 31
Message-ID: <uhku6e$3oidk$2@dont-email.me>
References: <uhjdng$3b8vl$1@dont-email.me> <Vqc%M.27198$INOa.7842@fx05.iad> <slrnujqp0p.fhpv.ronb02NOSPAM@3020m.hitronhub.home>
Injection-Date: Sun, 29 Oct 2023 06:30:40 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="b07e7b6850ff54b22c9832b502809f39";
logging-data="3951028"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+uVOkIJ3Rpw3CSqHe9sg/4E1f+E5jX8RA="
User-Agent: tin/2.6.2-20220130 ("Convalmore") (Linux/5.15.0-87-generic (x86_64))
Cancel-Lock: sha1:sG+60Ge9tJ1dVNB1JhHmw6/ursQ=
 by: Handsome Jack - Sun, 29 Oct 2023 06:30 UTC

RonB <ronb02NOSPAM@gmail.com> wrote:
> On 2023-10-28, Nic <Nic@none.net> wrote:
>> On 10/28/23 12:43 PM, Handsome Jack wrote:
>>> Yesterday I upgraded my Linux Mint 20.3 to 21. 2. One of the unpleasant side-effects is that my almost-permanently-plugged-in USB memory stick, which before the upgrade was readable and writable by me as user, is now read-only. Checking the permissions shows that the owner is now root, and I can't change it by doing "sudo chown ...": that gets "chown: changing ownership of 'USBdrive1': Operation not permitted"
>>>
>>>
>>> Any way I can fix this? The USB stick was originally formatted in Windows so I assume it is fat32.
>>>
>>> Doing an fdisk -l gives
>>>
>>> Disk /dev/sdc: 1.87 GiB, 2002780160 bytes, 3911680 sectors
>>> Disk model: USB DISK 2.0
>>> Units: sectors of 1 * 512 = 512 bytes
>>> Sector size (logical/physical): 512 bytes / 512 bytes
>>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Disklabel type: dos
>>> Disk identifier: 0x6f20736b
>>>
>>> Device Boot Start End Sectors Size Id Type
>>> /dev/sdc1 778135908 1919645538 1141509631 544.3G 72 unknown
>>> /dev/sdc2 168689522 2104717761 1936028240 923.2G 65 Novell Netware 386
>>> /dev/sdc3 1869881465 3805909656 1936028192 923.2G 79 unknown
>>> /dev/sdc4 0 3637226495 3637226496 1.7T d unknown
>> Maybe plugging it into a windows machine and run chkdsk might help
>
> Have you tried the USB Stick Formatter application that's built into Linux
> Mint? That has fixed issues for me on USB drives. (This is only if you want
> to delete what's on the USB drive, of course.)
>

I'll make a copy of the USB contents and then try it. WIll it be readable by a Windows machine afterwards?

Re: USB drive read-only after Mint upgrade

<uhkuot$3oidk$3@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7005&group=alt.os.linux.mint#7005

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Jac...@handsome.com (Handsome Jack)
Newsgroups: alt.os.linux.mint
Subject: Re: USB drive read-only after Mint upgrade
Date: Sun, 29 Oct 2023 06:40:31 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 106
Message-ID: <uhkuot$3oidk$3@dont-email.me>
References: <uhjdng$3b8vl$1@dont-email.me> <Vqc%M.27198$INOa.7842@fx05.iad> <uhjpi5$3fpnk$1@dont-email.me>
Injection-Date: Sun, 29 Oct 2023 06:40:31 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="b07e7b6850ff54b22c9832b502809f39";
logging-data="3951028"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19sVklzCPhkMVqnFuB9d4+X7lPkwr15bLo="
User-Agent: tin/2.6.2-20220130 ("Convalmore") (Linux/5.15.0-87-generic (x86_64))
Cancel-Lock: sha1:mBJXxsRnoyBFsYw0CF38BbaIQE8=
 by: Handsome Jack - Sun, 29 Oct 2023 06:40 UTC

Paul <nospam@needed.invalid> wrote:
> I think Al has it figured out.
>
> The installer has put it in text file /etc/fstab,

Apparently not; that file is still date-stamped August 2023 so it wasn't changed by the Mint 21.2 install. See my reply to Al.

> and
> the OP can try commenting out the entry so that the
> automounter can take over after a reboot.
>
> I would NOT pull the stick out mid-session, in the
> mess it is in right now. We're no longer in "Safely Remove" country.

I pulled it out after shutting the machine down last night.

The machine rebooted OK this morning without the stick, thank God.

> Mount points (those empty things the mount goes on top of),
> those are typically owned by root. That's for static mounts
> of some sort. The automounter makes mount points, as needed.
>
> Also, the place the stick is normally mounted, likely has a different name
> than what is displayed by the "df" command at the moment. You can
> use "df" to "see if you're still in Kansas or not". I always use
> "df" to verify things like USB sticks plugged in or whatever.
>
> I would run
>
> sudo disktype /dev/sdc # scans device, identifies file systems by sniffing

That produces "sudo: disktype: command not found".

> and just check and see whether the content of the stick has been
> disturbed or not.

It looks all right.

> It almost looks like the stick has no MBR
> (could just be a single file system laid down on it), and fdisk
> is trying to read and interpret the file system header, like
> it is an MBR.

You've lost me there.

> Don't panic over what fdisk is saying right now,
> also DONT use fdisk to make changes as it is right now!
>
> The whole thing is "a bit disturbing", and I can feel two strands
> of hair falling out right now :-)

Think how I feel ...
>
> This is a violation of the cardinal rule
>
> "upgraded my Linux Mint"
>
> DO NOT leave unrelated storage devices in a PC, while
> you do upgrades or brand new multiboot installs. The installer
> can stick boot materials just about anywhere (by mistake). By
> limiting storage to just the drive involved in the operation,
> you can limit the choices of the installer so it stays on target.

It's a pity that nobody told me this beforehand.

And they say that Linux is hard to use. Tchah.

>
> I didn't read this in some book -- this is a rule I use my own
> self, "based on ruined stuff".
>
> Anything that is an "OS Install" or "OS Upgrade", these are the conservative rules
>
> 1) Make a backup image of the target drive, before you begin work. <=== anything of value? back up!

I did that - the installer routine told me to.

>
> 2) Disconnect all unrelated storage (that might include some SD in an SD slot).
> That includes disconnecting the backup drive used in step (1).

Didn't do that.

>
> Then, if the installer destroys something... restore from backup.
>
> There are a million reasons something can go nuts, on a PC.
>
> I have a funny feeling this adventure is not over... Unfortunately.
> It would not surprise me, to find the PC now won't boot, without
> that USB stick being plugged in. There could be boot materials
> on it now. Who knows.

No, the PC booted OK this moring.

> Maybe the USB stick really is a royal mess
> now, and there is content loss. But don't panic. And work slowly
> to unravel things one bit at a time.

The content of the USB isn't that precious, I have other backups. But I do need it for my work.

>
> Actually, they put pithy textual comments in /etc/fstab, about
> "things that were done". It is worth a read in a text editor, anyway.
>
Many thanks for your detailed reply (and to others).

Re: USB drive read-only after Mint upgrade

<uhkvto$3or9o$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7006&group=alt.os.linux.mint#7006

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!rocksolid2!news.neodome.net!weretis.net!feeder8.news.weretis.net!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nos...@needed.invalid (Paul)
Newsgroups: alt.os.linux.mint
Subject: Re: USB drive read-only after Mint upgrade
Date: Sun, 29 Oct 2023 03:00:05 -0400
Organization: A noiseless patient Spider
Lines: 92
Message-ID: <uhkvto$3or9o$1@dont-email.me>
References: <uhjdng$3b8vl$1@dont-email.me> <Vqc%M.27198$INOa.7842@fx05.iad>
<slrnujqp0p.fhpv.ronb02NOSPAM@3020m.hitronhub.home>
<uhku6e$3oidk$2@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 29 Oct 2023 07:00:08 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="b23226e218ad45614d9a546a4d951b11";
logging-data="3960120"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+/8PYW54VKUA5dfvvIVep1tUllU0o+bDc="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
Cancel-Lock: sha1:yDrdz6hFzWXS5eUxx+m+gk1Yf78=
Content-Language: en-US
In-Reply-To: <uhku6e$3oidk$2@dont-email.me>
 by: Paul - Sun, 29 Oct 2023 07:00 UTC

On 10/29/2023 2:30 AM, Handsome Jack wrote:
> RonB <ronb02NOSPAM@gmail.com> wrote:
>> On 2023-10-28, Nic <Nic@none.net> wrote:
>>> On 10/28/23 12:43 PM, Handsome Jack wrote:
>>>> Yesterday I upgraded my Linux Mint 20.3 to 21. 2. One of the unpleasant side-effects is that my almost-permanently-plugged-in USB memory stick, which before the upgrade was readable and writable by me as user, is now read-only. Checking the permissions shows that the owner is now root, and I can't change it by doing "sudo chown ...": that gets "chown: changing ownership of 'USBdrive1': Operation not permitted"
>>>>
>>>>
>>>> Any way I can fix this? The USB stick was originally formatted in Windows so I assume it is fat32.
>>>>
>>>> Doing an fdisk -l gives
>>>>
>>>> Disk /dev/sdc: 1.87 GiB, 2002780160 bytes, 3911680 sectors
>>>> Disk model: USB DISK 2.0
>>>> Units: sectors of 1 * 512 = 512 bytes
>>>> Sector size (logical/physical): 512 bytes / 512 bytes
>>>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>>>> Disklabel type: dos
>>>> Disk identifier: 0x6f20736b
>>>>
>>>> Device Boot Start End Sectors Size Id Type
>>>> /dev/sdc1 778135908 1919645538 1141509631 544.3G 72 unknown
>>>> /dev/sdc2 168689522 2104717761 1936028240 923.2G 65 Novell Netware 386
>>>> /dev/sdc3 1869881465 3805909656 1936028192 923.2G 79 unknown
>>>> /dev/sdc4 0 3637226495 3637226496 1.7T d unknown
>>> Maybe plugging it into a windows machine and run chkdsk might help
>>
>> Have you tried the USB Stick Formatter application that's built into Linux
>> Mint? That has fixed issues for me on USB drives. (This is only if you want
>> to delete what's on the USB drive, of course.)
>>
>
> I'll make a copy of the USB contents and then try it. WIll it be readable by a Windows machine afterwards?
>

sudo apt install disktype

sudo disktype /dev/sdc

We want to check it out, without moving it.
What it should tell you, if it was a Windows stick,
is that it has "NTFS" as a single partition. That
"hints" it is not damaged. That is not as powerful as
doing a CHKDSK, but it looks for a few attributes suggesting
it is NTFS. Disktype is FOSS, and a tiny executable, and it
has quite an array of filesystem detections.

If the OS had tried to automount "Novell Netware 386" then
that might be an issue. I'm sure the partition sizes
and offsets, make no sense with respect to the actual
capacity of the stick.

You can use the "df" command, and look for weird stuff
that has mounted, and should not be there.

If it thought it had detected a Linux partition type,
it might have tried to run fsck on it, which would
not be a good thing.

In the good old days, you would have run "dmesg" and
got the boot log and have a look at it, as it used to
record "things it was doing to storage" as it was booting.
But progress being what it is, I'm not sure that log
has integrity any more. I have not the foggiest, if
there is any record of the quality of dmesg, now hiding
in the machine. dmesg, you see, was too simple for those
developers, and it doesn't put them in control. Now, the
little fuckers are in control. Solved.

*******

If you want to copy the stick, the command might look like

sudo dd if=/dev/sdc of=/dev/sdd bs=65536 status=progress # Assumes stick is a multiple of 64K bytes

( https://man7.org/linux/man-pages/man1/dd.1.html)

That would copy all of storage device sdc to storage device sdd.
The assumption is, that sdd is the same size or a bit bigger than sdc,
so that nothing is lost.

That is a block by block transfer, so nothing gets lost. If
there is damage, all the damage is copied verbatim.

If the stick was NTFS, there is "ntfsclone" which may be
more efficient than the dd (disk dump) command, in that
only the files get copied and not the white space between
files. That is what Clonezilla uses. But considering the
OS currently doesn't seem to know what is going on, the
"dd" command is the safest, because "dd" makes no assumptions
about anything, and just copies sectors.

Paul

Re: USB drive read-only after Mint upgrade

<slrnujs2bt.qgk.ronb02NOSPAM@3020m.hitronhub.home>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7007&group=alt.os.linux.mint#7007

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: ronb02NO...@gmail.com (RonB)
Newsgroups: alt.os.linux.mint
Subject: Re: USB drive read-only after Mint upgrade
Date: Sun, 29 Oct 2023 07:27:57 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 38
Message-ID: <slrnujs2bt.qgk.ronb02NOSPAM@3020m.hitronhub.home>
References: <uhjdng$3b8vl$1@dont-email.me> <Vqc%M.27198$INOa.7842@fx05.iad>
<slrnujqp0p.fhpv.ronb02NOSPAM@3020m.hitronhub.home>
<uhku6e$3oidk$2@dont-email.me>
Injection-Date: Sun, 29 Oct 2023 07:27:57 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="7ad61385a8a1a30bde320c25410adfa4";
logging-data="3968467"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18kpa2ihUpFHXTGx92whAx4"
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:hBCakJGal8Yo0c+1V5yHOv6QSi8=
 by: RonB - Sun, 29 Oct 2023 07:27 UTC

On 2023-10-29, Handsome Jack <Jack@handsome.com> wrote:
> RonB <ronb02NOSPAM@gmail.com> wrote:
>> On 2023-10-28, Nic <Nic@none.net> wrote:
>>> On 10/28/23 12:43 PM, Handsome Jack wrote:
>>>> Yesterday I upgraded my Linux Mint 20.3 to 21. 2. One of the unpleasant side-effects is that my almost-permanently-plugged-in USB memory stick, which before the upgrade was readable and writable by me as user, is now read-only. Checking the permissions shows that the owner is now root, and I can't change it by doing "sudo chown ...": that gets "chown: changing ownership of 'USBdrive1': Operation not permitted"
>>>>
>>>>
>>>> Any way I can fix this? The USB stick was originally formatted in Windows so I assume it is fat32.
>>>>
>>>> Doing an fdisk -l gives
>>>>
>>>> Disk /dev/sdc: 1.87 GiB, 2002780160 bytes, 3911680 sectors
>>>> Disk model: USB DISK 2.0
>>>> Units: sectors of 1 * 512 = 512 bytes
>>>> Sector size (logical/physical): 512 bytes / 512 bytes
>>>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>>>> Disklabel type: dos
>>>> Disk identifier: 0x6f20736b
>>>>
>>>> Device Boot Start End Sectors Size Id Type
>>>> /dev/sdc1 778135908 1919645538 1141509631 544.3G 72 unknown
>>>> /dev/sdc2 168689522 2104717761 1936028240 923.2G 65 Novell Netware 386
>>>> /dev/sdc3 1869881465 3805909656 1936028192 923.2G 79 unknown
>>>> /dev/sdc4 0 3637226495 3637226496 1.7T d unknown
>>> Maybe plugging it into a windows machine and run chkdsk might help
>>
>> Have you tried the USB Stick Formatter application that's built into Linux
>> Mint? That has fixed issues for me on USB drives. (This is only if you want
>> to delete what's on the USB drive, of course.)
>>
>
> I'll make a copy of the USB contents and then try it. WIll it be readable by a Windows machine afterwards?

Yes, if the format is successful.

--
"Evil preaches tolerance until it is dominant, then it tries to silence good."
-- Archbishop Charles J. Chaput

Re: USB drive read-only after Mint upgrade

<uhl3fe$3pd7g$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7009&group=alt.os.linux.mint#7009

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!nntp.comgw.net!paganini.bofh.team!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Jac...@handsome.com (Handsome Jack)
Newsgroups: alt.os.linux.mint
Subject: Re: USB drive read-only after Mint upgrade
Date: Sun, 29 Oct 2023 08:00:49 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 105
Message-ID: <uhl3fe$3pd7g$1@dont-email.me>
References: <uhjdng$3b8vl$1@dont-email.me> <Vqc%M.27198$INOa.7842@fx05.iad> <slrnujqp0p.fhpv.ronb02NOSPAM@3020m.hitronhub.home> <uhku6e$3oidk$2@dont-email.me> <uhkvto$3or9o$1@dont-email.me>
Injection-Date: Sun, 29 Oct 2023 08:00:49 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="b07e7b6850ff54b22c9832b502809f39";
logging-data="3978480"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+nb2rxRA1M5WDIg+bheYhgic1ltH8Y+Lw="
User-Agent: tin/2.6.2-20220130 ("Convalmore") (Linux/5.15.0-87-generic (x86_64))
Cancel-Lock: sha1:/dq8hxEdJ9FaQFudmih083FM2zw=
 by: Handsome Jack - Sun, 29 Oct 2023 08:00 UTC

Paul <nospam@needed.invalid> wrote:
> On 10/29/2023 2:30 AM, Handsome Jack wrote:
>> RonB <ronb02NOSPAM@gmail.com> wrote:
>>> On 2023-10-28, Nic <Nic@none.net> wrote:
>>>> On 10/28/23 12:43 PM, Handsome Jack wrote:
>>>>> Yesterday I upgraded my Linux Mint 20.3 to 21. 2. One of the unpleasant side-effects is that my almost-permanently-plugged-in USB memory stick, which before the upgrade was readable and writable by me as user, is now read-only. Checking the permissions shows that the owner is now root, and I can't change it by doing "sudo chown ...": that gets "chown: changing ownership of 'USBdrive1': Operation not permitted"
>>>>>
>>>>>
>>>>> Any way I can fix this? The USB stick was originally formatted in Windows so I assume it is fat32.
>>>>>
>>>>> Doing an fdisk -l gives
>>>>>
>>>>> Disk /dev/sdc: 1.87 GiB, 2002780160 bytes, 3911680 sectors
>>>>> Disk model: USB DISK 2.0
>>>>> Units: sectors of 1 * 512 = 512 bytes
>>>>> Sector size (logical/physical): 512 bytes / 512 bytes
>>>>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>>>>> Disklabel type: dos
>>>>> Disk identifier: 0x6f20736b
>>>>>
>>>>> Device Boot Start End Sectors Size Id Type
>>>>> /dev/sdc1 778135908 1919645538 1141509631 544.3G 72 unknown
>>>>> /dev/sdc2 168689522 2104717761 1936028240 923.2G 65 Novell Netware 386
>>>>> /dev/sdc3 1869881465 3805909656 1936028192 923.2G 79 unknown
>>>>> /dev/sdc4 0 3637226495 3637226496 1.7T d unknown
>>>> Maybe plugging it into a windows machine and run chkdsk might help
>>>
>>> Have you tried the USB Stick Formatter application that's built into Linux
>>> Mint? That has fixed issues for me on USB drives. (This is only if you want
>>> to delete what's on the USB drive, of course.)
>>>
>>
>> I'll make a copy of the USB contents and then try it. WIll it be readable by a Windows machine afterwards?
>>
>
> sudo apt install disktype
>
> sudo disktype /dev/sdc
>
> We want to check it out, without moving it.
> What it should tell you, if it was a Windows stick,
> is that it has "NTFS" as a single partition. That
> "hints" it is not damaged. That is not as powerful as
> doing a CHKDSK, but it looks for a few attributes suggesting
> it is NTFS. Disktype is FOSS, and a tiny executable, and it
> has quite an array of filesystem detections.

The device's name has been changed to sdd (prob because I stuck it into a different USB socket) and the result of "sudo disktype /dev/sdd" is
[begin]
--- /dev/sdd
Block device, size 1.865 GiB (2002780160 bytes)
Windows NTLDR boot loader
FAT16 file system (hints score 4 of 5)
Volume size 1.865 GiB (2002518016 bytes, 61112 clusters of 32 KiB)
[end]

>
> If the OS had tried to automount "Novell Netware 386" then
> that might be an issue. I'm sure the partition sizes
> and offsets, make no sense with respect to the actual
> capacity of the stick.

No they don't. Perhaps a reformat will fix it.

> You can use the "df" command, and look for weird stuff
> that has mounted, and should not be there.

That produces:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 704008 3032 700976 1% /run
/dev/sda2 121969296 61660348 54067108 54% /
tmpfs 3520028 0 3520028 0% /dev/shm
tmpfs 5120 4 5116 1% /run/lock
/dev/sda1 523248 6220 517028 2% /boot/efi
tmpfs 704004 100 703904 1% /run/user/1000
/dev/sdb4 976807100 56115448 920691652 6% /media/jack/40DA9A89DA9A7ABC
/dev/sdd 1955584 373120 1582464 20% /mnt/USB DISK

> If it thought it had detected a Linux partition type,
> it might have tried to run fsck on it, which would
> not be a good thing.
>
> In the good old days, you would have run "dmesg" and
> got the boot log and have a look at it, as it used to
> record "things it was doing to storage" as it was booting.

Just did that, it produces a hge splurge of output that is not intelligible to me, though it does contain two suggestive lines as follows:
[ 5675.118073] FAT-fs (sdd): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

However there is no intelligible time-stamping on the lines, so I don't know when that happened.

> But progress being what it is, I'm not sure that log
> has integrity any more. I have not the foggiest, if
> there is any record of the quality of dmesg, now hiding
> in the machine. dmesg, you see, was too simple for those
> developers, and it doesn't put them in control. Now, the
> little fuckers are in control. Solved.
>
> *******
>
> If you want to copy the stick, the command might look like

[snip] I simply copied the contents to a temporary directory on my hard disk. Seems OK.

Re: USB drive read-only after Mint upgrade

<uhlefu$3rffl$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7013&group=alt.os.linux.mint#7013

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!1.us.feeder.erje.net!3.eu.feeder.erje.net!2.eu.feeder.erje.net!feeder.erje.net!gandalf.srv.welterde.de!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nos...@needed.invalid (Paul)
Newsgroups: alt.os.linux.mint
Subject: Re: USB drive read-only after Mint upgrade
Date: Sun, 29 Oct 2023 07:08:43 -0400
Organization: A noiseless patient Spider
Lines: 63
Message-ID: <uhlefu$3rffl$1@dont-email.me>
References: <uhjdng$3b8vl$1@dont-email.me> <Vqc%M.27198$INOa.7842@fx05.iad>
<slrnujqp0p.fhpv.ronb02NOSPAM@3020m.hitronhub.home>
<uhku6e$3oidk$2@dont-email.me> <uhkvto$3or9o$1@dont-email.me>
<uhl3fe$3pd7g$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 29 Oct 2023 11:08:46 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="b23226e218ad45614d9a546a4d951b11";
logging-data="4046325"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+VlzNhD3C744iUuz5gKVu4/8VhPbKIwwA="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
Cancel-Lock: sha1:V3/nAeaIcdqMLBBdlLNWJ8oZric=
In-Reply-To: <uhl3fe$3pd7g$1@dont-email.me>
Content-Language: en-US
 by: Paul - Sun, 29 Oct 2023 11:08 UTC

On 10/29/2023 4:00 AM, Handsome Jack wrote:
> /dev/sdd 1955584 373120 1582464 20% /mnt/USB DISK

So your USB stick, the one that fdisk did such a great
job of displaying, is mounted. The file system starts
at sector 0, as expected. That means there is no MBR.
It is possible a Windows utility did that.

An example of a sequence.

*******

First, some fun stuff I've used before. Cleaning GPT tables,
the tools for that are not very reliable (poor track record).

sudo gdisk /dev/sdd
"Initial answer???" doesn't matter
x # Expert mode
z # Zap GPT structure on USB stick, zero out MBR if asked
q

sudo fdisk /dev/sdd # should now look clean

So that section, is if you want to look at a cleaning first.

*******

This assumes you have all of your goods from /mnt/USB DISK safely stored on a hard drive.

sudo umount "/mnt/USB DISK" # I'm only guessing that name is OK!
# Sometimes an OS will eject a stick when you do that,
# making it somewhat uncertain the next command will work,
# without unplugging and replugging USB stick.

sudo dd if=/dev/zero of=/dev/sdd bs=512 count=1 # Wipe out first sector.

sudo fdisk /dev/sdd # Work on it in FDISK.
o # "Oh" - create new empty MBR
n # Create a partition
p # Make it primary
1 # Call it partition number 1
<carriage return, default offset> # Accept default 1MB offset for partition.
<carriage return, for size of whole disk> # Accept default of partition == whole disk
t # Change partition type
l # "Elle", lists the available types. 07=NTFS 0C=FAT32 etc
07 # Now, the partition table is 0x07 NTFS for first partition
w # Write the new table

Now, it still needs to be formatted. In my VM, this feels slow for some reason.

sudo mkfs.ntfs -f -L BUCKET /dev/sdd1 # Need to format it, to pass muster

sudo disktype /dev/sdd # Verify all is well

Now, take it over to Windows, and see if it looks pretty or not :-)

The next time you plug it in, the sudo fdisk /dev/sdd
is not going to look nearly so stupid. If the OS
wants to mount it, it should be working properly.

Paul

Re: USB drive read-only after Mint upgrade

<uhleqr$3rh92$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7014&group=alt.os.linux.mint#7014

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!paganini.bofh.team!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nos...@needed.invalid (Paul)
Newsgroups: alt.os.linux.mint
Subject: Re: USB drive read-only after Mint upgrade
Date: Sun, 29 Oct 2023 07:14:32 -0400
Organization: A noiseless patient Spider
Lines: 19
Message-ID: <uhleqr$3rh92$1@dont-email.me>
References: <uhjdng$3b8vl$1@dont-email.me> <Vqc%M.27198$INOa.7842@fx05.iad>
<slrnujqp0p.fhpv.ronb02NOSPAM@3020m.hitronhub.home>
<uhku6e$3oidk$2@dont-email.me> <uhkvto$3or9o$1@dont-email.me>
<uhl3fe$3pd7g$1@dont-email.me> <uhlefu$3rffl$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 29 Oct 2023 11:14:35 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="b23226e218ad45614d9a546a4d951b11";
logging-data="4048162"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19yiptwmKz4Mp90LIfIFOaeLs8tXS9f0fs="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
Cancel-Lock: sha1:7hAbLJAIRnSFW+0eV1dlzmcm5Vw=
In-Reply-To: <uhlefu$3rffl$1@dont-email.me>
Content-Language: en-US
 by: Paul - Sun, 29 Oct 2023 11:14 UTC

On 10/29/2023 7:08 AM, Paul wrote:
> On 10/29/2023 4:00 AM, Handsome Jack wrote:
>> /dev/sdd 1955584 373120 1582464 20% /mnt/USB DISK
>

sudo nano /etc/fstab # Don't forget to check that hard mount in the FSTAB!
# /mnt is not automounter
# /media/mint is likely to be automounter
# Try to find the USB DISK entry that corresponds to the /mnt thing.
# Comment it out with a "#" , like the other comments use.
# Save your changes

cat /etc/fstab # Quick review you really updated it.

If you need more help, copy the appropriate parts of your fstab
into a posting.

Paul

Re: USB drive read-only after Mint upgrade

<uhm14r$3v8bi$5@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7022&group=alt.os.linux.mint#7022

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Jac...@handsome.com (Handsome Jack)
Newsgroups: alt.os.linux.mint
Subject: Re: USB drive read-only after Mint upgrade
Date: Sun, 29 Oct 2023 16:27:09 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 21
Message-ID: <uhm14r$3v8bi$5@dont-email.me>
References: <uhjdng$3b8vl$1@dont-email.me> <Vqc%M.27198$INOa.7842@fx05.iad> <slrnujqp0p.fhpv.ronb02NOSPAM@3020m.hitronhub.home> <uhku6e$3oidk$2@dont-email.me> <uhkvto$3or9o$1@dont-email.me> <uhl3fe$3pd7g$1@dont-email.me> <uhlefu$3rffl$1@dont-email.me> <uhleqr$3rh92$1@dont-email.me>
Injection-Date: Sun, 29 Oct 2023 16:27:09 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="b07e7b6850ff54b22c9832b502809f39";
logging-data="4170098"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX198W7Iax6KiqVOxxdmALuema8mGhB3mZN4="
User-Agent: tin/2.6.2-20220130 ("Convalmore") (Linux/5.15.0-87-generic (x86_64))
Cancel-Lock: sha1:DerNmcIi29Dk55cFmVW8sDUgJGU=
 by: Handsome Jack - Sun, 29 Oct 2023 16:27 UTC

Paul <nospam@needed.invalid> wrote:
> On 10/29/2023 7:08 AM, Paul wrote:
>> On 10/29/2023 4:00 AM, Handsome Jack wrote:
>>> /dev/sdd 1955584 373120 1582464 20% /mnt/USB DISK
>>
>
> sudo nano /etc/fstab # Don't forget to check that hard mount in the FSTAB!
> # /mnt is not automounter
> # /media/mint is likely to be automounter
> # Try to find the USB DISK entry that corresponds to the /mnt thing.
> # Comment it out with a "#" , like the other comments use.
> # Save your changes
>
> cat /etc/fstab # Quick review you really updated it.
>
> If you need more help, copy the appropriate parts of your fstab
> into a posting.
>

Thanks for all this, but I am hopelessly confused. Why do we need entries for removable disks in /media/jack as well as /mnt? why is some stuff in /etc and some in /dev? I can't keep all this in my head.

Re: USB drive read-only after Mint upgrade

<uhm18e$3v8bi$6@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7023&group=alt.os.linux.mint#7023

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Jac...@handsome.com (Handsome Jack)
Newsgroups: alt.os.linux.mint
Subject: Re: USB drive read-only after Mint upgrade
Date: Sun, 29 Oct 2023 16:29:04 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 20
Message-ID: <uhm18e$3v8bi$6@dont-email.me>
References: <uhjdng$3b8vl$1@dont-email.me> <Vqc%M.27198$INOa.7842@fx05.iad> <slrnujqp0p.fhpv.ronb02NOSPAM@3020m.hitronhub.home> <uhku6e$3oidk$2@dont-email.me> <uhkvto$3or9o$1@dont-email.me> <uhl3fe$3pd7g$1@dont-email.me> <uhlefu$3rffl$1@dont-email.me> <uhleqr$3rh92$1@dont-email.me>
Injection-Date: Sun, 29 Oct 2023 16:29:04 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="b07e7b6850ff54b22c9832b502809f39";
logging-data="4170098"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+GbLESTjnKL0ccrmtLF4bGaaXwaOn0f04="
User-Agent: tin/2.6.2-20220130 ("Convalmore") (Linux/5.15.0-87-generic (x86_64))
Cancel-Lock: sha1:I2gqmNh+g3gcj1cj5L8t57Lvkm4=
 by: Handsome Jack - Sun, 29 Oct 2023 16:29 UTC

Paul <nospam@needed.invalid> wrote:
> On 10/29/2023 7:08 AM, Paul wrote:
>> On 10/29/2023 4:00 AM, Handsome Jack wrote:
>>> /dev/sdd 1955584 373120 1582464 20% /mnt/USB DISK
>>
>
> sudo nano /etc/fstab # Don't forget to check that hard mount in the FSTAB!
> # /mnt is not automounter
> # /media/mint is likely to be automounter
> # Try to find the USB DISK entry that corresponds to the /mnt thing.
> # Comment it out with a "#" , like the other comments use.
> # Save your changes
>
> cat /etc/fstab # Quick review you really updated it.
>
> If you need more help, copy the appropriate parts of your fstab
> into a posting.
>

I've now used the Mint formatting utility to wipe the USB drive. It seems to have restored r/w ownership to me so the problem is sort of solved.

Re: USB drive read-only after Mint upgrade

<uhm7l1$mke$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7024&group=alt.os.linux.mint#7024

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nom...@hotmail.com (Edmund)
Newsgroups: alt.os.linux.mint
Subject: Re: USB drive read-only after Mint upgrade
Date: Sun, 29 Oct 2023 19:18:09 +0100
Organization: A noiseless patient Spider
Lines: 44
Message-ID: <uhm7l1$mke$1@dont-email.me>
References: <uhjdng$3b8vl$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 29 Oct 2023 18:18:09 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="fbfd1741c19b91f59c427a129fac2812";
logging-data="23182"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/ESjIq4qJuhw1eDUrAXZmH"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:0Onh8BMAQfNb05do6MlxBxHuDWg=
Content-Language: en-US
In-Reply-To: <uhjdng$3b8vl$1@dont-email.me>
 by: Edmund - Sun, 29 Oct 2023 18:18 UTC

On 10/28/23 18:43, Handsome Jack wrote:
> Yesterday I upgraded my Linux Mint 20.3 to 21. 2. One of the unpleasant side-effects is that my almost-permanently-plugged-in USB memory stick, which before the upgrade was readable and writable by me as user, is now read-only. Checking the permissions shows that the owner is now root, and I can't change it by doing "sudo chown ...": that gets "chown: changing ownership of 'USBdrive1': Operation not permitted"
>
>
> Any way I can fix this? The USB stick was originally formatted in Windows so I assume it is fat32.
>
> Doing an fdisk -l gives
>
> Disk /dev/sdc: 1.87 GiB, 2002780160 bytes, 3911680 sectors
> Disk model: USB DISK 2.0
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: dos
> Disk identifier: 0x6f20736b
>
> Device Boot Start End Sectors Size Id Type
> /dev/sdc1 778135908 1919645538 1141509631 544.3G 72 unknown
> /dev/sdc2 168689522 2104717761 1936028240 923.2G 65 Novell Netware 386
> /dev/sdc3 1869881465 3805909656 1936028192 923.2G 79 unknown
> /dev/sdc4 0 3637226495 3637226496 1.7T d unknown

Welcome, you are number "many" who encountered the linux-USB problem.

After a some trial and error you might get it working again, but the
Linux-community will explain it away, say it is YOUR OWN FAULT and our
cut and paste "coders" will ignore it.

Edmund

--
-------------

The moment any organization established from pure noble intentions get
some influence, it will be corrupted from both inside and outside.
Then we have organizations established from pure evil.

Edmund

Re: USB drive read-only after Mint upgrade

<slrnujtfee.1lag.ronb02NOSPAM@3020m.hitronhub.home>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7025&group=alt.os.linux.mint#7025

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: ronb02NO...@gmail.com (RonB)
Newsgroups: alt.os.linux.mint
Subject: Re: USB drive read-only after Mint upgrade
Date: Sun, 29 Oct 2023 20:17:18 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 39
Message-ID: <slrnujtfee.1lag.ronb02NOSPAM@3020m.hitronhub.home>
References: <uhjdng$3b8vl$1@dont-email.me> <uhm7l1$mke$1@dont-email.me>
Injection-Date: Sun, 29 Oct 2023 20:17:18 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="7ad61385a8a1a30bde320c25410adfa4";
logging-data="65658"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19qBR8mF8LhsxChLTNsVECa"
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:DiqE6lv/NmEfknspzuGP7Nhn3Eo=
 by: RonB - Sun, 29 Oct 2023 20:17 UTC

On 2023-10-29, Edmund <nomail@hotmail.com> wrote:
> On 10/28/23 18:43, Handsome Jack wrote:
>> Yesterday I upgraded my Linux Mint 20.3 to 21. 2. One of the unpleasant side-effects is that my almost-permanently-plugged-in USB memory stick, which before the upgrade was readable and writable by me as user, is now read-only. Checking the permissions shows that the owner is now root, and I can't change it by doing "sudo chown ...": that gets "chown: changing ownership of 'USBdrive1': Operation not permitted"
>>
>>
>> Any way I can fix this? The USB stick was originally formatted in Windows so I assume it is fat32.
>>
>> Doing an fdisk -l gives
>>
>> Disk /dev/sdc: 1.87 GiB, 2002780160 bytes, 3911680 sectors
>> Disk model: USB DISK 2.0
>> Units: sectors of 1 * 512 = 512 bytes
>> Sector size (logical/physical): 512 bytes / 512 bytes
>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>> Disklabel type: dos
>> Disk identifier: 0x6f20736b
>>
>> Device Boot Start End Sectors Size Id Type
>> /dev/sdc1 778135908 1919645538 1141509631 544.3G 72 unknown
>> /dev/sdc2 168689522 2104717761 1936028240 923.2G 65 Novell Netware 386
>> /dev/sdc3 1869881465 3805909656 1936028192 923.2G 79 unknown
>> /dev/sdc4 0 3637226495 3637226496 1.7T d unknown
>
>
> Welcome, you are number "many" who encountered the linux-USB problem.
>
> After a some trial and error you might get it working again, but the
> Linux-community will explain it away, say it is YOUR OWN FAULT and our
> cut and paste "coders" will ignore it.

Wrong. By telling Jack that I've used the built-in Linux Mint formatting
utility for situations like this, it's an admission that this has been an
issue for me in the past.

Don't put words in my mouth and I won't put words in your mouth. Agreed?

--
"Evil preaches tolerance until it is dominant, then it tries to silence good."
-- Archbishop Charles J. Chaput

Re: USB drive read-only after Mint upgrade

<uhmmgq$3e00$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7028&group=alt.os.linux.mint#7028

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nos...@needed.invalid (Paul)
Newsgroups: alt.os.linux.mint
Subject: Re: USB drive read-only after Mint upgrade
Date: Sun, 29 Oct 2023 18:31:53 -0400
Organization: A noiseless patient Spider
Lines: 88
Message-ID: <uhmmgq$3e00$1@dont-email.me>
References: <uhjdng$3b8vl$1@dont-email.me> <Vqc%M.27198$INOa.7842@fx05.iad>
<slrnujqp0p.fhpv.ronb02NOSPAM@3020m.hitronhub.home>
<uhku6e$3oidk$2@dont-email.me> <uhkvto$3or9o$1@dont-email.me>
<uhl3fe$3pd7g$1@dont-email.me> <uhlefu$3rffl$1@dont-email.me>
<uhleqr$3rh92$1@dont-email.me> <uhm18e$3v8bi$6@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 29 Oct 2023 22:31:55 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="b23226e218ad45614d9a546a4d951b11";
logging-data="112640"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18RV/s2aW3EdAF59szTUK4gk3xTyE9Ybt8="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
Cancel-Lock: sha1:QVpFplOdxVTGO6bKCJcGVCKzR/E=
Content-Language: en-US
In-Reply-To: <uhm18e$3v8bi$6@dont-email.me>
 by: Paul - Sun, 29 Oct 2023 22:31 UTC

On 10/29/2023 12:29 PM, Handsome Jack wrote:
> Paul <nospam@needed.invalid> wrote:
>> On 10/29/2023 7:08 AM, Paul wrote:
>>> On 10/29/2023 4:00 AM, Handsome Jack wrote:
>>>> /dev/sdd 1955584 373120 1582464 20% /mnt/USB DISK
>>>
>>
>> sudo nano /etc/fstab # Don't forget to check that hard mount in the FSTAB!
>> # /mnt is not automounter
>> # /media/mint is likely to be automounter
>> # Try to find the USB DISK entry that corresponds to the /mnt thing.
>> # Comment it out with a "#" , like the other comments use.
>> # Save your changes
>>
>> cat /etc/fstab # Quick review you really updated it.
>>
>> If you need more help, copy the appropriate parts of your fstab
>> into a posting.
>>
>
> I've now used the Mint formatting utility to wipe the USB drive. It seems to have restored r/w ownership to me so the problem is sort of solved.
>

The OS really should not be manually mounting your goods, as you showed
in your results. The installer may have done it, which is why I recommended
reading the /etc/fstab control file, for the details.

You don't want the OS fucking with your stuff. You want your
defacto config, to be the same as my defacto config. Then,
when you ask a question, we're on the same page. Anything which
has run amok on your install, the simple stuff, should be fixed
so there are no future surprises.

The automounter would normally do the mounting, with no involvement
of the /etc/fstab control file. The automounter creates the mount point
automatically, then puts the mount on top of that. Later, when the OS
shuts down, the partition is dismounted and the mount points would be
cleared.

Manual mounts in /etc/fstab, can be entered with a text editor
by the user, and would normally be used for captive hard drives
inside a device.

Manual mounts, also allow your /home to be stored on a separate
partition from the rest of the OS. This allows moving your /home
at a later date. Some of the participants in this group, handle
various parts of their OS as separate partitions. I don't bother
with that, as I'm a rather casual user.

If you look at the custom install options for the OS, they
support defining your /home, as a partition which mounts on
top of / which is the root directory of the assembled file system.

As part of the learning experience, you should learn what the
moving parts under slash (the system root / ) are about.
If your OS breaks, and you need to rescue it, that's the
time some of this knowledge is useful. Mounts can not only
go on /mnt, they can go just about anywhere. And it is a useful
skill to "notice" a thing you used to have access to, is now
owned by root. That may not be an accident! It may mean
a mount point in a complex mount structure, has just "broken loose".

/etc/fstab <=== how the administrator controls manual mounts

//etc/mtab <=== a record, of the current set of mounts

cat /etc/mtab <=== use this command, to see what the OS has been up to.
You might be shocked at the mess in Ubuntu, for example.

There are also standards involved, so the structure is
standardized with usage in Unix and Linux. There are occasional
things which don't always follow the rules. Sometimes the packages
you install, are in /opt. But not everything does that. Only
some of the packages do. And /opt might be more "popular"
on some other platform, and you're only getting things packaged
that way for fun.

On occasion, you may install a package, and then when you typed
the command you expected to be present, it's not there! That's
because maybe /opt is not in your $PATH. You may need to add a path
component, into your $PATH, so the executable can be found. Maybe
the needed path component is /opt/something/bin for example.

Always expect the unexpected. If you can fix something in five
minutes yourself, it saves wasting two days waiting for us to
guess what broke :-)

Paul

Re: USB drive read-only after Mint upgrade

<uho1qf$ds71$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7040&group=alt.os.linux.mint#7040

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!rocksolid2!news.neodome.net!usenet.network!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nom...@hotmail.com (Edmund)
Newsgroups: alt.os.linux.mint
Subject: Re: USB drive read-only after Mint upgrade
Date: Mon, 30 Oct 2023 11:50:54 +0100
Organization: A noiseless patient Spider
Lines: 63
Message-ID: <uho1qf$ds71$1@dont-email.me>
References: <uhjdng$3b8vl$1@dont-email.me> <uhm7l1$mke$1@dont-email.me>
<slrnujtfee.1lag.ronb02NOSPAM@3020m.hitronhub.home>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Mon, 30 Oct 2023 10:50:55 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="24aa1507f4d63224948ac8c76bd00ea5";
logging-data="454881"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/PHjtoep8ZyxboeTgTx+tg"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:5Ii3PBwQDzjAOtiIbUI/U6B882Q=
Content-Language: en-US
In-Reply-To: <slrnujtfee.1lag.ronb02NOSPAM@3020m.hitronhub.home>
 by: Edmund - Mon, 30 Oct 2023 10:50 UTC

On 10/29/23 21:17, RonB wrote:
> On 2023-10-29, Edmund <nomail@hotmail.com> wrote:
>> On 10/28/23 18:43, Handsome Jack wrote:
>>> Yesterday I upgraded my Linux Mint 20.3 to 21. 2. One of the unpleasant side-effects is that my almost-permanently-plugged-in USB memory stick, which before the upgrade was readable and writable by me as user, is now read-only. Checking the permissions shows that the owner is now root, and I can't change it by doing "sudo chown ...": that gets "chown: changing ownership of 'USBdrive1': Operation not permitted"
>>>
>>>
>>> Any way I can fix this? The USB stick was originally formatted in Windows so I assume it is fat32.
>>>
>>> Doing an fdisk -l gives
>>>
>>> Disk /dev/sdc: 1.87 GiB, 2002780160 bytes, 3911680 sectors
>>> Disk model: USB DISK 2.0
>>> Units: sectors of 1 * 512 = 512 bytes
>>> Sector size (logical/physical): 512 bytes / 512 bytes
>>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Disklabel type: dos
>>> Disk identifier: 0x6f20736b
>>>
>>> Device Boot Start End Sectors Size Id Type
>>> /dev/sdc1 778135908 1919645538 1141509631 544.3G 72 unknown
>>> /dev/sdc2 168689522 2104717761 1936028240 923.2G 65 Novell Netware 386
>>> /dev/sdc3 1869881465 3805909656 1936028192 923.2G 79 unknown
>>> /dev/sdc4 0 3637226495 3637226496 1.7T d unknown
>>
>>
>> Welcome, you are number "many" who encountered the linux-USB problem.
>>
>> After a some trial and error you might get it working again, but the
>> Linux-community will explain it away, say it is YOUR OWN FAULT and our
>> cut and paste "coders" will ignore it.
>
> Wrong. By telling Jack that I've used the built-in Linux Mint formatting
> utility for situations like this, it's an admission that this has been an
> issue for me in the past.
>
> Don't put words in my mouth and I won't put words in your mouth. Agreed?

Well feel free to share with us which words you imagine that I have put
in your mouth.
Free free to attack me for saying again linux has USB proplems, even
though you just encountered and mentioned it here. Never let facts
distracts you from your bias about anything.

The simple answer here would be : Yes linux has a USB problem for
decades! But nobody cares.

The solution would be : Creating a system where BUGs can be reported
with a staff that READ these bugs and a team that pick it up and solve it.

Spoiler: it not going to happen.
Attacking the messenger its much more fun :-)

Edmund

--
-------------

The moment any organization established from pure noble intentions get
some influence, it will be corrupted from both inside and outside.
Then we have organizations established from pure evil.

Edmund

Re: USB drive read-only after Mint upgrade

<uhofj1$gc1c$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7043&group=alt.os.linux.mint#7043

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!feeder2.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nom...@hotmail.com (Edmund)
Newsgroups: alt.os.linux.mint
Subject: Re: USB drive read-only after Mint upgrade
Date: Mon, 30 Oct 2023 15:45:52 +0100
Organization: A noiseless patient Spider
Lines: 103
Message-ID: <uhofj1$gc1c$1@dont-email.me>
References: <uhjdng$3b8vl$1@dont-email.me> <Vqc%M.27198$INOa.7842@fx05.iad>
<slrnujqp0p.fhpv.ronb02NOSPAM@3020m.hitronhub.home>
<uhku6e$3oidk$2@dont-email.me> <uhkvto$3or9o$1@dont-email.me>
<uhl3fe$3pd7g$1@dont-email.me> <uhlefu$3rffl$1@dont-email.me>
<uhleqr$3rh92$1@dont-email.me> <uhm18e$3v8bi$6@dont-email.me>
<uhmmgq$3e00$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Mon, 30 Oct 2023 14:45:53 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="24aa1507f4d63224948ac8c76bd00ea5";
logging-data="536620"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/dI0GeWWxFkB5y+csf7E3V"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:/uDqYp4qqBTvgpGOm9l65h2Yjbo=
In-Reply-To: <uhmmgq$3e00$1@dont-email.me>
Content-Language: en-US
 by: Edmund - Mon, 30 Oct 2023 14:45 UTC

On 10/29/23 23:31, Paul wrote:
> On 10/29/2023 12:29 PM, Handsome Jack wrote:
>> Paul <nospam@needed.invalid> wrote:
>>> On 10/29/2023 7:08 AM, Paul wrote:
>>>> On 10/29/2023 4:00 AM, Handsome Jack wrote:
>>>>> /dev/sdd 1955584 373120 1582464 20% /mnt/USB DISK
>>>>
>>>
>>> sudo nano /etc/fstab # Don't forget to check that hard mount in the FSTAB!
>>> # /mnt is not automounter
>>> # /media/mint is likely to be automounter
>>> # Try to find the USB DISK entry that corresponds to the /mnt thing.
>>> # Comment it out with a "#" , like the other comments use.
>>> # Save your changes
>>>
>>> cat /etc/fstab # Quick review you really updated it.
>>>
>>> If you need more help, copy the appropriate parts of your fstab
>>> into a posting.
>>>
>>
>> I've now used the Mint formatting utility to wipe the USB drive. It seems to have restored r/w ownership to me so the problem is sort of solved.
>>
>
> The OS really should not be manually mounting your goods, as you showed
> in your results. The installer may have done it, which is why I recommended
> reading the /etc/fstab control file, for the details.
>
> You don't want the OS fucking with your stuff. You want your
> defacto config, to be the same as my defacto config. Then,
> when you ask a question, we're on the same page. Anything which
> has run amok on your install, the simple stuff, should be fixed
> so there are no future surprises.
>
> The automounter would normally do the mounting, with no involvement
> of the /etc/fstab control file. The automounter creates the mount point
> automatically, then puts the mount on top of that. Later, when the OS
> shuts down, the partition is dismounted and the mount points would be
> cleared.
>
> Manual mounts in /etc/fstab, can be entered with a text editor
> by the user, and would normally be used for captive hard drives
> inside a device.
>
> Manual mounts, also allow your /home to be stored on a separate
> partition from the rest of the OS. This allows moving your /home
> at a later date. Some of the participants in this group, handle
> various parts of their OS as separate partitions. I don't bother
> with that, as I'm a rather casual user.
>
> If you look at the custom install options for the OS, they
> support defining your /home, as a partition which mounts on
> top of / which is the root directory of the assembled file system.
>
> As part of the learning experience, you should learn what the
> moving parts under slash (the system root / ) are about.
> If your OS breaks, and you need to rescue it, that's the
> time some of this knowledge is useful. Mounts can not only
> go on /mnt, they can go just about anywhere. And it is a useful
> skill to "notice" a thing you used to have access to, is now
> owned by root. That may not be an accident! It may mean
> a mount point in a complex mount structure, has just "broken loose".
>
> /etc/fstab <=== how the administrator controls manual mounts
>
> //etc/mtab <=== a record, of the current set of mounts
>
> cat /etc/mtab <=== use this command, to see what the OS has been up to.
> You might be shocked at the mess in Ubuntu, for example.
>
> There are also standards involved, so the structure is
> standardized with usage in Unix and Linux. There are occasional
> things which don't always follow the rules. Sometimes the packages
> you install, are in /opt. But not everything does that. Only
> some of the packages do. And /opt might be more "popular"
> on some other platform, and you're only getting things packaged
> that way for fun.
>
> On occasion, you may install a package, and then when you typed
> the command you expected to be present, it's not there! That's
> because maybe /opt is not in your $PATH. You may need to add a path
> component, into your $PATH, so the executable can be found. Maybe
> the needed path component is /opt/something/bin for example.
>
> Always expect the unexpected. If you can fix something in five
> minutes yourself, it saves wasting two days waiting for us to
> guess what broke :-)

Yes, same for TRYING the file a bug.
For starters, it is impossible to do so.
and IF you manage to do it anyway, nobody cares.
>
> Paul

--
-------------

The moment any organization established from pure noble intentions get
some influence, it will be corrupted from both inside and outside.
Then we have organizations established from pure evil.

Edmund

Re: USB drive read-only after Mint upgrade

<uhol1v$grjj$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7044&group=alt.os.linux.mint#7044

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!news.chmurka.net!eternal-september.org!feeder2.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: wicklowh...@rfburns.eu (wicklowham)
Newsgroups: alt.os.linux.mint
Subject: Re: USB drive read-only after Mint upgrade
Date: Mon, 30 Oct 2023 16:19:11 +0000
Organization: A noiseless patient Spider
Lines: 81
Message-ID: <uhol1v$grjj$1@dont-email.me>
References: <uhjdng$3b8vl$1@dont-email.me> <uhm7l1$mke$1@dont-email.me>
<slrnujtfee.1lag.ronb02NOSPAM@3020m.hitronhub.home>
<uho1qf$ds71$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 30 Oct 2023 16:19:11 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="35fbfc7d4f08faaf5c41f6866d98614b";
logging-data="552563"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX191ut7NpSueEKnyZ84o6Rz/WAg6t87oS34="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:ELwo+MeeIOQqwP/i04G2QUgHt2E=
Content-Language: en-US
In-Reply-To: <uho1qf$ds71$1@dont-email.me>
 by: wicklowham - Mon, 30 Oct 2023 16:19 UTC

On 30/10/2023 10:50, Edmund wrote:
> On 10/29/23 21:17, RonB wrote:
>> On 2023-10-29, Edmund <nomail@hotmail.com> wrote:
>>> On 10/28/23 18:43, Handsome Jack wrote:
>>>> Yesterday I upgraded my Linux Mint 20.3 to 21. 2. One of the
>>>> unpleasant side-effects is that my almost-permanently-plugged-in USB
>>>> memory stick, which before the upgrade was readable and writable by
>>>> me as user, is now read-only. Checking the permissions shows that
>>>> the owner is now root, and I can't change it by doing "sudo chown
>>>> ...": that gets "chown: changing ownership of 'USBdrive1': Operation
>>>> not permitted"
>>>>
>>>>
>>>> Any way I can fix this? The USB stick was originally formatted in
>>>> Windows so I assume it is fat32.
>>>>
>>>> Doing an fdisk -l gives
>>>>
>>>> Disk /dev/sdc: 1.87 GiB, 2002780160 bytes, 3911680 sectors
>>>> Disk model: USB DISK 2.0
>>>> Units: sectors of 1 * 512 = 512 bytes
>>>> Sector size (logical/physical): 512 bytes / 512 bytes
>>>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>>>> Disklabel type: dos
>>>> Disk identifier: 0x6f20736b
>>>>
>>>> Device     Boot      Start        End    Sectors   Size Id Type
>>>> /dev/sdc1        778135908 1919645538 1141509631 544.3G 72 unknown
>>>> /dev/sdc2        168689522 2104717761 1936028240 923.2G 65 Novell
>>>> Netware 386
>>>> /dev/sdc3       1869881465 3805909656 1936028192 923.2G 79 unknown
>>>> /dev/sdc4                0 3637226495 3637226496   1.7T  d unknown
>>>
>>>
>>> Welcome, you are number "many" who encountered the linux-USB problem.
>>>
>>> After a some trial and error you might get it working again, but the
>>> Linux-community will explain it away, say it is YOUR OWN FAULT and our
>>> cut and paste "coders" will ignore it.
>>
>> Wrong. By telling Jack that I've used the built-in Linux Mint formatting
>> utility for situations like this, it's an admission that this has been an
>> issue for me in the past.
>>
>> Don't put words in my mouth and I won't put words in your mouth. Agreed?
>
> Well feel free to share with us which words you imagine that I have put
> in your mouth.
> Free free to attack me for saying again linux has USB proplems, even
> though you just encountered and mentioned it here. Never let facts
> distracts you from your bias about anything.
>
> The simple answer here would be : Yes linux has a USB problem for
> decades! But nobody cares.
>
> The solution would be : Creating a system where BUGs can be reported
> with a staff that READ these bugs and a team that pick it up and solve it.
>
> Spoiler: it not going to happen.
> Attacking the messenger its much more fun :-)
>
> Edmund
>
============================
Very surprising messages re USB memory sticks .I never had any "read
only" problems with any Linux distro during the past 18 years.
A few days ago at a recycle centre I found a physically dirty 1GB stick
with educational info (probably from a school teacher )
After physical cleaning the stick I erased all data with Gparted and
reformatted it FAT32. Writing/reading any files : NO problem

I also have erased and reformatted various disk drives from discarded
laptops with Gparted.

Currently on various 13-10 years old machines (desktop and laptop) I use
Linux Mint 21.2 and Zorin OS 16.3 all with a system SSD.

Frank in County Wicklow , Republic of Ireland

Re: USB drive read-only after Mint upgrade

<2_40N.205958$0UVe.73363@fx17.iad>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7047&group=alt.os.linux.mint#7047

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!1.us.feeder.erje.net!feeder.erje.net!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx17.iad.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.13.0
Reply-To: Nic@none.net
Subject: Re: USB drive read-only after Mint upgrade
Newsgroups: alt.os.linux.mint
References: <uhjdng$3b8vl$1@dont-email.me> <Vqc%M.27198$INOa.7842@fx05.iad>
<slrnujqp0p.fhpv.ronb02NOSPAM@3020m.hitronhub.home>
<uhku6e$3oidk$2@dont-email.me> <uhkvto$3or9o$1@dont-email.me>
<uhl3fe$3pd7g$1@dont-email.me> <uhlefu$3rffl$1@dont-email.me>
<uhleqr$3rh92$1@dont-email.me> <uhm18e$3v8bi$6@dont-email.me>
<uhmmgq$3e00$1@dont-email.me> <uhofj1$gc1c$1@dont-email.me>
Content-Language: en-US
From: Nic...@none.net (Nic)
Organization: Arm Chair Observer
In-Reply-To: <uhofj1$gc1c$1@dont-email.me>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Lines: 108
Message-ID: <2_40N.205958$0UVe.73363@fx17.iad>
X-Complaints-To: abuse(at)newshosting.com
NNTP-Posting-Date: Tue, 31 Oct 2023 10:50:38 UTC
Date: Tue, 31 Oct 2023 06:50:37 -0400
X-Received-Bytes: 6291
 by: Nic - Tue, 31 Oct 2023 10:50 UTC

On 10/30/23 10:45 AM, Edmund wrote:
> On 10/29/23 23:31, Paul wrote:
>> On 10/29/2023 12:29 PM, Handsome Jack wrote:
>>> Paul <nospam@needed.invalid> wrote:
>>>> On 10/29/2023 7:08 AM, Paul wrote:
>>>>> On 10/29/2023 4:00 AM, Handsome Jack wrote:
>>>>>> /dev/sdd         1955584 373120   1582464  20% /mnt/USB DISK
>>>>>
>>>>
>>>> sudo nano /etc/fstab             # Don't forget to check that hard
>>>> mount in the FSTAB!
>>>>                                   # /mnt is not automounter
>>>>                                   # /media/mint is likely to be
>>>> automounter
>>>>                                   # Try to find the USB DISK entry
>>>> that corresponds to the /mnt thing.
>>>>                                   # Comment it out with a "#" ,
>>>> like the other comments use.
>>>>                                   # Save your changes
>>>>
>>>> cat /etc/fstab                   # Quick review you really updated it.
>>>>
>>>> If you need more help, copy the appropriate parts of your fstab
>>>> into a posting.
>>>>
>>>
>>> I've now used the Mint formatting utility to wipe the USB drive. It
>>> seems to have restored r/w ownership to me so the problem is sort of
>>> solved.
>>>
>>
>> The OS really should not be manually mounting your goods, as you showed
>> in your results. The installer may have done it, which is why I
>> recommended
>> reading the /etc/fstab control file, for the details.
>>
>> You don't want the OS fucking with your stuff. You want your
>> defacto config, to be the same as my defacto config. Then,
>> when you ask a question, we're on the same page. Anything which
>> has run amok on your install, the simple stuff, should be fixed
>> so there are no future surprises.
>>
>> The automounter would normally do the mounting, with no involvement
>> of the /etc/fstab control file. The automounter creates the mount point
>> automatically, then puts the mount on top of that. Later, when the OS
>> shuts down, the partition is dismounted and the mount points would be
>> cleared.
>>
>> Manual mounts in /etc/fstab, can be entered with a text editor
>> by the user, and would normally be used for captive hard drives
>> inside a device.
>>
>> Manual mounts, also allow your /home to be stored on a separate
>> partition from the rest of the OS. This allows moving your /home
>> at a later date. Some of the participants in this group, handle
>> various parts of their OS as separate partitions. I don't bother
>> with that, as I'm a rather casual user.
>>
>> If you look at the custom install options for the OS, they
>> support defining your /home, as a partition which mounts on
>> top of / which is the root directory of the assembled file system.
>>
>> As part of the learning experience, you should learn what the
>> moving parts under slash (the system root / ) are about.
>> If your OS breaks, and you need to rescue it, that's the
>> time some of this knowledge is useful. Mounts can not only
>> go on /mnt, they can go just about anywhere. And it is a useful
>> skill to "notice" a thing you used to have access to, is now
>> owned by root. That may not be an accident! It may mean
>> a mount point in a complex mount structure, has just "broken loose".
>>
>> /etc/fstab   <=== how the administrator controls manual mounts
>>
>> //etc/mtab   <=== a record, of the current set of mounts
>>
>> cat /etc/mtab  <=== use this command, to see what the OS has been up to.
>>                      You might be shocked at the mess in Ubuntu, for
>> example.
>>
>> There are also standards involved, so the structure is
>> standardized with usage in Unix and Linux. There are occasional
>> things which don't always follow the rules. Sometimes the packages
>> you install, are in /opt. But not everything does that. Only
>> some of the packages do. And /opt might be more "popular"
>> on some other platform, and you're only getting things packaged
>> that way for fun.
>>
>> On occasion, you may install a package, and then when you typed
>> the command you expected to be present, it's not there! That's
>> because maybe /opt is not in your $PATH. You may need to add a path
>> component, into your $PATH, so the executable can be found. Maybe
>> the needed path component is /opt/something/bin for example.
>>
>> Always expect the unexpected. If you can fix something in five
>> minutes yourself, it saves wasting two days waiting for us to
>> guess what broke :-)
>
> Yes, same for TRYING the file a bug.
> For starters, it is impossible to do so.
> and IF you manage to do it anyway, nobody cares.
>>
>>     Paul
>
I agree Linux Mint has its share of problems with usb at the top, but I
will continue to use it instead of the m$ alternatives. It is a great
system that can compete with the m$$$$$$$ way. I like to think that as
computers evolve and as new knowledge is acquired eventually most of
these problems will go away.

Re: USB drive read-only after Mint upgrade

<uhqpog$119u3$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7048&group=alt.os.linux.mint#7048

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!news.nntp4.net!news5.corell.dk!news.corell.dk!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nom...@hotmail.com (Edmund)
Newsgroups: alt.os.linux.mint
Subject: Re: USB drive read-only after Mint upgrade
Date: Tue, 31 Oct 2023 12:51:44 +0100
Organization: A noiseless patient Spider
Lines: 123
Message-ID: <uhqpog$119u3$1@dont-email.me>
References: <uhjdng$3b8vl$1@dont-email.me> <Vqc%M.27198$INOa.7842@fx05.iad>
<slrnujqp0p.fhpv.ronb02NOSPAM@3020m.hitronhub.home>
<uhku6e$3oidk$2@dont-email.me> <uhkvto$3or9o$1@dont-email.me>
<uhl3fe$3pd7g$1@dont-email.me> <uhlefu$3rffl$1@dont-email.me>
<uhleqr$3rh92$1@dont-email.me> <uhm18e$3v8bi$6@dont-email.me>
<uhmmgq$3e00$1@dont-email.me> <uhofj1$gc1c$1@dont-email.me>
<2_40N.205958$0UVe.73363@fx17.iad>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 31 Oct 2023 11:51:44 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="cc57717d8ea1ab91f6155ab89a4d74e3";
logging-data="1091523"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/WwRqrPaG7N49elNvcMk+x"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:YWi9EV0jTfbA/SZBZjxffhjXVY8=
Content-Language: en-US
In-Reply-To: <2_40N.205958$0UVe.73363@fx17.iad>
 by: Edmund - Tue, 31 Oct 2023 11:51 UTC

On 10/31/23 11:50, Nic wrote:
> On 10/30/23 10:45 AM, Edmund wrote:
>> On 10/29/23 23:31, Paul wrote:
>>> On 10/29/2023 12:29 PM, Handsome Jack wrote:
>>>> Paul <nospam@needed.invalid> wrote:
>>>>> On 10/29/2023 7:08 AM, Paul wrote:
>>>>>> On 10/29/2023 4:00 AM, Handsome Jack wrote:
>>>>>>> /dev/sdd         1955584 373120   1582464  20% /mnt/USB DISK
>>>>>>
>>>>>
>>>>> sudo nano /etc/fstab             # Don't forget to check that hard
>>>>> mount in the FSTAB!
>>>>>                                   # /mnt is not automounter
>>>>>                                   # /media/mint is likely to be
>>>>> automounter
>>>>>                                   # Try to find the USB DISK entry
>>>>> that corresponds to the /mnt thing.
>>>>>                                   # Comment it out with a "#" ,
>>>>> like the other comments use.
>>>>>                                   # Save your changes
>>>>>
>>>>> cat /etc/fstab                   # Quick review you really updated it.
>>>>>
>>>>> If you need more help, copy the appropriate parts of your fstab
>>>>> into a posting.
>>>>>
>>>>
>>>> I've now used the Mint formatting utility to wipe the USB drive. It
>>>> seems to have restored r/w ownership to me so the problem is sort of
>>>> solved.
>>>>
>>>
>>> The OS really should not be manually mounting your goods, as you showed
>>> in your results. The installer may have done it, which is why I
>>> recommended
>>> reading the /etc/fstab control file, for the details.
>>>
>>> You don't want the OS fucking with your stuff. You want your
>>> defacto config, to be the same as my defacto config. Then,
>>> when you ask a question, we're on the same page. Anything which
>>> has run amok on your install, the simple stuff, should be fixed
>>> so there are no future surprises.
>>>
>>> The automounter would normally do the mounting, with no involvement
>>> of the /etc/fstab control file. The automounter creates the mount point
>>> automatically, then puts the mount on top of that. Later, when the OS
>>> shuts down, the partition is dismounted and the mount points would be
>>> cleared.
>>>
>>> Manual mounts in /etc/fstab, can be entered with a text editor
>>> by the user, and would normally be used for captive hard drives
>>> inside a device.
>>>
>>> Manual mounts, also allow your /home to be stored on a separate
>>> partition from the rest of the OS. This allows moving your /home
>>> at a later date. Some of the participants in this group, handle
>>> various parts of their OS as separate partitions. I don't bother
>>> with that, as I'm a rather casual user.
>>>
>>> If you look at the custom install options for the OS, they
>>> support defining your /home, as a partition which mounts on
>>> top of / which is the root directory of the assembled file system.
>>>
>>> As part of the learning experience, you should learn what the
>>> moving parts under slash (the system root / ) are about.
>>> If your OS breaks, and you need to rescue it, that's the
>>> time some of this knowledge is useful. Mounts can not only
>>> go on /mnt, they can go just about anywhere. And it is a useful
>>> skill to "notice" a thing you used to have access to, is now
>>> owned by root. That may not be an accident! It may mean
>>> a mount point in a complex mount structure, has just "broken loose".
>>>
>>> /etc/fstab   <=== how the administrator controls manual mounts
>>>
>>> //etc/mtab   <=== a record, of the current set of mounts
>>>
>>> cat /etc/mtab  <=== use this command, to see what the OS has been up to.
>>>                      You might be shocked at the mess in Ubuntu, for
>>> example.
>>>
>>> There are also standards involved, so the structure is
>>> standardized with usage in Unix and Linux. There are occasional
>>> things which don't always follow the rules. Sometimes the packages
>>> you install, are in /opt. But not everything does that. Only
>>> some of the packages do. And /opt might be more "popular"
>>> on some other platform, and you're only getting things packaged
>>> that way for fun.
>>>
>>> On occasion, you may install a package, and then when you typed
>>> the command you expected to be present, it's not there! That's
>>> because maybe /opt is not in your $PATH. You may need to add a path
>>> component, into your $PATH, so the executable can be found. Maybe
>>> the needed path component is /opt/something/bin for example.
>>>
>>> Always expect the unexpected. If you can fix something in five
>>> minutes yourself, it saves wasting two days waiting for us to
>>> guess what broke :-)
>>
>> Yes, same for TRYING the file a bug.
>> For starters, it is impossible to do so.
>> and IF you manage to do it anyway, nobody cares.
>>>
>>>     Paul
>>
> I agree Linux Mint has its share of problems with usb at the top, but I
> will continue to use it instead of the m$ alternatives. It is a great
> system that can compete with the m$$$$$$$ way. I like to think that as
> computers evolve and as new knowledge is acquired eventually most of
> these problems will go away.

I gave up that idea, the utter insanity and chaos in the linux society
make sure things will never be solved.

--
-------------

The moment any organization established from pure noble intentions get
some influence, it will be corrupted from both inside and outside.
Then we have organizations established from pure evil.

Edmund

Re: USB drive read-only after Mint upgrade

<jd70N.265183$2fS.84911@fx16.iad>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=7049&group=alt.os.linux.mint#7049

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!feeder2.eternal-september.org!eternal-september.org!feeder1.feed.usenet.farm!feed.usenet.farm!peer01.ams4!peer.am4.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx16.iad.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.13.0
Reply-To: Nic@none.net
Subject: Re: USB drive read-only after Mint upgrade
Content-Language: en-US
Newsgroups: alt.os.linux.mint
References: <uhjdng$3b8vl$1@dont-email.me> <Vqc%M.27198$INOa.7842@fx05.iad>
<slrnujqp0p.fhpv.ronb02NOSPAM@3020m.hitronhub.home>
<uhku6e$3oidk$2@dont-email.me> <uhkvto$3or9o$1@dont-email.me>
<uhl3fe$3pd7g$1@dont-email.me> <uhlefu$3rffl$1@dont-email.me>
<uhleqr$3rh92$1@dont-email.me> <uhm18e$3v8bi$6@dont-email.me>
<uhmmgq$3e00$1@dont-email.me> <uhofj1$gc1c$1@dont-email.me>
<2_40N.205958$0UVe.73363@fx17.iad> <uhqpog$119u3$1@dont-email.me>
From: Nic...@none.net (Nic)
Organization: Arm Chair Observer
In-Reply-To: <uhqpog$119u3$1@dont-email.me>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Lines: 124
Message-ID: <jd70N.265183$2fS.84911@fx16.iad>
X-Complaints-To: abuse(at)newshosting.com
NNTP-Posting-Date: Tue, 31 Oct 2023 13:23:27 UTC
Date: Tue, 31 Oct 2023 09:23:27 -0400
X-Received-Bytes: 7228
 by: Nic - Tue, 31 Oct 2023 13:23 UTC

On 10/31/23 7:51 AM, Edmund wrote:
> On 10/31/23 11:50, Nic wrote:
>> On 10/30/23 10:45 AM, Edmund wrote:
>>> On 10/29/23 23:31, Paul wrote:
>>>> On 10/29/2023 12:29 PM, Handsome Jack wrote:
>>>>> Paul <nospam@needed.invalid> wrote:
>>>>>> On 10/29/2023 7:08 AM, Paul wrote:
>>>>>>> On 10/29/2023 4:00 AM, Handsome Jack wrote:
>>>>>>>> /dev/sdd         1955584 373120   1582464  20% /mnt/USB DISK
>>>>>>>
>>>>>>
>>>>>> sudo nano /etc/fstab             # Don't forget to check that
>>>>>> hard mount in the FSTAB!
>>>>>>                                   # /mnt is not automounter
>>>>>>                                   # /media/mint is likely to be
>>>>>> automounter
>>>>>>                                   # Try to find the USB DISK
>>>>>> entry that corresponds to the /mnt thing.
>>>>>>                                   # Comment it out with a "#" ,
>>>>>> like the other comments use.
>>>>>>                                   # Save your changes
>>>>>>
>>>>>> cat /etc/fstab                   # Quick review you really
>>>>>> updated it.
>>>>>>
>>>>>> If you need more help, copy the appropriate parts of your fstab
>>>>>> into a posting.
>>>>>>
>>>>>
>>>>> I've now used the Mint formatting utility to wipe the USB drive.
>>>>> It seems to have restored r/w ownership to me so the problem is
>>>>> sort of solved.
>>>>>
>>>>
>>>> The OS really should not be manually mounting your goods, as you
>>>> showed
>>>> in your results. The installer may have done it, which is why I
>>>> recommended
>>>> reading the /etc/fstab control file, for the details.
>>>>
>>>> You don't want the OS fucking with your stuff. You want your
>>>> defacto config, to be the same as my defacto config. Then,
>>>> when you ask a question, we're on the same page. Anything which
>>>> has run amok on your install, the simple stuff, should be fixed
>>>> so there are no future surprises.
>>>>
>>>> The automounter would normally do the mounting, with no involvement
>>>> of the /etc/fstab control file. The automounter creates the mount
>>>> point
>>>> automatically, then puts the mount on top of that. Later, when the OS
>>>> shuts down, the partition is dismounted and the mount points would be
>>>> cleared.
>>>>
>>>> Manual mounts in /etc/fstab, can be entered with a text editor
>>>> by the user, and would normally be used for captive hard drives
>>>> inside a device.
>>>>
>>>> Manual mounts, also allow your /home to be stored on a separate
>>>> partition from the rest of the OS. This allows moving your /home
>>>> at a later date. Some of the participants in this group, handle
>>>> various parts of their OS as separate partitions. I don't bother
>>>> with that, as I'm a rather casual user.
>>>>
>>>> If you look at the custom install options for the OS, they
>>>> support defining your /home, as a partition which mounts on
>>>> top of / which is the root directory of the assembled file system.
>>>>
>>>> As part of the learning experience, you should learn what the
>>>> moving parts under slash (the system root / ) are about.
>>>> If your OS breaks, and you need to rescue it, that's the
>>>> time some of this knowledge is useful. Mounts can not only
>>>> go on /mnt, they can go just about anywhere. And it is a useful
>>>> skill to "notice" a thing you used to have access to, is now
>>>> owned by root. That may not be an accident! It may mean
>>>> a mount point in a complex mount structure, has just "broken loose".
>>>>
>>>> /etc/fstab   <=== how the administrator controls manual mounts
>>>>
>>>> //etc/mtab   <=== a record, of the current set of mounts
>>>>
>>>> cat /etc/mtab  <=== use this command, to see what the OS has been
>>>> up to.
>>>>                      You might be shocked at the mess in Ubuntu,
>>>> for example.
>>>>
>>>> There are also standards involved, so the structure is
>>>> standardized with usage in Unix and Linux. There are occasional
>>>> things which don't always follow the rules. Sometimes the packages
>>>> you install, are in /opt. But not everything does that. Only
>>>> some of the packages do. And /opt might be more "popular"
>>>> on some other platform, and you're only getting things packaged
>>>> that way for fun.
>>>>
>>>> On occasion, you may install a package, and then when you typed
>>>> the command you expected to be present, it's not there! That's
>>>> because maybe /opt is not in your $PATH. You may need to add a path
>>>> component, into your $PATH, so the executable can be found. Maybe
>>>> the needed path component is /opt/something/bin for example.
>>>>
>>>> Always expect the unexpected. If you can fix something in five
>>>> minutes yourself, it saves wasting two days waiting for us to
>>>> guess what broke :-)
>>>
>>> Yes, same for TRYING the file a bug.
>>> For starters, it is impossible to do so.
>>> and IF you manage to do it anyway, nobody cares.
>>>>
>>>>     Paul
>>>
>> I agree Linux Mint has its share of problems with usb at the top, but
>> I will continue to use it instead of the m$ alternatives. It is a
>> great system that can compete with the m$$$$$$$ way. I like to think
>> that as computers evolve and as new knowledge is acquired eventually
>> most of these problems will go away.
>
> I gave up that idea, the utter insanity and chaos in the linux society
> make sure things will never be solved.
>
>
Perhaps it is human nature or human nature dumbed down with modern day
foods, but when it comes to innovation you never know when a new
Beethoven will be born to the computer scene. The insanity you speak of
is manifesting not only in the Linux society but in society in general
as we approach greater wars and destruction's.

Pages:12
server_pubkey.txt

rocksolid light 0.9.7
clearnet tor