Thank you for investigating. The disk is old and I had defective sectors earlier. In a second try,
I installed using option 'Full disk' with formatting and that succeeded. Please close this report as done; no further inspection needed, thank you. By the way: using the freshly installed Ubuntu, getting a terminal finally did not succeed. This software is unusable for me, if I dont succed in that. A standard selector (left margin) is missing. I know, one has to search for 'term' (else you are hosed). Selecting that gave no final result; it tried to start up but dropped out finally. I want to use the Operating System and not to be fed (like a Win** dummy) with cannned food Nevertheless, thanks for achievements so far, R =================================================== On 3/29/21 4:17 AM, Chris Guiver wrote: > Thank you for taking the time to report this issue and helping to make > Ubuntu better. > > This problem appears to be related to hardware errors. I notice in the > logs > > Mar 29 00:47:53 ubuntu kernel: [ 1585.461476] sd 2:0:0:0: [sdb] tag#9 FAILED > Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s > Mar 29 00:47:53 ubuntu kernel: [ 1585.461518] sd 2:0:0:0: [sdb] tag#9 Sense > Key : Illegal Request [current] > Mar 29 00:47:53 ubuntu kernel: [ 1585.461531] sd 2:0:0:0: [sdb] tag#9 Add. > Sense: Invalid field in cdb > Mar 29 00:47:53 ubuntu kernel: [ 1585.461543] sd 2:0:0:0: [sdb] tag#9 CDB: > Write(10) 2a 08 0e 9a cd 60 00 00 08 00 > Mar 29 00:47:53 ubuntu kernel: [ 1585.461557] blk_update_request: critical > target error, dev sdb, sector 245026144 op 0x1:(WRITE) flags 0x20800 phys_seg > 1 prio class 0 > Mar 29 00:47:53 ubuntu kernel: [ 1585.461607] blk_update_request: critical > target error, dev sdb, sector 245026144 op 0x1:(WRITE) flags 0x20800 phys_seg > 1 prio class 0 > Mar 29 00:47:53 ubuntu kernel: [ 1585.461741] Aborting journal on device > sdb4-8. > Mar 29 00:47:53 ubuntu kernel: [ 1585.464411] EXT4-fs error (device sdb4): > ext4_journal_check_start:83: Detected aborted journal > Mar 29 00:47:53 ubuntu kernel: [ 1585.464421] EXT4-fs (sdb4): Remounting > filesystem read-only > Mar 29 00:47:53 ubuntu kernel: [ 1585.464720] EXT4-fs error (device sdb4): > ext4_journal_check_start:83: Detected aborted journal > > I've marked this bug as incomplete (due hardware issues), if you believe > I'm in error please leave a comment as to why, and you can return the > status to "New". > > I suggest you validate the health of your hardware (esp. disk by > checking it's SMART status using `smartctl`, `gnome-disks` or whichever > tool you prefer), and possibly the integrity of your partition table > (https://help.ubuntu.com/community/Smartmontools). If you're unfamiliar > with these, I suggest seeking support, options available can be seen at > https://discourse.ubuntu.com/t/finding-help/709 > > ** Changed in: ubuntu > Status: New => Incomplete > > ** Package changed: ubuntu => ubiquity (Ubuntu) > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921661 Title: Simply crashed when installing to a preformatted disk. thats ery unusual. Regards,RL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1921661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
