Public bug reported:
norvel@norvel4-ThinkPad-T460:~$ apt-cache policy gnome-disk-utility
gnome-disk-utility:
Installed: 42.0-1ubuntu1
Candidate: 42.0-1ubuntu1
Version table:
*** 42.0-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/
By burnout or overload of USB I mean I like stored more than that 2.1TB
stick could hold and if it helps it is now a drive not recognized as
being there to an extent of being usable but recognized as existing
maybe or maybe not, maybe.
--
You received this bug notification because you are a membe
I now remember I got USBs at time of reinstalling OS. That means that
all USB operations were after reinstalling. I now think order was
reinstall OS, check size, reformat USB, rsync to USB and burn out, then
reformatting another USB and checking. Feel free to check like my logs
on this but I think
By memory I know I overloaded a 2.1TB USB some time. I had a previous OS
by same USB bootable thing and almost same setup. I know I used rsync
with no exclude or -x or --one-file-system to overload that USB. I think
I overloaded it BEFORE reinstalling OS. I think order was overload USB,
reinstall O
Public bug reported:
I reformatted to NTFS on another computer, I then reformatted to ext4,
could not write, then reformatted some and some took ownership, almost
always "read only". After all that and always naming it "UbuntuFilesXE"
I have a large /media/norvel/UbuntuFilesXE part of like my syst
