[ubuntu-za] 14.04 crash during update
deon1964 at googlemail.com
Tue Jul 12 08:25:40 UTC 2016
Just some more information,
I was not actually upgrading to 16.04 but running normal 14.04 updates when
the issue happened.
Using the live CD to try and repair the installation I never got the optoin
Only options were new install or install 14.04 alongside 14.04
I have now installed 16.04 on a seperate partition and can recover my
documents on 14.04. Grub also does not see the 14.04 installation.
Will go back to Wiki and see if there is more information available.
On 12 July 2016 at 08:40, Xandor Schiefer <me at xandor.co.za> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> Hi Raoul,
> > You end up with antiquated software and no real updates, save for a
> > few kernel or other security updates
> That's pretty much the same scenario as Debian Stable. It's not uncommon
> to have 2+ year old software in Debian Stable (barring security updates).
> Don't mean to be a buzzkill but it doesn't make sense to "put forward"
> Debian Stable as a way to avoid old versions of software, compared to
> Ubuntu LTS.
> This can be ameliorated by using debian-backports, but that can also
> introduce instability.
> The same reason you want Debian Stable is why people wants LTS releases
> for their Desktops. Also if they've got older hardware it makes sense to
> stick with Ubuntu LTS.
> Ubuntu is forked off Debian Testing every 6 months, feature frozen, bugs
> worked out (more or less), and then released.
> For Deon:
> That wiki link Raoul sent you should help you out. Read the Update
> Failure part. Basically you'll be booting into a liveCD system, mounting
> your old partitions (the wiki assumes you had a single partition—adjust
> as necessary), mounting the dev, proc, and sys live file systems in a
> second place, and then chrooting into your old system.
> Chroot is a way to have your current kernel (in this case the running
> liveCD kernel) think and act like it's using a different file system
> (your unbootable system's).
> Now you're essentially booted into your system again (more or less).
> - From here you can diagnose problems. Like the wiki suggests, I would
> start with update & upgrade. If that works well and you still cannot
> boot, you'll have to investigate your specific issue in more detail.
> E.g. perhaps you'd need to run update-grub again (after chrooting
> again). Perhaps something else (depends on the specific issue).
> I've used this technique (liveCD + chrooting) to recover from epic TIFUs
> like: sudo chown -R user:user /
> or: sudo chmod -R 777 /
> Reinstalling is the nuclear option. It will give you what you want, and
> will probably do so more quickly in some cases than trying to recover a
> severely mangled system. But, it won't really teach you anything about
> how Linux works, what options are available, learn new skills that are
> useful in other situations also, etc. Teach a man to fish and all that
> In any case Matthew's comments about partitioning are good sense. If you
> do end up reinstalling dig into the install process a little and use
> several partitions if you don't already.
> Kind regards,
> Xandor Schiefer
> 079 706 5620
> This communication may be unlawfully collected and stored by the
> National Security Agency (NSA) and other organizations in secret. The
> parties to this email do not consent to the retrieving or storing of
> this communication and any related metadata, as well as printing,
> copying, re-transmitting, disseminating, or otherwise using it. If you
> believe you have received this communication in error, please delete
> it immediately.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
> -----END PGP SIGNATURE-----
> ubuntu-za mailing list
> ubuntu-za at lists.ubuntu.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ubuntu-za