On 4/11/23 04:56, bad sector wrote:
On 4/11/23 07:47, Jim Jackson wrote:
On 2023-04-11, TJ <TJ@noneofyour.business> wrote:
On 2023-04-10 17:27, Ant wrote:
Hello,
Over Easter 2023 weekend, my friend and I replaced my 14 yrs. old
Debian PC's mobo, CPU, RAM, drives, etc. for better setups like
speeds. However, my May 2022's updated 64-bit Debian v11 (stable --
bullseye) installation has a long start up due to errors on the new
hardwares especially in SSD.
Last night, I Clonezillaed from the very old 320 GB HDD to a new
Samsung 500 GB SSD. I used a bootable gparted
(gparted-live-1.5.0-1-amd64.iso) CDRW to make my old Linux partition
bigger, redid my partitions to remake a new bigger swap partition
and add a NTFS partition for my future 64-bit Windows 7 HPE SP1
restore/install (just concentrating on my old Debian for now).
I managed to make the 1.5 mins. pause go away for
UUID=7f52c5a5-0a8f-478e-bbc6-fb22204a06ed job issue by adding # to
my /etc/fstab's #UUID=7f52c5a5-0a8f-478e-bbc6-fb22204a06ed
none swap sw 0 0 line.
Its comment says "swap was on /dev/sdb5 during installation". That
used to be my old 1 GB swap partition. How do I figure out what UUID
to use to point to the newly made swap partition? Actually, do I
even need it with 16 GB of RAM now? I did on the former PC with 2 GB
of RAM.
http://zimage.com/~ant/temp/DebianSwappedHWs/ shows details like
dmesg log, a photo, systemctl status systemd-modules-load.service, etc. >>>>
How do I fix these issues? I hope I don't have to (clean/re)install!
Thank you for reading and hopefully answering soon. :)
You'll need the bigger swap partition if you ever use hibernate or
suspend/resume.
If I were doing that big of a hardware upgrade, I wouldn't dream of
*not* doing a clean install of the system.
Aaaahhhh... the microsoft mentality wins out even here :-) Just before
Easter I too upgraded my 11 year old hardware. I moved my old
spinning rust to the new hardware, and it just booted.
I did have a little bit more trouble getting the new SSD to boot after
dd'ing across the contents of the old disk - but I never did get my head
around these new fangled uuid's (I had forgot that the dd duplicated the
disk uuid!!!! whoops), and grub2 must one of the most opaque pieces of
software ever! But even that was quicker than a reinstall, and putting
back my custom mail, syslog, nfs etc, etc configs
But of course YMMV.
%$#@*ing-A :-)
Is systemd jockeying to stranglehold the kernel?
Is uuid a microcancer long-knife too?
How about grub2?
Will dd next be crippled too?
just musing about eEe
Golly you old-timers are set your ways. If this was a real
conversation I would say sot in your ways. I have only been using
GNU/Linux for about 15 years. Started with Mandriva 2006. Most of
you guys started years before me but you have not kept up with
the GNU/Linux news.
Now Grub2 is as easy as Grub 0.99 if you bother to search for documentation.
Plenty of good distributions without systemd.
UUID and labeling as well are great tools.
"dd" cannot be crippled but in a good script it writes .iso files to a Flash Drive very well...
What sort of support does your distribution of GNU/Linux have?
My choice has one of the very finest User Forums around with plenty
of testers and coders and the coolest packager I have yet found.
If I cannot find an answer there I figure out what I have to ask and
go to the WWW. DuckDuckGo works very well.
Good luck with all your problems
bliss - on the ever-faithful Dell Latitude E7450, PCLinuxOS 2023
KDE Plasma 5.27.4 Kernel Version: 6.2.10 pclos1 (64-bit)
KDE Frameworks 5.104.0 - Qt Version: 5.15.6
Graphics : X11 - Mesa Intel® HD Graphics 5500
15.5 GiB of RAM C9PU 4 × Intel® Core™ i7-5600U CPU @ 2.60GHz
Actually 2 real cores and 2 virtual cores.
--
bliss dash SF 4 ever at dslextreme dot com
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)