2 TB M.2 Sata SSD not recognized by lsblk but by dmesg in multiple distros
by M0M0 from LinuxQuestions.org on (#5AVXH)
Hello,
I bought a brand new 2 TB M.2 Sata SSD and an M.2. Sata to USB 3 adapter. To check that everything was working I plugged in the SSD via USB and ran lsblk while my "normal" Slackware operating system was running. Nothing found so I run dmesg and the results were:
[5.987776] sd 2: 0: 0: 0: [sdb] 0 logical 512-byte blocks: (0 B / 0 B)
[5.987778] SD 2: 0: 0: 0: [SDB] physical 0-byte blocks
[5.988138] sd 2: 0: 0: 0: [sdb] Test WP failed, assuming Write Enabled
[5.988252] sd 2: 0: 0: 0: [sdb] Querying cache data failed
[5.988253] sd 2: 0: 0: 0: [sdb] Assuming drive cache: write through
[5.988456] sd 2: 0: 0: 0: [sdb] Optimal transfer size 33553920 bytes, not a multiple of the physical block size (0 bytes)
So I thought it could be a problem with Slackware and booted into Clonezilla - same result. Then I tried gparted and it didn't recognize the drive either.
The next step was not to use the m.2 to USB converter at all and plug the drive directly into my m.2 Sata port and then boot into multiple live distros and again none of them could recognize the drive.
So I think there are two possibilities:
1. The Linux kernel does not support the drive
2. The drive is dead
Can someone who can understand the dmesg messages check this?
Name of the SSD is:
Samsung V-NAND SSD 860 EVO SATA M.2
I bought a brand new 2 TB M.2 Sata SSD and an M.2. Sata to USB 3 adapter. To check that everything was working I plugged in the SSD via USB and ran lsblk while my "normal" Slackware operating system was running. Nothing found so I run dmesg and the results were:
[5.987776] sd 2: 0: 0: 0: [sdb] 0 logical 512-byte blocks: (0 B / 0 B)
[5.987778] SD 2: 0: 0: 0: [SDB] physical 0-byte blocks
[5.988138] sd 2: 0: 0: 0: [sdb] Test WP failed, assuming Write Enabled
[5.988252] sd 2: 0: 0: 0: [sdb] Querying cache data failed
[5.988253] sd 2: 0: 0: 0: [sdb] Assuming drive cache: write through
[5.988456] sd 2: 0: 0: 0: [sdb] Optimal transfer size 33553920 bytes, not a multiple of the physical block size (0 bytes)
So I thought it could be a problem with Slackware and booted into Clonezilla - same result. Then I tried gparted and it didn't recognize the drive either.
The next step was not to use the m.2 to USB converter at all and plug the drive directly into my m.2 Sata port and then boot into multiple live distros and again none of them could recognize the drive.
So I think there are two possibilities:
1. The Linux kernel does not support the drive
2. The drive is dead
Can someone who can understand the dmesg messages check this?
Name of the SSD is:
Samsung V-NAND SSD 860 EVO SATA M.2