"$d_SysMaint""0_LMDE notes.txt"
wwwBillHowell.ca  29Jun2019 initial






08********08
#] ??Oct2023 


08********08
#] ??Oct2023 


08********08
#] ??Oct2023 


08********08
#] ??Oct2023 


08********08
#] 27Oct2023 lost LMDE Elsie setups & my downloaded programs !!?!?!??  NIGHTMARE for HALLOWEEN
see : 
    "$d_SysMaint"'LibreOffice/0_LibreOffice notes.txt'  
    "$d_SysMaint"'email programs/evolution email account settings.txt'
    "$d_SysMaint"'email programs/evolution notes.txt'

very old : 
    "$d_SysMaint"'Thunderbird/0_Thunderbird notes.txt'


08********08
24Mar2021 d_webSite - put on USB memory stick to avoid accidental [usage, edit, delete]s etc 
	of d_website rather than d_webRawe
1. just use gparted to reformat USB drive!!!
		rename partition to 'WebSite' 
2. $ sudo chown -R  bill:bill  '/media/bill/WebSite'  
3. $ mv  '/media/bill/Dell2/Website/'  '/media/bill/WebSite'  
		oops, copied as a subdir but I had '/media/bill/WebSite/'  


*****************
29Jun2019 SWAPPER inaccessible after LMDE crash

An error occurred while accessing 'Home', the system responded: The requested operation has failed: Error mounting /dev/sdb2 at /media/bill/SWAPPER: Command-line `mount -t "ext4" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdb2" "/media/bill/SWAPPER"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb2,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.

search "Linux and exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock"




GParted manual » Working with Partitions » Advanced Partition Actions »  Copying and Pasting a Partition

The copy of the partition has the same file system label and Universally Unique Identifier (UUID) as the source partition. This can cause a problem when booting, or when mount actions use the file system label or UUID to identify the partition.
The problem is that the operating system will randomly select to mount either the source, or the copy of the partition. For example, on the first mount action the source partition might be mounted. On the next mount action the copy of the partition might be mounted. Over time this random nature of partition mounting might make files seem to mysteriously appear or disappear depending upon which partition is mounted. Random mounting of the source or the copy of the partition might also cause severe data corruption or loss.
To avoid the problem you are advised to do one of the following:
After you have queued or applied the copy operation:
Change the UUID of either the source, or the copy of the partition. See Changing a Partition UUID.
If the file system label is not blank then change the file system label of either the source, or the copy of the partition. See Setting a Partition File System Label.
After you have applied the copy operation, delete or reformat the source partition.
Use some other method to ensure that the source partition and the copy of the partition are not used on the same computer at the same time. For example, if the copy of the partition is on a separate drive then remove the drive from the computer.


190629 09:40  No time for this now! - look at AFTER doing peer review!



# enddoc