Problem after SSD upgrade

Just to be clear.

You've cloned your old drive to a new ssd
It was booting past grub fine, but then locking up on log in
You've formatted the drive, created a new partition table, and made a fresh install of manjaro with the same result

Is that the chain of events so far?

what was the other distro you installed that booted successfully?

Can you post

inxi -Fxxxza --no-host

So we know more about your drive, and hardware in general.

You should check that the UUID's specified in /etc/fstab match your drives current UUID correctly.

Please post:

cat /etc/fstab
sudo blkid -o list

If the UUID listed in the blkid output is different from those in etc fstab you will need to edit the UUID(s) to the correct alphanumeric string.

You will need to do this by booting to a grub prompt to run the commands properly. See here:

It blocked after about fifteen seconds no matter what I was doing. The rest is as you have described it.The other distro I had on live USB was MX Linux.It booted just fine and worked flawlessly.

ystem:
Kernel: 5.4.13-3-MANJARO x86_64 bits: 64 compiler: gcc v: 9.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.4-x86_64
root=UUID=a837f63f-4323-42c7-b066-4a830a43a8e0 rw quiet apparmor=1
security=apparmor udev.log_priority=3
Desktop: Xfce 4.14.2 tk: Gtk 3.24.13 info: xfce4-panel wm: xfwm4
dm: LightDM 1.30.0 Distro: Manjaro Linux
Machine:
Type: Laptop System: LENOVO product: 20091 v: Lenovo IdeaPad Y570
serial:
Mobo: LENOVO model: N/A serial: BIOS: LENOVO v: 47CN31WW(V2.09)
date: 10/28/2011
Battery:
ID-1: BAT1 charge: 3.8 Wh condition: 3.8/5.8 Wh (66%) volts: 12.4/11.1
model: SANYO PABAS024 type: Li-ion serial: status: Unknown
CPU:
Topology: Quad Core model: Intel Core i7-2670QM bits: 64 type: MT MCP
arch: Sandy Bridge family: 6 model-id: 2A (42) stepping: 7 microcode: 2F
L2 cache: 6144 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 35128
Speed: 798 MHz min/max: 800/3100 MHz Core speeds (MHz): 1: 798 2: 798
3: 798 4: 799 5: 798 6: 799 7: 798 8: 799
Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable
Type: l1tf mitigation: PTE Inversion
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: conditional, RSB filling
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0116
Device-2: NVIDIA GF108M [GeForce GT 555M] vendor: Lenovo driver: nouveau
v: kernel bus ID: 01:00.0 chip ID: 10de:0deb
Display: x11 server: X.Org 1.20.7 driver: intel,modesetting
alternate: fbdev,vesa resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 19.3.2
compat-v: 3.0 direct render: Yes
Audio:
Device-1: Intel 6 Series/C200 Series Family High Definition Audio
vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1b.0
chip ID: 8086:1c20
Device-2: NVIDIA GF108 High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0bea
Sound Server: ALSA v: k5.4.13-3-MANJARO
Network:
Device-1: Intel Centrino Wireless-N 1000 [Condor Peak] driver: iwlwifi
v: kernel port: 2000 bus ID: 08:00.0 chip ID: 8086:0084
IF: wlp8s0 state: up mac:
Drives:
Local Storage: total: 465.76 GiB used: 28.00 GiB (6.0%)
ID-1: /dev/sda vendor: Seagate model: ST9500325AS size: 465.76 GiB
block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
rotation: 5400 rpm serial: rev: LVM1 scheme: MBR
Partition:
ID-1: / raw size: 465.76 GiB size: 457.45 GiB (98.22%)
used: 28.00 GiB (6.1%) fs: ext4 dev: /dev/sda1
Sensors:
System Temperatures: cpu: 61.0 C mobo: N/A gpu: nouveau temp: 65 C
Fan Speeds (RPM): N/A
Info:
Processes: 227 Uptime: 4h 26m Memory: 15.58 GiB used: 2.58 GiB (16.6%)
Init: systemd v: 242 Compilers: gcc: 9.2.0 Shell: bash v: 5.0.11
running in: xfce4-terminal inxi: 3.0.37
Knowing that this is my old hard drive on the computer.

Thank you

1 Like

You're welcome.

Did you figure out how to fix your issue by editing the UUID in /etc/fstab.

Not yet because i am at work ,but tomorrow will tackle it. I am sure to have many more questions , so I will try not to be nasty and only bother you if I can't do on my own.
Offtopic I am pleased to find out some guys like you who re so responsive and not like ''you are soo stupid ..and so on " ...Really grateful!

3 Likes

I'm still not sure, so you installed MX rather than running a live session?

Can't you get an inxi using the problem hard drive? Even from a live environment it would tell us the full model name and partition table. We aren't trying to troubleshoot your old drive.

Did you check this? it's the most likely culprit. You could also try reinstalling grub and replacing the old boot entry

If you did and you're answering in the affirmative to all of the above you could try one of the 19.0 preview builds and see if you have anymore luck getting that to install on your new drive.

1 Like

Will try it ,and -yes I'm sure to have successfully installed the MX on the same ssd>

You also have a 2011 BIOS. Any updates for that?

1 Like

System:
Kernel: 5.4.6-2-MANJARO x86_64 bits: 64 compiler: gcc v: 9.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
driver=free nouveau.modeset=1 i915.modeset=1 radeon.modeset=1
misobasedir=manjaro misolabel=MJRO1815 quiet systemd.show_status=1
Desktop: Xfce 4.14.1 tk: Gtk 3.24.12 info: xfce4-panel wm: xfwm4
dm: LightDM 1.30.0 Distro: Manjaro Linux
Machine:
Type: Laptop System: LENOVO product: 20091 v: Lenovo IdeaPad Y570
serial:
Mobo: LENOVO model: N/A serial: BIOS: LENOVO v: 47CN31WW(V2.09)
date: 10/28/2011
Battery:
ID-1: BAT1 charge: 3.8 Wh condition: 3.8/5.8 Wh (66%) volts: 12.4/11.1
model: SANYO PABAS024 type: Li-ion serial: status: Unknown
CPU:
Topology: Quad Core model: Intel Core i7-2670QM bits: 64 type: MT MCP
arch: Sandy Bridge family: 6 model-id: 2A (42) stepping: 7 microcode: 2F
L2 cache: 6144 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 35135
Speed: 950 MHz min/max: 800/3100 MHz Core speeds (MHz): 1: 880 2: 1037
3: 1215 4: 1083 5: 1027 6: 918 7: 1060 8: 931
Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable
Type: l1tf mitigation: PTE Inversion
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: conditional, RSB filling
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0116
Device-2: NVIDIA GF108M [GeForce GT 555M] vendor: Lenovo driver: nouveau
v: kernel bus ID: 01:00.0 chip ID: 10de:0deb
Display: x11 server: X.Org 1.20.6 driver: intel,nouveau
unloaded: modesetting alternate: fbdev,nv,vesa resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 19.3.1
compat-v: 3.0 direct render: Yes
Audio:
Device-1: Intel 6 Series/C200 Series Family High Definition Audio
vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1b.0
chip ID: 8086:1c20
Device-2: NVIDIA GF108 High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0bea
Sound Server: ALSA v: k5.4.6-2-MANJARO
Network:
Device-1: Broadcom and subsidiaries NetLink BCM57781 Gigabit Ethernet PCIe
vendor: Lenovo driver: N/A port: 2000 bus ID: 07:00.0 chip ID: 14e4:16b1
Device-2: Intel Centrino Wireless-N 1000 [Condor Peak] driver: iwlwifi
v: kernel port: 2000 bus ID: 08:00.0 chip ID: 8086:0084
IF: wlp8s0 state: up mac:
Drives:
Local Storage: total: 935.24 GiB used: 107.9 MiB (0.0%)
ID-1: /dev/sda vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB
block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
serial: rev: 023 scheme: MBR
ID-2: /dev/sdb type: USB vendor: Toshiba model: TransMemory size: 3.73 GiB
block size: physical: 512 B logical: 512 B serial: rev: PMAP
scheme: MBR
Partition:
ID-1: / raw size: N/A size: 11.69 GiB used: 107.9 MiB (0.9%) fs: overlay
source: ERR-102
Sensors:
System Temperatures: cpu: 62.0 C mobo: N/A gpu: nouveau temp: 65 C
Fan Speeds (RPM): N/A
Info:
Processes: 248 Uptime: 4m Memory: 15.58 GiB used: 1.44 GiB (9.3%)
Init: systemd v: 242 Compilers: gcc: 9.2.0 Shell: bash v: 5.0.11
running in: xfce4-terminal inxi: 3.0.37
With the SSD

Also a very good call

Same partition table, goodo.

Try restoring clonezilla image again and then check the UUIDs of the partitions on the ssd and compare them to the UUIDs in your fstab to see if they match, amend accordingly, you can do this by mounting the partition in a live session. If that doesn't work you can restore grub using the guide I linked earlier, this can also be done from a live session using manjaro chroot.

Before that it may be worth seeing if you can log in using a console session, at the login screen press CTRL+ALT+F2 and log in with your username and password. If that works we'll know that the drive is mounting correctly, if it freezes again then following the steps I just outlined should fix it up.

And update your bios :slight_smile:

It's current.

Current might not be quite the right term, but yes it does seem like its the most recent, some stellar long term support from Lenovo right there :sweat_smile:

1 Like

They only really bother with ThinkPad T series

Almost forgot, this explains how to reinstall your bootloader using manjaro chroot from a live session, for if you're unable to get in to your current installation with a text session or otherwise.
https://wiki.manjaro.org/index.php?title=GRUB/Restore_the_GRUB_Bootloader#Use_manjaro-chroot

If that doesn't work try the more up to date iso I linked earlier, and if that doesn't work I'm out of ideas!

1 Like

So sudo] password for boyan:
/dev/sda1: UUID="a837f63f-4323-42c7-b066-4a830a43a8e0" TYPE="ext4" PARTUUID="1c903654-01"
on my HD andIMG_20200125_192624
So on the photo I see the same UUID twice.The photo was taken while booting the SSD as a live disk.The two partitions are the HD and the SSD if I am getting it right>Unfortunately the SSD didn't work as a primary boot source although I have a perfect match ...

You leaving the backup drive plugged in after restoring? Cos that's how you make a kernel freakout, it reads duplicated UUIDs and doesn't know what to do because they're supposed to be unique. After restoring the image shut down the computer, remove the backup drive (or original drive rather), and then try to boot.

You want to be comparing the UUID of the restored partitions to those in /etc/fstab, if they match you're good if they don't you need to amend the fstab.

1 Like

You can also change UUID's on a preexisting partition without a data destructive format.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by