Unable to boot Debian 9.0

[entropic]

Hi i'm pretty much a Linux/Debian newbie and also on this forum so i hope this is the right place to ask my question.
Thing is i started a dist-upgrade ( apt-get dist-upgrade) but at some point it just stopped and as i tried to boot debian again it returned a

fsck.ext4: unable to resolve 'UUID=[alphanumerical number]
fsck died with exit status 8

After that i tried to check with the command "less" for a error log in var/log/fsck/checkfs but i couldn't go any further.
I just got the "fsck.ext4: unable to resolve UUID" line back.
So could someone help me and give me a hint?
thank you

[NFT5]

Please post up:

1. The complete contents of /etc/fstab
2. The output of

Code: Select all

sudo blkid

3. The contents of /var/log/fsck/checkfs

[entropic]

/etc/fstab content is:

<file system> <mount point> <type> <options> <dump> <pass>
/ was on /dev/sda7 during installation
UUID=fa29afbe-c561-41e3-82b4-a1fe386783cd / ext4 errors=remount-ro 0 1
# /home was on /dev/sda9/ during installation
UUID=d8b261f4-ad23-4b6e-9c49-ad7d0c6bfae4 /home ext4 defaults 0 2
#swap was on /dev/sda8 during installation
UUID=28bbc928-c603-4814-8400b7359f3f none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660

Then the sudo blkid command:

/dev/sd8= UUID="22a88e74-3963-afbe-16159d63a552" TYPE="ext4"
/dev/sda1:LABEL="Recovery" UUID="46042E69042E5BE5" TYPE="ntfs" //i think it's windows recovery partition
/dev/sda2: LABEL= "ESP" UUID=D830-E4C3" TYPE=vfat
/dev/sda4 LABEL= "acer" UUID [some numbers] TYPE=ntfs" // windows
/dev/sda5: UUID= fa29afbe-c561-41e3-82b4-a1fe386783cd" TYPE=ext4
/dev/sda6
/dev/sda7 Those are both TYPE=ntfs so i suppose you don't need it
/dev/sda9 UUID="fb1bdffc-93fa-4389-9420-6d889c452fc6" TYPE=swap
/dev/sda10 UUID="ed4f8110-8b85-4a84-84bb-027e47f5d20a TYPE= ext4
/dev/sdb1: UUID=9016-4ef8" TYPE =vfat

and /var/log/fsck less checkfs
Log of fsck -C -R -A -a

fsck from util-linux 2.20.1
fsck.ext4: Unable to resolve `UUID=d8b261f4-ad23-4b6e-9c49-ad7d0c6bfae4
fsck died with exit status 8


So i can see there is a problem with ext4 is that right? How can i fix it, where should i look?
Thank you

p.s.
i couldn't ulpload any screenshot sorry for that

[dasein]

Ok, this is way more than a dist-upgrade gone bad. What else did you do? You need to tell the whole story honestly in order for anyone to help you.

[entropic]

Well this is what i did:
dist-upgrade following a guide on the web
while the upgrade the system asked me the permit to stop whitout asking again some "libraries"(?) i pressed YES
after a while the system just got stuck like frozen so i waited a bit (20 min) and just shut down
at the reboot... this is what i got

I suppose i shouldn't shut down

[dasein]

Perhaps someone with more patience will come along and help you. But you will still have to be honest with them.

Good luck.

[entropic]

Look i have been honest,i really thought this was an upgrading issuse since the system got stuck while the upgrading process. Only now after keeping reading the debian documentation i undrestand that maybe i shoudn't shut the system down like i did. What i mean is that if i "hide" something it's in complete "bona fide" and not on purpose.

Anyway i appreciate you took your time to answer me and thank you for your patience.
I'll keep looking for a way to fix it and let know if i'll find a solution.

Just a question : how and why you can tell this is a different matter than upgrading where do you can "read" this? I'm asking because i want to learn "debugging" so i will appreciate if someone can tell me where and what i have to look.
thank you again.

[GarryRicketson]

I started to reply, but then deleted it, but any way:

Postby entropic » 2017-07-04 06:07
Well this is what i did:
dist-upgrade following a guide on the web

This is to vague, What guide, where ?

What i mean is that if i "hide" something it's in complete "bona fide" and not on purpose.

It is not so much that any one thinks you are deliberately trying to hide anything,
but you are not giving any real details.
Use code boxes, to show exactly what commands you used to do the
upgrade, what version of Debian you upgraded from ?
Shutting down the computer in the middle of it probably has left it
in a UN-use able state.

i want to learn "debugging" so i will appreciate if someone can tell me where and what i have to look.

The first step in trouble shooting is to have notes, on exactly what you did.
Did you take any notes ?
How to trouble shoot a failed upgrade on Debian 9
=====================================
https://www.debian.org/doc/manuals/debi ... te.en.html
====================
i want to learn "debugging" on a Debian system


Also now, there are starting to be various questions, 1 question at a time
is better.
Your sources.list file, located in :

Code: Select all

 /etc/apt/sources.list

may be revealing.
=============

Just a question : how and why you can tell this is a different matter than upgrading where do you can "read" this?

Because on a correctly configured system, and if it does not have any packages
from out side of the Debian repositories, the upgrade should go smoothly.
There could be other factors involved, but without any details on the original system, we can only guess. When people do not include any details, it appears
they are "hiding"something, maybe it is not deliberate, but that still does not
change the fact that the person with the problem is not telling everything we need to know.
I also don't have the patience to play the "pry the details" game, and 20 questions,.. try looking up some of the questions by doing some searches.

Well this is what i did:
dist-upgrade following a guide on the web

Knowing what guide you followed, from where would help , there are many blogs and guides, and many are totally wrong.
Other are good, but you might not have followed the steps accurately, we don't know, because you have not told us exactly what steps you followed.
=============
Probably the best thing you can do, use the backup you made before trying to upgrade to restore the system to it's original working state.
If you did not make a good back up before trying to upgrade, that indicates
you also did not really read any good documentation, because all of the good
documentation tells the person to make a good back up first.
Guess that is all for now. Multiple questions are bad, because it leads to overly long posts, trying to explain each question.
========== edited ========

p.s.
i couldn't ulpload any screenshot sorry for that

Usually screen shots are useless, and not necessary, but if you really
think you must show a screen shot :
http://forums.debian.net/viewtopic.php?f=16&t=123831
and also please read:
http://forums.debian.net/viewtopic.php?f=12&t=131097

[dasein]

It is not so much that any one thinks you are deliberately trying to hide anything,

I do, and quite unapologetically so. Again, this is very obviously not a "dist-upgrade" gone wrong. Without an honest and complete report of what actually preceded it, there is no point in engaging the OP.

Shutting down the computer in the middle of it probably has left it in a UN-use able state.

Also not the problem.

I also don't have the patience to play the "pry the details" game, and 20 questions,..

Especially when "20 questions" yields 20 incomplete/dishonest answers.

Just a question : how and why you can tell this is a different matter than upgrading where do you can "read" this?

Because on a correctly configured system... the upgrade should go smoothly.

Again, no. A focused 30 seconds spent comparing fstab to blkid output makes it clear: partitions have been moved, reformatted, and generally mucked with, none of which is part of a dist-upgrade.

I am so done here.

[entropic]

Again, no. A focused 30 seconds spent comparing fstab to blkid output makes it clear: partitions have been moved, reformatted, and generally mucked with, none of which is part of a dist-upgrade. (No wonder I don't believe the OP, huh?)

Belive me i wish i were able to do all this (move partitions , reformat etc etc) all i did was to run sudo apt-get update && sudo apt-get upgrade at the end of this process the system asked me to use autoremove (which i did) and then the infamous dist-upgrade after that i dint't type any command .
Just like i said

Those are all the notes that i took at the time, i know was a mistake, apparently i did a lot of mistakes but i'm telling you about.
I would like you to quit this "disonesty discussion" please , if your time isn't worth then fine , but i'm not liyng and i'm telling you all what i know i did . I may have done a lot of stupid mistakes like no backups ...cool i'm an idiot and you don't have patience with me ? It's fine i accept that just stop insulting people, thank you.


To be more specific i got a empty space warnig at some point of the upgrading process but i just closed the pop up and nothing happened.

I will go through the advice GarryRicketson did give to me and post here the results if someone will help fine otherwise ... i will reinstall all again.
thanks

[Zjho]

i will reinstall all again.

Wise move for any Linux newbie, dist-upgrades should carry an "over 18 re-installs first only" rating.

[pylkko]

just stop insulting people, thank you.

Oh come on! Insult?

I would like you to quit this "disonesty discussion" please

OK, but this doesn't help:

To be more specific i got a empty space warnig at some point of the upgrading process but i just closed the pop up and nothing happened.

Anything else?

Can you post output of

Code: Select all

df -h