Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I’m not the most experienced Linux user, and it’s been a while since I used it regularly, but recently my MacBook was damaged and I’ve been using my old laptop running Kali Linux 2017.3 sincd. I had been ignoring the OS telling me that there were updates to be installed, but today I finally decided to do the updates. It took a while, then when my computer rebooted it just sat at the screen that says /dev/sda1 437987/5812678 (normally appears right before the OS finishes loading). I rebooted it into recovery mode and got a root shell and have tried a few commands, but like I said, it’s been a while and I can’t afford to ruin anything (not backed up yet). The pic I’ve included shows most of the commands I’ve tried. It looks to me like the root file system can’t be resolved to its UUID, or something of that nature. It won’t let me run fsck or remount the filesystem as rw so I can create a /forcefsck file. In both cases it says fsck.ext4: Unable to resolve ‘UUID=4db2cdd6-c6c9-4be9-9a5a-105c17f4748’. Any advice is appreciated.
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
Rep:
Quote:
Originally Posted by B3PO
I’m not the most experienced Linux user, and it’s been a while since I used it regularly, but recently my MacBook was damaged and I’ve been using my old laptop running Kali Linux 2017.3 sincd. I had been ignoring the OS telling me that there were updates to be installed, but today I finally decided to do the updates. It took a while, then when my computer rebooted it just sat at the screen that says /dev/sda1 437987/5812678 (normally appears right before the OS finishes loading). I rebooted it into recovery mode and got a root shell and have tried a few commands, but like I said, it’s been a while and I can’t afford to ruin anything (not backed up yet). The pic I’ve included shows most of the commands I’ve tried. It looks to me like the root file system can’t be resolved to its UUID, or something of that nature. It won’t let me run fsck or remount the filesystem as rw so I can create a /forcefsck file. In both cases it says fsck.ext4: Unable to resolve ‘UUID=4db2cdd6-c6c9-4be9-9a5a-105c17f4748’. Any advice is appreciated.
Firstly, it's not real easy to read your post like it is.
As I said, it’s been a while since I used Linux regularly (as in a couple years). When I put Kali on tis PC, I was using it regularly in school for penetration-testing purposes (intended pupose you mentioned), but have forgotten much since that time. In any case, I could easily be having this same problem on Ubuntu, as they are both Debian, so I understand your point but I still have this problem and need help solving it. If you need more information I will provide it, but please look at what I’ve already provided first.
Once it gets this far, the screen flashes black repeatedly, as if it keeps trying and failing over and over again. The screen flashing happens for both versions, and when trying to boot in recovery mode.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.