@october262, thank you very much for detailed answer, it will be useful for the future when somebody get similar problem.
well, I concluded it is failed usb flash device, there was no problem at installation, I use this usb device many months and there was no problem, when i installed live and persistence I followed commands from kali tutorial and there was no problem. I tried also all usb ports on laptop, 2x usb 2.0 and 1x 3.0
This is for newbies who can get the same problem: solution is to make new linux baby, to buy new usb flash device, when you use usb device long time and it is written many times, it gets damaged and even if you reinstall/reimage Kali it can get problem again because it is already damaged. I ordered one usb device today for 35 euro, 1000MB/s reading speed and 900MB/s writing speed, kingston max 256GB. such usb cost more than 70 euro.
Here is what i tried before decision to make funeral for present SP MS 60 250GB usb flash kali linux:
So, first error before loosing desktop and getting black screen, I saw beside bluetooth icon:
/usr/share/kali-themes/xfce4-panel-genmon-vpnip.sh: input/output error
but it is not about one bad sh script, this shows that error is happening because of bad usb flash device.
Fixing the Black Screen
This is typically caused by graphics driver conflicts. During boot:
At the GRUB menu, select “Live system” and press e to edit boot parameters
In the linux line, add nouveau.modeset=0 before splash (for NVIDIA GPUs) or nomodeset (generic solution). For example:
… quiet nouveau.modeset=0 splash noeject …
Press Ctrl+X or F10 to boot
This disables problematic graphics drivers and should resolve the black screen.
re-image kali live usb partition /dev/sdb1 with old laptop ubuntu 18 (user dell), after Kali iso download…
sudo fdisk -l # or sudo lsblk -f
The first partition (sdb1) is iso9660 on USB, which is a read-only filesystem, so I cannot directly write to it. To replace the SquashFS file on that partition, I need to re-create the USB with the Kali ISO.
This command will overwrite only the first partition sdb1=ISO9660, leaving sdb2=FAT32 and sdb3=luks untouched.
sudo dd if=/home/dell/Desktop/kali-linux.iso of=/dev/sdb1 bs=4M status=progress conv=fdatasync
if you don’t have linux outside of usb flash, if you think you can do it in windows 11 for example, you will see that win11 can see only fat32 sdb2 boot partition, you will not see sdb2 ext4 and sdb3 luks encrypted partitions and you can not use rufus or balenaEtcher to recreate kali usb flash device = /dev/sdb1.
of course, after every try, I tried to reboot kali usb flash device and it failed… again I had problem with loosing dekstop…
checking second boot partition /dev/sdb2 fat32:
sudo lsblk -f
sudo fsck.vfat -n /dev/sdb2 # Check without repairing
if there is error, you can use repair command: sudo fsck.vfat -a /dev/sdb2
Then I tried to repair partition sdb3 (luks encrypted):
sudo fdisk -l
sudo cryptsetup luksOpen /dev/sdb3 my_usb2 # to open partition protected by password
sudo umount /dev/mapper/my_usb2 # e2fsck will not work with mounted partition
sudo e2fsck -b 32768 /dev/mapper/my_usb2
…
persistence was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
…persistence: ***** FILE SYSTEM WAS MODIFIED *****
persistence: 702812/14958592 files (1.1% non-contiguous), 41340202/59809838 blocks
sudo fdisk -l
sudo e2fsck -ycfv /dev/mapper/my_usb2 # this is very slow, 17% after 30 minutes
-y Assume “yes” to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
…checking for bad blocks (read only test)…
persistence: Updating bad block inode.
ext2fs_update_bb_inode: Ext2 file too big while updating bad block inode
persistence: ***** FILE SYSTEM WAS MODIFIED *****
rebooot aaand … after 2 minutes I lost desktop again and when i restarted laptop bios doesn’t see usb flash device any more, I tried 3 different usb ports but bios think this usb flash device should get funeral and new linux baby should be plugged in in usb port…
this error (Ext2 file too big while updating bad block inode) is saying that there are so many bad blocks that it can not be placed in ext4 partition or something like that, so, I had two choices: re-imaging whole usb again from zero with kali iso and risking that damaged usb fail again in the future or second choice: buy new usb device with enough storage and minimum 100MB/s writing speed. Kali must be updated every several weeks and if you have slow writing speed, you will wait 30 minutes to update Kali.
So, I made a choice, my laptop has one c-type usb port + USB port 3.0 with 10GB speed and I can buy new usb flash device and I found good one kingston 900MB/s writing speed 256GB…
