Good day. I acquired a new SSD (220) and decided to put Linux Mint on it. Disconnected all the disks, connected the new one, installed it, but bios does not see at all that there is a system on this disk. On the old SDD (110) disk, on which the Windows used to stand, the system gets up normally and is displayed in the BIOS loader.

I connected both disks, started the system from the old disk, made sudo fdisk -l to check if the markup was suddenly different, it turned out that the markup is the same. What to do to see the bios system from the second disk?

PS Mint reinstalled a bunch of times, and through UEFI, and without it, without result. Bios vseravno it does not see

The output of sudo fdisk -l :

 Диск /dev/sda: 111,8 GiB, 120034123776 Π±Π°ΠΉΡ‚ΠΎΠ², 234441648 сСкторов Π•Π΄ΠΈΠ½ΠΈΡ†Ρ‹ измСрСния: сСкторов ΠΈΠ· 1 * 512 = 512 Π±Π°ΠΉΡ‚ΠΎΠ² Π Π°Π·ΠΌΠ΅Ρ€ сСктора (логичСский/физичСский): 512 Π±Π°ΠΉΡ‚ / 512 Π±Π°ΠΉΡ‚ I/O size (minimum/optimal): 512 bytes / 512 bytes Π’ΠΈΠΏ ΠΌΠ΅Ρ‚ΠΊΠΈ диска: dos Π˜Π΄Π΅Π½Ρ‚ΠΈΡ„ΠΈΠΊΠ°Ρ‚ΠΎΡ€ диска: 0x3d4bc537 Устр-Π²ΠΎ Π—Π°Π³Ρ€ΡƒΠ·ΠΎΡ‡Π½Ρ‹ΠΉ Start ΠšΠΎΠ½Π΅Ρ† Π‘Π΅ΠΊΡ‚ΠΎΡ€Ρ‹ Size Id Π’ΠΈΠΏ /dev/sda1 * 2048 205158399 205156352 97,8G 83 Linux /dev/sda2 205160446 234440703 29280258 14G 5 Π Π°ΡΡˆΠΈΡ€Π΅Π½Π½Ρ‹ΠΉ /dev/sda5 205160448 234440703 29280256 14G 82 Linux своп / Solaris Диск /dev/sdb: 223,6 GiB, 240065183744 Π±Π°ΠΉΡ‚ΠΎΠ², 468877312 сСкторов Π•Π΄ΠΈΠ½ΠΈΡ†Ρ‹ измСрСния: сСкторов ΠΈΠ· 1 * 512 = 512 Π±Π°ΠΉΡ‚ΠΎΠ² Π Π°Π·ΠΌΠ΅Ρ€ сСктора (логичСский/физичСский): 512 Π±Π°ΠΉΡ‚ / 512 Π±Π°ΠΉΡ‚ I/O size (minimum/optimal): 512 bytes / 512 bytes Π’ΠΈΠΏ ΠΌΠ΅Ρ‚ΠΊΠΈ диска: dos Π˜Π΄Π΅Π½Ρ‚ΠΈΡ„ΠΈΠΊΠ°Ρ‚ΠΎΡ€ диска: 0x396a5733 Устр-Π²ΠΎ Π—Π°Π³Ρ€ΡƒΠ·ΠΎΡ‡Π½Ρ‹ΠΉ Start ΠšΠΎΠ½Π΅Ρ† Π‘Π΅ΠΊΡ‚ΠΎΡ€Ρ‹ Size Id Π’ΠΈΠΏ /dev/sdb1 * 2048 439592959 439590912 209,6G 83 Linux /dev/sdb2 439595006 468875263 29280258 14G 5 Π Π°ΡΡˆΠΈΡ€Π΅Π½Π½Ρ‹ΠΉ /dev/sdb5 439595008 468875263 29280256 14G 82 Linux своп / Solaris

I also noticed that the system running from the old SSD (110) displays 3 disks, one on which is the current system, the other on which is the system that does not start, and the third one that does not open, called "KINGSTON ..." (SSD name ( 110)) as in the boot menu.

Resetting CMOS through the button on the motherboard did not help either.

  • The last remark is very interesting. As if the new ssd can be seen as 2 devices and the BIOS does not see that. At least this "third disc" makes you wonder. It is interesting that in / proc / partitions and that in the kernel boot logs, what it saw there ... - Mike
  • Well, the third disk is the name of the one on which the "starting system". Those. On a running system, two disks, one of which does not open, and a third with another system that does not start - Denis
  • in / proc / partitions all the same disks as in fdisk - Denis
  • You do not look fdisk , but gdisk or whatever it is called for GPT. - 0andriy
  • Please attach the output of $ tail /sys/block/*/removable with both block devices attached. - aleksandr barakin

1 answer 1

Problem solved!

The jamb was that my main Asrock p67 extreme4 has 4 SATA3 ports, two of which are without AHCI support. Just in one of these ports a new SSD was connected, so the BIOS bootloader did not see it, and it was possible to write and read from it.