NVME disk problem linux version question.

It's not even partition magic , it's just that partition magic boot disk.
After booting to that, I can use fdisk. that's not a partition magic program, right?!
I've never used Partition Magic. I'm a gparted guy.
If you can't change or resize a partition in Partition Magic than no.

The command fdisk -l has to be ran with root privileges.
sudo fidisk -l
 


Have you tried going into the BIOS and disable "Sata Operation"?
Reboot and than try to install Linux Mint.

If that doesn't work I'm not sure what will.
I have.
On that thread, only one person says disable SATA the other two say switch to ACHI.
 
I have.
On that thread, only one person says disable SATA the other two say switch to ACHI.
IF that doesn't help you to be able to start the install of Linux Mint I don't know what will.

I'm very surprised that gparted doesn't see the nvme.
That's unusual.
 
I downloaded a a Seagate tool .bin file and tried to install it.
Since it was just spinning circle for a few minutes I decided to shut it down.
Now it's doing this for the last 5 min.
At some point I will cut power to it.
20210331_182028.jpg
 
I've never used Partition Magic. I'm a gparted guy.
If you can't change or resize a partition in Partition Magic than no.

The command fdisk -l has to be ran with root privileges.
sudo fidisk -l
Actually Partition Magic is in windows I think, I am just mixing the names of things. Just like I Gnome, gparted, parted magic, parted, fdisk. too many, too many versions. command line, old text based, new GUI.
 
Actually Partition Magic is in windows I think, I am just mixing the names of things. Just like I Gnome, gparted, parted magic, parted, fdisk. too many, too many versions. command line, old text based, new GUI.
Ok got it.

Can you boot into Windows?
 
Is gparted GUI is the same as what I start as "parted" in command line ?
 
IF that doesn't help you to be able to start the install of Linux Mint I don't know what will.

I'm very surprised that gparted doesn't see the nvme.
That's unusual.

Because you are still not registering that stuff that happens during boot, is different for the 2016 and current (like the Mint or others)
There was a log in Mint I was looking at. It clearly full of errors. The last thing I want to do is to understand all this, but by the time it's in Mint, it's too late.
 

Attachments

  • 20210331_181410.jpg
    20210331_181410.jpg
    3 MB · Views: 215
Can you help me to clean, clear the drive with what does work in the 2016 version, fdisk and parted ?
Parted Magic was also working at some point.
 
Because you are still not registering that stuff that happens during boot, is different for the 2016 and current (like the Mint or others)
There was a log in Mint I was looking at. It clearly full of errors. The last thing I want to do is to understand all this, but by the time it's in Mint, it's too late.
I'll look up those errors and see if I can make any sense of it.
 
Can you help me to clean, clear the drive with what does work in the 2016 version, fdisk and parted ?
Parted Magic was also working at some point.
I don't have any experience with Parted Magic.

IF parted Magic is a partition manager than you would use it to delete, resize or otherwise manipulate partitions.
 
On the 2016 menu there are other thing, to load stuff, any help there?
View attachment 8937
-Super Grub2 Disk is for fixing/installing Grub which is a bootloader.
-Clonezilla is for cloning a drive and everything on it if you want to use it.
-Load iSCSI kernel modules 64 is for a 64 bit machine and iSCSI kernel moules 32 is for a 32 bit machine.
I'm not sure if that would load a kernel for you or not. I've never used it.
 
Are you sure there is no gparted on this?
It looks like it started to do something instead of the "command doesn't exist" et.
Also any of these returns mean anything?
20210331_185947.jpg20210331_190243.jpg20210331_190400.jpg
 
squashfs error: unable to read page could mean that you have bad memory modules.
Are you sure there is no gparted on this?
It looks like it started to do something instead of the "command doesn't exist" et.
Also any of these returns mean anything?
View attachment 8938View attachment 8939View attachment 8940
Both drives are showing in the output of lsblk. That's a good sign.
However; I don't get why Mint or any other Linux distro doesn't see your nvme.:(

I did a quick search and one of the errors that you are getting (squashfs error: unable to read page) could mean that the memory modules are bad.

The only way to find out if the RAM is bad is to run Memtest.
 
Reading this, I'm starting to think there's a legit hardware (hard drive/SSD) issue going on.

The only problem with that theory is that they'd still be able to boot to a live USB instance.
 
Reading this, I'm starting to think there's a legit hardware (hard drive/SSD) issue going on.

The only problem with that theory is that they'd still be able to boot to a live USB instance.

I can creat and format and changed to GPT and wiped with Nwipe , so the drive has be ok, I would waste this time if I think it is a hardware problem.
 
Reading this, I'm starting to think there's a legit hardware (hard drive/SSD) issue going on.

The only problem with that theory is that they'd still be able to boot to a live USB instance.
At this point I'm not sure if the RAM is bad or there is something wrong with the HDD.

Maybe S.M.A.R.T. is the best tool to check the health of the drive now.
 
squashfs error: unable to read page could mean that you have bad memory modules.

Both drives are showing in the output of lsblk. That's a good sign.
However; I don't get why Mint or any other Linux distro doesn't see your nvme.:(

I did a quick search and one of the errors that you are getting (squashfs error: unable to read page) could mean that the memory modules are bad.

The only way to find out if the RAM is bad is to run Memtest.
I had to hard shut that down, it was just trying to clear itself or something.
The errors in the log should be more telling.

I downloaded an old gparted (gnome live cd ) .iso and it didn't even boot. Maybe it is not UEFI.
 

Staff online

Members online


Top