3 added 5 characters in body
source | link

I think the cause is a power shortage during the fsck/clean part where it only says 'dev/sda1/ : recovering journal' .

The computer will reach fsck clean and itllit'll say recovering journals"recovering journals", so and so many files checked, the screen will flash and try to start ubuntuUbuntu and go right back, in an infinite loop.

I would assume something wasntwasn't correctly written during shut down and that there are some corrupt files causing this.

I've tried going into recovery mode and doing everything there, dpkg repair and clean give me the error apt-get: relocation error somename not defined in libstdc++.so.6. fsck doesntdoesn't give any errors when in the recovery mode prompt. Unfortunately, my ubuntuUbuntu knowledge is limited, so do I have any options here? Do I have to reinstall my osOS?

I think the cause is a power shortage during the fsck/clean part where it only says 'dev/sda1/ : recovering journal' .

The computer will reach fsck clean and itll say recovering journals, so and so many files checked, the screen will flash and try to start ubuntu and go right back, in an infinite loop.

I would assume something wasnt correctly written during shut down and that there are some corrupt files causing this.

I've tried going into recovery mode and doing everything there, dpkg repair and clean give me the error apt-get: relocation error somename not defined in libstdc++.so.6. fsck doesnt give any errors when in the recovery mode prompt. Unfortunately, my ubuntu knowledge is limited, so do I have any options here? Do I have to reinstall my os?

I think the cause is a power shortage during the fsck/clean part where it only says 'dev/sda1/ : recovering journal' .

The computer will reach fsck clean and it'll say "recovering journals", so and so many files checked, the screen will flash and try to start Ubuntu and go right back, in an infinite loop.

I would assume something wasn't correctly written during shut down and that there are some corrupt files causing this.

I've tried going into recovery mode and doing everything there, dpkg repair and clean give me the error apt-get: relocation error somename not defined in libstdc++.so.6. fsck doesn't give any errors when in the recovery mode prompt. Unfortunately, my Ubuntu knowledge is limited, so do I have any options here? Do I have to reinstall my OS?

2 added 6 characters in body
source | link

I think the cause is a power shortage during the fsck/clean part where it only says 'dev/sda1/ : recovering journal' .

The computer will reach fsck clean and itll say recovering journals, so and so many files checked, the screen will flash and try to start ubuntu and go right back, in an infinite loop.

I would assume something wasnt correctly written during shut down and that there are some corrupt files causing this.

I've tried going into recovery moderecovery mode and doing everything there, fsck says OK but when i try to do anything that requires apt-get, dpkg repair and clean give me the error apt-get: relocation error somename not defined in libstdc++.so.6.. shows up. So something is wrongfsck doesnt give any errors when in the recovery mode prompt. Unfortunately, my ubuntu knowledge is limited, so do I have any options here? Do I have to reinstall my os?

I think the cause is a power shortage during the fsck/clean part where it only says 'dev/sda1/ : recovering journal' .

The computer will reach fsck clean and itll say recovering journals, so and so many files checked, the screen will flash and try to start ubuntu and go right back, in an infinite loop.

I would assume something wasnt correctly written during shut down and that there are some corrupt files causing this.

I've tried going into recovery mode and doing everything there, fsck says OK but when i try to do anything that requires apt-get, the error apt-get: relocation error somename not defined in libstdc++.so.6.. shows up. So something is wrong. Unfortunately, my ubuntu knowledge is limited, so do I have any options here? Do I have to reinstall my os?

I think the cause is a power shortage during the fsck/clean part where it only says 'dev/sda1/ : recovering journal' .

The computer will reach fsck clean and itll say recovering journals, so and so many files checked, the screen will flash and try to start ubuntu and go right back, in an infinite loop.

I would assume something wasnt correctly written during shut down and that there are some corrupt files causing this.

I've tried going into recovery mode and doing everything there, dpkg repair and clean give me the error apt-get: relocation error somename not defined in libstdc++.so.6. fsck doesnt give any errors when in the recovery mode prompt. Unfortunately, my ubuntu knowledge is limited, so do I have any options here? Do I have to reinstall my os?

1
source | link

Stuck in bootloop after upgrade to Ubuntu 16.04LTS

I think the cause is a power shortage during the fsck/clean part where it only says 'dev/sda1/ : recovering journal' .

The computer will reach fsck clean and itll say recovering journals, so and so many files checked, the screen will flash and try to start ubuntu and go right back, in an infinite loop.

I would assume something wasnt correctly written during shut down and that there are some corrupt files causing this.

I've tried going into recovery mode and doing everything there, fsck says OK but when i try to do anything that requires apt-get, the error apt-get: relocation error somename not defined in libstdc++.so.6.. shows up. So something is wrong. Unfortunately, my ubuntu knowledge is limited, so do I have any options here? Do I have to reinstall my os?