Trying to Install Lubuntu 18.04 over hosed-up 16.04 on 32G thumb drive

Bug #1833376 reported by David-E
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Lubuntu 16.04 worked fine for long time (12.9GB FAT32 in front for data to be accessible to Windows 7, then 16.89GB EXT4 Extended with 16GB Lubuntu 16.04 and 1GB Swap). Hadn't used or updated in quite a while so tried to install updates (to 16.04). Updates required reboot - but somehow it locked up. Only way to get it started again was to kill power and reboot - choosing thumb drive in boot loader. Every attempt gave Ubuntu options - I selected current Ubuntu and sometime the other baseline ubuntu options). Many attempts to fix but nothing worked. Finally got 18.04 installer download on disc and tried to install to thumb (that was this time). Instructions didn't seem to follow correctly = it asked if I wanted to re-partition - I said no - then when I clicked to install I was asked if I wanted to move the partitions with a picture of partitions. I said no again - but it seems like it tried to split the Lubuntu partition into two smaller partitions (at least that what it has now - so if that's what it did of course there probably wasn't room to install 18.04). +++ I will attempt to repartition the thumb myself (GPartEd) and then try again to load 18.04.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-15-generic i686
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: i386
CasperVersion: 1.394
Date: Tue Jun 18 23:36:46 2019
InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity initrd=/casper/initrd quiet splash ---
LiveMediaBuild: Lubuntu 18.04.2 LTS "Bionic Beaver" - Release i386 (20190210)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
David-E (desloat) wrote :
Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for taking the time to report this issue and helping to make Ubuntu better.

This package failure looks like it was caused by a corrupted file system, or device failure. eg. look in the logs and you'll see lots of messages like these :-

Jun 19 06:29:10 lubuntu kernel: [ 2913.701779] sr 7:0:0:0: [sr1] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jun 19 06:29:10 lubuntu kernel: [ 2913.701788] sr 7:0:0:0: [sr1] tag#0 Sense Key : Hardware Error [current]
Jun 19 06:29:10 lubuntu kernel: [ 2913.701795] sr 7:0:0:0: [sr1] tag#0 Add. Sense: Timeout on logical unit
Jun 19 06:29:10 lubuntu kernel: [ 2913.701803] sr 7:0:0:0: [sr1] tag#0 CDB: Read(10) 28 00 00 03 d0 ae 00 00 3c 00 00 00
Jun 19 06:29:10 lubuntu kernel: [ 2913.701808] print_req_error: critical target error, dev sr1, sector 1000120

Examining the information you have given us, this does not appear to be a useful bug report so I am closing it, as it appears to be a faulty device to me, thus I'll mark it as invalid. If you believe I'm in error, please leave a comment explaining why and change the status back to 'new'.

(did you 'check disk for defects' to ensure it wasn't a bad write of the ISO as per https://manual.lubuntu.me/1/1.3/installation.html)

Changed in ubiquity (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.