Flidas fails to boot

2 respostas [Última entrada]
amenex
Desconectado
Joined: 01/04/2015

After a few attempts to run simultaneous nmap scans that produced several
core dumps, my formerly reliable Trisquel_8 will not boot, stopping
with a blinking "-" in the upper left hand corner of the screen.

Forced at last to learn something about "Recovery Mode" I consulted the
Ubuntu Wiki on the subject of Recovery Mode and found these hints:

From the Recovery Mode menu, choose "Drop to root shell prompt."
Execute mount -o remount rw/ followed by mount --all

Realizing that the above steps may have something to do with one of the
lines of text that flashed across the screen during the startup of the
Recovery Mode process:
Failed to create static drive nodes in /dev
So the Ubuntu Wiki's instructions make some sense.

Upon Selecting "Continue boot process" in Recovery Mode, I now see the
blinking "-" in the upper left hand corner of the screen, accompanied
by series of colorful raster lines scrolling up the screen and nothing
more.

Delving further into the matter, I discovered that [Fn + SysRq] gives
me a login prompt, and that the login accepts my credentials, but that
attempts to use sudo produce this admonishment:
sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set

That statement is one I had only seen once before after the aforementioned
core dumps.

In Recovery Mode, enabling networking gives access to nothing more than
127.0.0.1 and localhost; all other destinations are unreachable.

George Langford

Magic Banana

I am a member!

Conectado
Joined: 07/24/2010

Flidas' support ends next month: upgrade to Etiona! First of all, backup the user data from a live system. Then from that same live system, if you do not want a fresh install, try to 'chroot' in the installed system. https://help.ubuntu.com/community/Grub2/Installing#via_ChRoot describes the process in too many details: you probably use neither software RAID, nor LVM, nor bcache, etc. From the chroot environment, you should be able to upgrade to Etiona with 'sudo do-release-upgrade' or, if it does not work, with 'sudo do-release-upgrade -d' or even 'sudo sed -i s/flidas/etiona/ /etc/apt/sources.list && sudo apt update && sudo apt full-upgrade'.

amenex
Desconectado
Joined: 01/04/2015

First, the bad news: Flidas is going into exile next month.
Second, the good news: Flidas had been my dependable rock operating system, but I've just
found out why Etiona had been freezing at the worst moments: I'd been running two nmap
scans at once, e.g. nmap -v -A -Pn 94.23.177.235 in Terminal 1; and
nmap -v -A 148.251.69.139 in Terminal 2

That's a bad move, as conflicts occur between the two scripts, leading to core dumps in
the present context in Flidas, and freezes of the Etiona operating system.

Freezes do not occur in Etiona when running just one of the aforementioned nmap scripts
at a time; and I've learned the hard way to save any open file before commencing _any_
script that I've written.

That makes Flidas redundant on this computer.