No start after wipe

I made a big mistake, I stopped Wipe free disk space before it was
finished, and now the hd results full and it won't start. Tried to
repair using

sudo su -c "dpkg --configure -a"

sudo su -c "apt-get -f install"

but it didn't work. If I try full-upgrade it tells me that in
/var/cache/apt/archives/ there is no space.

I'm talking about Ubuntu 18.04. Is there a way to solve without a new
installation?


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

[Liam Proven]

On Fri, 12 Feb 2021 at 21:40, [hidden email] <[hidden email]> wrote:
>
> I'm talking about Ubuntu 18.04. Is there a way to solve without a new
> installation?

sudo apt clean

Then

sudo touch /forcefsck

And reboot.


--
Liam Proven – Profile: https://about.me/liamproven
Email: [hidden email] – gMail/gTalk/gHangouts: [hidden email]
Twitter/Facebook/LinkedIn/Flickr: lproven – Skype: liamproven
UK: [phone] – ČR (+ WhatsApp/Telegram/Signal): [phone]

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

I tried sudo apt clean but nothing happened. I will try forcefsck, thanx


Il 12/02/21 22:01, Liam Proven ha scritto:

> On Fri, 12 Feb 2021 at 21:40, [hidden email] <[hidden email]> wrote:
>> I'm talking about Ubuntu 18.04. Is there a way to solve without a new
>> installation?
> sudo apt clean
>
> Then
>
> sudo touch /forcefsck
>
> And reboot.
>
>

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

[Liam Proven]

On Fri, 12 Feb 2021 at 22:07, [hidden email] <[hidden email]> wrote:
>
> I tried sudo apt clean but nothing happened.

Please bottom-post on mailing lists, including this one. Your reply
goes _under_ the text you're replying to.

Thanks.

`apt clean` should not give any output but you should see a lot more
disk space afterwards.

> I will try forcefsck, thanx

I think it still works in 18.04. I am not sure it does any more on 20.xx :-(

More info here:
https://www.linuxuprising.com/2019/05/how-to-force-fsck-filesystem.html

--
Liam Proven – Profile: https://about.me/liamproven
Email: [hidden email] – gMail/gTalk/gHangouts: [hidden email]
Twitter/Facebook/LinkedIn/Flickr: lproven – Skype: liamproven
UK: [phone] – ČR (+ WhatsApp/Telegram/Signal): [phone]

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

Il 12/02/21 22:01, Liam Proven ha scritto:

> On Fri, 12 Feb 2021 at 21:40, [hidden email] <[hidden email]> wrote:
>> I'm talking about Ubuntu 18.04. Is there a way to solve without a new
>> installation?
> sudo apt clean
>
> Then
>
> sudo touch /forcefsck
>
> And reboot.
>
>

Tried it from recovery mode, apparently nothing happened, then I gave
reboot, but after rebooting it stops at the line

"Started GNOME Display Manager .nerate Color Profiles....tem changes.po
link was shut down"

When the problemes began it told about errors in Network Name and
Network Syncronization. After I tried almost all the possibilities in
recovery mode, such errors disappeared, but arriving on that line,
cursor goes on flashing and the disk stops working


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

[Tom H-4]

On Fri, Feb 12, 2021 at 10:03 PM Liam Proven <[hidden email]>
wrote:

> On Fri, 12 Feb 2021 at 21:40, [hidden email]
> <[hidden email]> wrote:
>>
>> I'm talking about Ubuntu 18.04. Is there a way to solve without
>> a new installation?
>
> sudo apt clean
>
> Then
>
> sudo touch /forcefsck
>
> And reboot.

It's probably better to use the systemd kernel cmdline variable
"fsck.mode=force" in case "/forcefsck" is obsoleted in the future.

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

Il 15/02/21 11:54, Tom H ha scritto:
> It's probably better to use the systemd kernel cmdline variable
> "fsck.mode=force" in case "/forcefsck" is obsoleted in the future.
>
I mounted another hd with new installation, but still trying to recover
the old one, I'll try this, thanx

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

[Liam Proven]

On Mon, 15 Feb 2021 at 17:44, [hidden email] <[hidden email]> wrote:

> I mounted another hd with new installation, but still trying to recover
> the old one, I'll try this, thanx

That works. ;-)

Of course you can also just boot off a USB key, or a CD/DVD, and use
that to check/repair your filesystems.

--
Liam Proven – Profile: https://about.me/liamproven
Email: [hidden email] – gMail/gTalk/gHangouts: [hidden email]
Twitter/Facebook/LinkedIn/Flickr: lproven – Skype: liamproven
UK: [phone] – ČR (+ WhatsApp/Telegram/Signal): [phone]

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

Il 16/02/21 17:10, Liam Proven ha scritto:
>
> That works. ;-)
>
> Of course you can also just boot off a USB key, or a CD/DVD, and use
> that to check/repair your filesystems.
>
I already tried the usb, but I wasn't able to solve. Actually I'm using
old hd as storage, having all my datas safe. But I would like to learn
how to solve this error I made. Thanx to all for helping ;)

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users