Software > Operating Systems and Porting
[NEWS] Debian
MauryG5:
In practice, now that I carefully read your procedure, I have already performed the deletion of the offending swap partition when all this happened to me and I thought it was enough but it wasn't. What I did not do, however, as I did not know, is the last part of the procedure or copy the new uuid number created with the new partition and copy it instead of the old one ... I have to try and let you know ok, thank you
MauryG5:
--- Quote from: xilinder on February 07, 2021, 01:33:01 pm ---Free advice (for what it's worth). This could fix the problem, or screw things up really bad.
The UUID of that partition in /dev/disk/by-uuid and /etc/fstab must be the same.
Open Gparted and select the proper swap partition. Then in the Partition Menu select swap-off and Apply that. Next, select the partition again and from the menu select Format and Cleared from the secondary menu.
Apply that. Now format the partition as Linux-swap, and apply. Then set swapon.
Select Information and Highlight the new uuid, you can use Ctrl + c to copy it and paste it into a text editor.
As root open /etc/fstab with a text editor, cut the old uuid number from the file and paste the new number in it's place and save the file.
Hi Xlinder, you are great! I applied everything you told me and solved the problem big time. Fedora now starts up smoothly and no longer hangs there for 1.30 minutes. Since you told me that the uuid number of etc / fstab must also be on dev / disk / by-uuid you have made me understand the whole problem. In practice he crashed because he did not find the correspondence of the swap partition, the number that was there of the new partition he had created before Debian and then when I deleted and reformatted it the first time, it no longer corresponded with the one contained in by-uuid and consequently he stopped at that point and finding no response then deactivated the swap partition. Now I have to do the same procedure on the other hardisk with another Fedora installed and restore that to return to normal. Thank you so much for your advice you were great!
Reboot. It's okay to curse me if things went very badly.
--- End quote ---
xilinder:
I noticed you are using the default desktop file manager for this problem.
May I suggest to you to install and try XFE and MC (Midnight Commander). Play with them for a while, especially for system and kernel work you might find them very handy.
Sometimes all you need is a bigger hammer. :)
MauryG5:
https://gitlab.com/chromium-ppc64le/chromium-ppc64le
Debian friends, the link that TLE posted brings Chromium version 84 for various distributions. Is it possible in your opinion to install it on Debian by downloading it from this link? I tried this with the dpkg command but couldn't, maybe because it has no .Deb extension ... I tried dpkg -i
MauryG5:
Hi guys excuse me, I was trying to upgrade debian buster to bullseye but something went wrong. While he was doing all the upgrades he put himself in stenad by, I was out of the room and I did not notice and now he no longer takes the commands sudo apt-get upgrade or sudo apt-get dist-upgrade and tells me that the dpkg is locked and I need to make some changes. What exactly must he do that I don't understand? Thanks
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version