Swap partition causes blocked BIOS menu (black screen) [SOLVED]

adrian123 · 2020-06-25 23:22:25

So, I have installed ubuntu over a year ago (newbie to the linux community), and the swap partition (a small one, 512MB) did not do anything wrong. Last week I bought an nvme and installed it on the laptop, also I installed arch linux (that's why I'm here). Basically, I noticed the day after the installation that I couldn't go to the BIOS settings (the screen turned to black after the BIOS asked for password, no BIOS menu after 10 min). I cleared the CMOS but it didn't help. I tried checking the HDMI port with a monitor, same black screen. I tried going to the BIOS without the nvme or the hard disk, that is when it started working again. I erased everything on the drives and I started checking after every installation. When I installed arch and created a swap partition (mkswap, swapon and modified fstab with the correct UUID), the problem came up again. When I turned off the swap partition and deleted the partition, the BIOS menu was accessible again.

I checked if I had created a swap partition wrong by creating the swap partition with the ubuntu installer. It happened again.

Also, the laptop BIOS was updated over a year ago, there haven't been new versions since.

Any suggestion is appreciated

Last edited by adrian123 (2020-07-15 16:33:42)

loqs · 2020-06-25 23:42:57

What is the output of

# blkid
#parted -l

Last edited by loqs (2020-06-26 00:17:50)

adrian123 · 2020-06-26 01:17:40

blkid

/dev/nvme0n1p1: UUID="3C21-AC56" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="5a22423c-f6ca-4533-adec-afe0e76d16cb"
/dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="e7352889-9261-4f71-bdd6-dd325893d08d"
/dev/nvme0n1p3: BLOCK_SIZE="512" UUID="A6BE268BBE2653D9" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="b38e237c-8c5c-40c5-ac10-457c2684db09"
/dev/nvme0n1p4: BLOCK_SIZE="512" UUID="529C86119C85F031" TYPE="ntfs" PARTUUID="7883ebd8-31a4-487c-9718-cac8d931b1f9"
/dev/nvme0n1p5: UUID="9dc9de71-1f95-462c-b7ef-269eb7b712a1" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="39020cb0-e35a-4f67-83a8-c0e26f7ea105"
/dev/nvme0n1p6: UUID="F135-47AE" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="2e9b5cac-0857-4f08-b618-e30b4af048d5"
/dev/nvme0n1p7: UUID="6a26c3ac-b0df-4724-bd3f-54fe9530c579" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="37af1042-0d73-b340-80a8-18586e09fdaa"
/dev/sda1: UUID="16951fa1-ebe2-496c-8f52-1388b291ea22" TYPE="swap" PARTLABEL="Basic data partition" PARTUUID="334ddfa3-b3c4-4924-b916-fc1232754aee"

Explanation/Simplification:
/dev/nvme0n1p1 is the windows bootloader
/dev/nvme0n1p2 is a windows reserved partition (I can look what is its purpose later)
/dev/nvme0n1p3 is the windows system partition
/dev/nvme0n1p4 is the windows recovery partition
/dev/nvme0n1p5 is the ubuntu partition
/dev/nvme0n1p6 is the grub partition (boot #1 option)
/dev/nvme0n1p7 is the arch linux partition
/dev/sda1 is the swap partition

Not important info: The swap partition is on another device because I think it's better not to use the nvme (I have read that the ssd have limited writes, and as such should not be used for swap partitions). The sda device does not have more partitions because I have erased them.

parted -l

(some words translated)

Model: ATA HGST HTS721010A9 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start  End       Size           File System           Name                          Flags
 1      1049kB  4057MB  4056MB  linux-swap(v1)       Basic data partition  swap


Model: WDS500G3X0C-00SJG0 (nvme)
Disk /dev/nvme0n1: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start  End       Size           File System           Name                          Flags
 1      1049kB  106MB  105MB   fat32                EFI system partition          startup, esp
 2      106MB   123MB  16,8MB                       Microsoft reserved partition  msftres
 3      123MB   290GB  290GB   ntfs                 Basic data partition          msftdata
 4      290GB   290GB  543MB   ntfs                                               hidden diag
 5      290GB   381GB  90,7GB  ext4
 6      381GB   382GB  900MB   fat32                                              startup, esp
 7      382GB   500GB  118GB   ext4

Last edited by adrian123 (2020-06-26 14:27:10)

seth · 2020-06-26 05:28:10

Please use "code" tags, https://bbs.archlinux.org/help.php#bbcode and "LC_ALL=C parted -l" (and similar)

Try to create two partitions on that drive, make the first one vfat - the BIOS probably tries to access the partition but cannot deal w/ the swap type.

nl6720 · 2020-06-26 05:33:01

What is the swap partition's partition type?

$ lsblk -o +PARTTYPE /dev/sda1

adrian123 · 2020-06-26 14:28:37

lsblk -o +PARTTYPE /dev/sda1

NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT PARTTYPE
sda1   8:1    0  3,8G  0 part [SWAP]     0657fd6d-a4ab-43c4-84e5-0933c84b4f4f

seth · 2020-06-26 14:35:20

That's a UUID, the partition type should™ be 0x82 - what do you use to create those partitions?

loqs · 2020-06-26 14:38:07

seth 0657fd6d-a4ab-43c4-84e5-0933c84b4f4f is correct see man 8 systemd-gpt-auto-generator or https://en.wikipedia.org/wiki/GUID_Part … type_GUIDs

adrian123 · 2020-06-26 14:41:54

I first used cfdisk, mkswap and swapon, later I tried with the ubuntu install, the last try was with gparted. Maybe this last swap partition was not correctly created, but I don't think creating a new one correctly will fix it. I'm right now making what you said, seth, I think it could work (5 min, I need to know if vfat is the same as fat32 or if I have to use mkfs.vfat).

Btw, thanks for the markdown link, seth

seth · 2020-06-26 14:48:56

Ah, I missed that this was a BIOS/GPT config (probably because of the bad markup ;-) - sorry.

mkfs.vat is the correct one for all the various FAT partition types (except exfat)

adrian123 · 2020-06-26 14:57:52

Well, right now it is still not working. To create the swap partition and the fat partition I used gparted, but later I used mkfs.vfat /dev/sda1 just to be sure.

lsblk -f

NAME        FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda
├─sda1      vfat   FAT32       A2F3-9449
└─sda2      swap   1           f27f5a90-6472-419c-acf6-0a19319e92f4                [SWAP]
sr0
nvme0n1
├─nvme0n1p1 vfat   FAT32       3C21-AC56
├─nvme0n1p2
├─nvme0n1p3 ntfs               A6BE268BBE2653D9
├─nvme0n1p4 ntfs               529C86119C85F031
├─nvme0n1p5 ext4   1.0         9dc9de71-1f95-462c-b7ef-269eb7b712a1
├─nvme0n1p6 vfat   FAT32       F135-47AE
└─nvme0n1p7 ext4   1.0         6a26c3ac-b0df-4724-bd3f-54fe9530c579     97G     5% /

The swap PARTTYPE is still 0657, so I guess that is how gparted makes swap partitions.

lsblk -o +PARTTYPE /dev/sda1

NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT PARTTYPE
sda1   8:1    0  869M  0 part            ebd0a0a2-b9e5-4433-87c0-68b6b72699c7

lsblk -o +PARTTYPE /dev/sda2

NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT PARTTYPE
sda2   8:2    0  9,3G  0 part [SWAP]     0657fd6d-a4ab-43c4-84e5-0933c84b4f4f

I think i'll try

mkswap /dev/sda2

just to be sure

seth · 2020-06-26 15:04:40

You could also try to compeltely remove the swap partition and keep the fat one.

loqs · 2020-06-26 15:15:48

Or try changing the GUID to a different one such as Linux filesystem data 0fc63daf-8483-4772-8e79-3d69d8477de4 or Windows Basic data partition ebd0a0a2-b9e5-4433-87c0-68b6b72699c7

adrian123 · 2020-06-26 15:25:14

So, I have tried with keeping only the FAT32 partition and it still didn't work, so I was wrong when I thought this was only due to the swap partition.

Maybe I need something for a BIOS boot instead of a gpt partition. Also, I don't recall any "enable UEFI/legacy" setting on the BIOS (ironically even if it did exist right now I could not change it )

As I said on the post, I had in that disk a swap partition before and it didn't give problems, I also had a windows boot loader as the first partition (I erased it because I put it on the nvme), not as of right now (it could be related)

Last edited by adrian123 (2020-06-26 15:25:51)

seth · 2020-06-26 15:55:38

Is the disk in the list of boot devices? Can you remove it from there?

adrian123 · 2020-06-26 16:10:28

The disk is detected by all the OS. Right now it doesn't appear in the boot settings because I deleted every partition.

Also, in the BIOS there is not enable UEFI or anything similar. Useless BIOS settings list (just the interesting ones, I wont put wake on lid open, for example) and the current state:

Intel Virtualization Technology -> on
Intel AES-NI -> on
VT-d -> on
Smart Self test -> off
Network stack -> off
Legacy USB support -> on
USB Mass Storage Driver Support -> on
Sata Configuration -> one and only option = AHCI
Fast Boot -> off
CSM support -> off
All the interfaces on the security I/O -> unlocked (included SATA ODD interface)

I will try installing a linux distro on the first partition of the hdd and after that partition I will create the swap partition

adrian123 · 2020-06-26 17:09:53

Well, I have tried to install a linux system on the first partition of the HDD. Here is what happened:

Installed elementary OS (and associated a new grub with the MBR of the hdd) and created during the installation a swap partition
Tried to go to the BIOS menu, it was not possible so I went to arch and removed the swap partition
Tried to go to the BIOS menu. This time I decided to wait while doing other things. 30-40 min later I forced the shutdown. There is no way the BIOS settings needs 30 min lo load. Fortunately, from grub I could go to arch, and from there I could delete the elementary OS partition (ext4)
And after that, obviously the BIOS menu revealed itself in the next try

So I know it is related to the partitions in the hdd (even though when I'm in any OS the disk works just fine) but now I'm without any ideas. Also, I won't install windows on the disk because I don't think it will help me finding the solution and if it does block the BIOS menu I would need remove it (I don't know how to remove windows inside it, and I would not have access to the boot menu to select arch or a live os) to be able to use other OS.

Fortunately, there is a plan B (without knowing the cause of this problem and just avoding it) and that is creating a swap file in every linux partition.

Edit: Also, loqs thanks for your suggestion. I have tried it and in both cases the BIOS menu was blocked

Last edited by adrian123 (2020-06-26 17:13:01)

seth · 2020-06-26 21:23:20

Grasping some straws:
What if you "dd if=/dev/zero of=/dev/sda count=1k" nuke the header of the disk before partitioning it?
Did you try to create an MBR/DOS partition table instead of GPT?

adrian123 · 2020-06-27 01:42:17

I tried nuking the header (couldn't resist the temptation). Also I tried the DOS partition, using cfdisk on the device after nuking the header it asked me a type (I only tried with gpt and MBR because the 2 other options had names I've never heard). Unfortunately, It didn't work.

But, I this problem is not about the type of partition. I'll explain:
To me it was very rare that previously it never had a problem and it now does. So I erased the hdd and uninstalled the nvme. I installed ubuntu on a partition on the hdd, as well as a swap partition. After the installation I tried and I could go to the BIOS settings. I installed again the nvme and the problem appeared again.

I went to ASUS webpage to check the laptops manual (gl753vd). The ssd installation section does not mention any problem having a ssd and a hdd at the same time (also, the ssd and the hdd are using different interfaces, nvme and sata, respectively)

(Right now it still not solved, and both the hdd and the nvme are with the label gpt, so the problem is not there)

This is more confusing the deeper it goes. If you don't have more ideas, don't worry. I'm still grateful for the help and the suggestions. Thank you guys

Last edited by adrian123 (2020-06-27 01:43:58)

mxfm · 2020-06-27 04:18:29

adrian123 wrote:

Intel Virtualization Technology -> on
Intel AES-NI -> on
VT-d -> on
Smart Self test -> off
Network stack -> off
Legacy USB support -> on
USB Mass Storage Driver Support -> on
Sata Configuration -> one and only option = AHCI
Fast Boot -> off
CSM support -> off
All the interfaces on the security I/O -> unlocked (included SATA ODD interface)

Perhaps you enable CSM? Do you use only UEFI mode?

adrian123 · 2020-06-27 16:21:15

Thanks for the suggestion.

Yes I use UEFI, both disks are with the label gpt. Also, enabling csm caused that not only I couldn't access the BIOS settings with 2 disks (both with partitions, if one disk does not have partitions, no problem), I couldn't access the BIOS with only 1 disk. So CSM will stay disabled.

Conclusion: ASUS's fault and seems like I can't do anything to fix it

seth · 2020-06-27 20:11:52

According to thsi manual, https://www.asus.com/de/Laptops/ROG-GL7 … sk_Manual/ the BIOS should allow to edit boot options and boot priority.
Does the sata drive somhow show up there?

adrian123 · 2020-06-28 00:15:23

The BIOS allows to change that, but when I have the nvme and the hdd installed, and both with partitions, the BIOS does not load (after I put the correct password). With CSM enabled, the BIOS didn't show up with only the hdd installed (and it was problematic because it wasn't booting grub, it was booting windows and from there I could not remove an EFI partition in order to be able to see the BIOS settings).

adrian123 · 2020-07-15 16:31:45

I'm sorry I didn't update this earlier, I had exams and other things, so I was busy. I have tried a few things and now I may have a hint of what is going on. (I will also leave it with this "solution")

First I downgraded my BIOS, there is only 2 versions, so I tried with 307 and 308. No improvement.

Later, I discovered with creating only a swap partition in the hdd (with arch), I could go to the BIOS if I pressed f2 once seconds after the ASUS logo appears (maybe I could go there pressing f2 more times, or pressing f2 instantly when the ASUS logo appeared, but that worked for me).

After that, I installed kali linux on the hdd. And the problem appeared again. So I did a few tests and found that after the kali installation, I could only go to the BIOS settings if I pressed once f2 seconds after the ASUS logo appears, and it is necessary that a USB installer is connected (it worked with the kali installer as well as the windows installer) to one of the USB ports.

My guess would be that the BIOS is searching for a USB stick with an installer (I don't know why) and it will loop because it doesn't find it (also, It won't work if I connect the USB stick after going to the BIOS settings). I think I'll leave it as it is.

Thanks for the help

Arch Linux

#1 2020-06-25 23:22:25

Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#2 2020-06-25 23:42:57

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#3 2020-06-26 01:17:40

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#4 2020-06-26 05:28:10

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#5 2020-06-26 05:33:01

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#6 2020-06-26 14:28:37

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#7 2020-06-26 14:35:20

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#8 2020-06-26 14:38:07

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#9 2020-06-26 14:41:54

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#10 2020-06-26 14:48:56

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#11 2020-06-26 14:57:52

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#12 2020-06-26 15:04:40

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#13 2020-06-26 15:15:48

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#14 2020-06-26 15:25:14

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#15 2020-06-26 15:55:38

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#16 2020-06-26 16:10:28

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#17 2020-06-26 17:09:53

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#18 2020-06-26 21:23:20

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#19 2020-06-27 01:42:17

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#20 2020-06-27 04:18:29

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#21 2020-06-27 16:21:15

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#22 2020-06-27 20:11:52

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#23 2020-06-28 00:15:23

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

#24 2020-07-15 16:31:45

Re: Swap partition causes blocked BIOS menu (black screen) [SOLVED]

Board footer