Hello,errors on the new hardwares especially in SSD.
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
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 andadd 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.former PC with 2 GB of RAM.
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
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. :)
Hello,errors on the new hardwares especially in SSD.
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
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 andadd 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.former PC with 2 GB of RAM.
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
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. :)
On 4/10/23 17:27, Ant wrote:errors on the new hardwares especially in SSD.
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
add a NTFS partition for my future 64-bit Windows 7 HPE SP1 restore/install (just concentrating on my old Debian for now).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
former PC with 2 GB of RAM.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
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. :)
Not sure if I understand but...
# blkid
this will list the uuids accessible at the time, including your swap
identify the swap partition you magde then use THAT uuid in your fstab
UUID=(new uuid here) none swap sw 0 0
some people also add nofail to the swap entry, I can't comment on that
Hello,errors on the new hardwares especially in SSD.
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
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 andadd 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.former PC with 2 GB of RAM.
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
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. :)
In comp.os.linux.hardware bad sector <forgetski@invalid.net> wrote:errors on the new hardwares especially in SSD.
On 4/10/23 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
and add a NTFS partition for my future 64-bit Windows 7 HPE SP1 restore/install (just concentrating on my old Debian for now).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
the former PC with 2 GB of RAM.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
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. :)
Not sure if I understand but...
# blkid
this will list the uuids accessible at the time, including your swap identify the swap partition you magde then use THAT uuid in your fstab
UUID=(new uuid here) none swap sw 0 0
some people also add nofail to the swap entry, I can't comment on that
Thanks. It worked. I didn't use nofail since my /etc/fstab didn't show it.
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.former PC with 2 GB of RAM.
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
If I were doing that big of a hardware upgrade, I wouldn't dream of
*not* doing a clean install of the system.
But then, I don't use Debian, I use Mageia. And being a member of the
Mageia team that tests install isos before their release to the
public, I've done hundreds of new installs in my time. What's one more
to me?
In comp.os.linux.hardware Ant <ant@zimage.comant> wrote:errors on the new hardwares especially in SSD.
In comp.os.linux.hardware bad sector <forgetski@invalid.net> wrote:
On 4/10/23 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
add a NTFS partition for my future 64-bit Windows 7 HPE SP1 restore/install (just concentrating on my old Debian for now).
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
former PC with 2 GB of RAM.
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
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. :)
Not sure if I understand but...
# blkid
this will list the uuids accessible at the time, including your swap
identify the swap partition you magde then use THAT uuid in your fstab
UUID=(new uuid here) none swap sw 0 0
some people also add nofail to the swap entry, I can't comment on that
Thanks. It worked. I didn't use nofail since my /etc/fstab didn't show it.
https://www.reddit.com/r/debian/comments/12hwrfo/swapped_my_hardwares_motherboard_cpu_ram_drives/jfsoqmd/
fixed my other startup issues too. Wow, my old Debian now boots up and
shut down so fast! I had to do it a few times to be sure I wasn't
dreaming since I was tired. :D
On 2023-04-10 17:27, Ant wrote:errors on the new hardwares especially in SSD.
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
add a NTFS partition for my future 64-bit Windows 7 HPE SP1 restore/install (just concentrating on my old Debian for now).
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
former PC with 2 GB of RAM.
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
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.
On 2023-04-11, TJ <TJ@noneofyour.business> wrote:errors on the new hardwares especially in SSD.
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
add a NTFS partition for my future 64-bit Windows 7 HPE SP1 restore/install (just concentrating on my old Debian for now).
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
former PC with 2 GB of RAM.
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
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.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 307 |
Nodes: | 16 (2 / 14) |
Uptime: | 64:05:26 |
Calls: | 6,915 |
Files: | 12,379 |
Messages: | 5,431,553 |