Comment 109 for bug 1922342

My thumb-drive K (what was used in #107 & #101) which contains Ubuntu 22.04 LTS (20220416) resulted in

PLEASE NOTE: I just noted the ISO date shows it wasn't the released image.. It'll be the last daily/final/RC i actually used in testing... I'd expect 20220419 for the released ISO. I don't expect it'll impair these results though.

(parts of lsblk & blkid are included... I'm not sure the provided command xorriso contains I expected)

sdb 8:16 1 7.5G 0 disk
├─sdb1 8:17 1 3.4G 0 part /media/guiverc/Ubuntu 22.04 LTS amd64
├─sdb2 8:18 1 4.1M 0 part
├─sdb3 8:19 1 300K 0 part
└─sdb4 8:20 1 4G 0 part /media/guiverc/writable
sr0 11:0 1 1024M 0 rom

guiverc@d960-ubu2:~/uwn/issues/735$ xorriso -indev /dev/sdb -report_system_area plain
xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project.

xorriso : FAILURE : Drive address '/dev/sdb' rejected because: not MMC and -drive_class 'caution' '/dev'
xorriso : HINT : If the address is a legitimate target, prepend "stdio:"
xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE'
guiverc@d960-ubu2:~/uwn/issues/735$ lsblk^Crriso -index /dev/sdb -report_system_area plain
guiverc@d960-ubu2:~/uwn/issues/735$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
.. redacting loop devices & my sda disk
sdb 8:16 1 7.5G 0 disk
├─sdb1 8:17 1 3.4G 0 part /media/guiverc/Ubuntu 22.04 LTS amd64
├─sdb2 8:18 1 4.1M 0 part
├─sdb3 8:19 1 300K 0 part
└─sdb4 8:20 1 4G 0 part /media/guiverc/writable

-- I stopped at this point & haven't performed
> This is obviously one of the machines which demand a boot flag in MBR. Does it boot after you (rawly and naughtily) set the boot flag to MBR

Please advise if I should continue, or other (the xorriso output didn't appear right to me)