Battery died during "mintupdate" update in 18.3
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions use the other forums in the support section.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions use the other forums in the support section.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Battery died during "mintupdate" update in 18.3
I was running 18.3 perfectly and I saw a level 1 mintupdate update. It was downloading/installing when the battery died. Now the laptop boots to a balck screen that says initramfs.
I created a live LM19 usb. I figured I could just upgrade to LM19 from the usb, but instead, after LM19 loads from the usb it reboots after a minute or two and won't complete the LM19 installation.
Is there any way to go back to 18.3 or else upgrade to 19 at this point, or is the hard drive completely broken?
Thinkpad T410s with an ssd.
I created a live LM19 usb. I figured I could just upgrade to LM19 from the usb, but instead, after LM19 loads from the usb it reboots after a minute or two and won't complete the LM19 installation.
Is there any way to go back to 18.3 or else upgrade to 19 at this point, or is the hard drive completely broken?
Thinkpad T410s with an ssd.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Battery died during "mintupdate" update in 18.3
the Same Rule applies for Both the Windows & the Linux Systems:
- when applying any updates - ensure the machine is Mains Powered ..
from that Live LM19 usb, can you use the Gparted program,
and paste a screen_shot of the SSD partitions - back here ?
- when applying any updates - ensure the machine is Mains Powered ..
from that Live LM19 usb, can you use the Gparted program,
and paste a screen_shot of the SSD partitions - back here ?
Please edit your original post title to include [SOLVED] - when your problem is solved!
and DO LOOK at those Unanswered Topics - - you may be able to answer some!.
Re: Battery died during "mintupdate" update in 18.3
The dpkg system takes extra care to ensure the OS remains intact when new packages are being installed. Later, it might complain that there are packages partially installed, but not a crash to a busybox boot. That's more likely the OS-root file system interrupted mid-write and needing a repair that can't be handled without deleting something. Linux won't do that without a human driving.
From the initramfs prompt, there's usually a hint about what went wrong.
You can try a simple
You can do an fsck from the initramfs prompt, if you know which device has a problem...
From the initramfs prompt, there's usually a hint about what went wrong.
You can try a simple
exit
command to resume the boot, or repeat the failure.You can do an fsck from the initramfs prompt, if you know which device has a problem...
fsck /dev/sda1
### Check the file system in /dev/sda1Re: Battery died during "mintupdate" update in 18.3
I changed the boot order in order to boot from the live usb. Without the usb plugged in now it boots to a blank screen with a cursor/underscore flashing. I tried changing the boot order back to the original order, but to no avail. So I can't get back to the initramfs prompt it seems.Mute Ant wrote: ⤴Thu Jul 19, 2018 5:05 am The dpkg system takes extra care to ensure the OS remains intact when new packages are being installed. Later, it might complain that there are packages partially installed, but not a crash to a busybox boot. That's more likely the OS-root file system interrupted mid-write and needing a repair that can't be handled without deleting something. Linux won't do that without a human driving.
From the initramfs prompt, there's usually a hint about what went wrong.
You can try a simpleexit
command to resume the boot, or repeat the failure.
You can do an fsck from the initramfs prompt, if you know which device has a problem...
fsck /dev/sda1
### Check the file system in /dev/sda1
I seem to remember reading something on the screen about /dev/sda1 errors when it was booting to the initramfs prompt.
Do you have a suggestion?
Re: Battery died during "mintupdate" update in 18.3
You could run the check-repair on /dev/sda1 from your live USB. Launch gparted and right-click on the partition and choose "Check disk" and then "Apply" from the toolbar. Reboot and see if this has resolved the issue.
Re: Battery died during "mintupdate" update in 18.3
/dev/sda1 appears to have only 1.87GiB of data... I don't think that's enough to be a working Mint, with or without errors.
Re: Battery died during "mintupdate" update in 18.3
ah no - - that's a Standard Ubuntu Installation:
- sda1 = 107.44Gb
- sda2 & sda5 = 11.80Gb
bog standard Ubuntu install.
that 1.87 GB is the Used Portion of sda1 . .
- sda1 = 107.44Gb
- sda2 & sda5 = 11.80Gb
bog standard Ubuntu install.
that 1.87 GB is the Used Portion of sda1 . .
Please edit your original post title to include [SOLVED] - when your problem is solved!
and DO LOOK at those Unanswered Topics - - you may be able to answer some!.
Re: Battery died during "mintupdate" update in 18.3
Re: Battery died during "mintupdate" update in 18.3
"...it did not work..." Well no, there is only half an OS in /dev/sda1, unless the gparted display changed. I suggest...
o Live Session memtest to confirm the motherboard chips are all working.
o Live Session disks accessory to check the drive's SMART is still saying "Disk is okay".
o Install Mint, again.
o Don't update anything, just run the installation for a day and wait for something horrible to happen.
o Live Session memtest to confirm the motherboard chips are all working.
o Live Session disks accessory to check the drive's SMART is still saying "Disk is okay".
o Install Mint, again.
o Don't update anything, just run the installation for a day and wait for something horrible to happen.
Re: Battery died during "mintupdate" update in 18.3
Next time, you might want to create a separate /home partition
Re: Battery died during "mintupdate" update in 18.3
I wasn't sure how to go from a Live Session to memtest, so I enabled Extended Memory Test during startup. In the Live Session in /boot/grub there are two files both of which are empty: gfxblacklist.txt and unicode.pf2Mute Ant wrote: ⤴Fri Jul 20, 2018 6:09 pm "...it did not work..." Well no, there is only half an OS in /dev/sda1, unless the gparted display changed. I suggest...
o Live Session memtest to confirm the motherboard chips are all working.
o Live Session disks accessory to check the drive's SMART is still saying "Disk is okay".
o Install Mint, again.
o Don't update anything, just run the installation for a day and wait for something horrible to happen.
Under disks the ssd says "Disk is Ok".
Booted back into a Live Session to re-install. Still re-booted as before before completing the installation. Same issue.
Re: Battery died during "mintupdate" update in 18.3
There's something specifically wrong with your machine or your burned ISO if the standard distribution won't complete an installation. Mostly an install run is just copying files out of the squashed live system into a hard drive partition, nothing risky or exciting.
The DVD Live Session boot gives a countdown timer where you can use up-down to select a boot mode. It looks something like...
/usr/lib/memtest86+/memtest86+.iso ### ISO 9660 CD-ROM filesystem data 'MT501' (bootable)
The DVD Live Session boot gives a countdown timer where you can use up-down to select a boot mode. It looks something like...
- Try Linux Mint
Try Compatibility Mode
OEM Install
Check Media Integrity
Test Memory
/usr/lib/memtest86+/memtest86+.iso ### ISO 9660 CD-ROM filesystem data 'MT501' (bootable)