Arch hangs on boot after system update

After I ran 'pacman -Syyu' yesterday, my Arch install won't boot anymore. Instead, it hangs after 'Reached target Graphical Interface' with a blinking underscore. It is the first time I've encountered such problems after running Arch for almost a year and frequently updating. Am I right to assume it might have something to do with the recent kernel/nvidia drivers update?

Keep checking archlinux site - information was posted here https://www.archlinux.org/news/nvidia-340xx-and-nvidia/
PS. mark as [SOLVED]

Similar Messages

Arch won't boot after rEFInd update

I've followed https://wiki.archlinux.org/index.php/UEFI_Bootloaders as closely as I can, but still can't get Arch to boot. It doesn't even get to the boot loader.
uname -m
x86_64
Partitions:
Device Type Name
/dev/sda1 Linux filesystem root
/dev/sda2 Linux filesystem boot
/dev/sda3 EFI System efi
/dev/sda4 Linux filesystem var
/dev/sda5 Linux filesystem home
lsblk
Name Type Mountpoint
sda disk
sda1 part /
sda2 part /boot
sda3 part /boot/efi
sda4 part /var
sda5 part /home
Directory tree:
/boot/
efi/
EFI/
arch/
initramfs-arch-fallback.img
initramfs-arch.img
refind_linux.conf
vmlinux-arch.efi
refind/
icons/
refind.conf
refind_x64.efi
initramfs-linux-fallback.img
initramfs-linux.img
vmlinuz-linux
/boot/efi/EFI/arch/refind_linux.conf:
"Default boot" "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=graphical.target"
"Boot to terminal" "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=multi-user.target"
ls -l /dev/disk/by-partuuid/
lrwxrwx 1 root root Jan 30 1:08 d368616d-a423-4511-88df-f2f645079bab -> ../../sda1
efibootmgr -v
BootOrder: 0018, ...
Boot0018* Arch Linux (rEFInd) HD(3,0,0,74930800)File(EFI\refind\refind_x64.efi)
Anything else I'm missing? By the way, I think this is related to the Jan 27. update to refind. Today was the first time I've rebooted my computer since then.
Also - I tried both commenting and uncommenting scan_all_linux_kernels in refind.conf. No dice.
Thank you very much!
EDIT: Some updates...
I was poking around the UEFI shell. The following commands caused my computer to hang (I had to hard-restart):
Shell> fs0:
FS0> ls
I could ls just fine using shell 1.0, but shell 2.0 caused a hang. Then, after the hard restart, more strange behavior:
Shell> bcfg boot add 0 fs0:\EFI\refind\refind_x64.efi "Test"
Error. The file 'fs0:\EFI\refind\refind_x64.efi' did not open.
Also, I can "bcfg boot dump" just fine, but if I want to scroll through the output, I get an error, and it hangs, so I have to hard restart again.
Shell> bcfg boot dump
// bunch of output
Shell> bcfg boot dump -b
// after printing five boot entries...
Press ENTER to continue or 'Q' to break:
ASSERT_EFI_ERROR (Status = Not Ready)
ASSERT c:\dev\edk2top\ShellPkg\Library\UefiShellLib\UefiShellLib.c(3223) : !EFI_ERROR (Status)
Not sure if any of that last but is relevant. Thanks again.
Tried downgrading kernel to 3.6, still won't boot.
Last edited by MitchellSalad (2013-01-30 20:05:10)

MitchellSalad wrote:
Partitions:
Device Type Name
/dev/sda1 Linux filesystem root
/dev/sda2 Linux filesystem boot
/dev/sda3 EFI System efi
/dev/sda4 Linux filesystem var
/dev/sda5 Linux filesystem home
/boot/efi/EFI/arch/refind_linux.conf:
"Default boot" "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=graphical.target"
"Boot to terminal" "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=multi-user.target"
ls -l /dev/disk/by-partuuid/
lrwxrwx 1 root root Jan 30 1:08 d368616d-a423-4511-88df-f2f645079bab -> ../../sda3
Shouldn't that be sda1? Your root-partition is /dev/sda1.

Can't boot after system update: unknown filesystem type

After running a system update, including updating the kernel, I can't boot to the new kernel.
On booting, grub loads the kernel image, runs/loads udev, but then fails to mount the root partition with error:
mount: unknown filesystem type 'ext4'
I have tried reinstalling the 'linux' package via packman several times, also trying the --recursive argument to make sure all my dependencies were there, and after days of googling and tweaking my system, I'm at a loss.
Thank goodness I happened to keep a spare kernel laying around in /boot.
Thanks in advance.
Last edited by jackrabbit (2012-03-22 23:25:28)

The OP can read their partition initially though, it's only after udev that they can't.
Also, try adding "rootfstype=ext4" to your grub kernel line. Is your /boot on a separate partition or part of your / partition?

Yosemite hangs in booting after applying Update 2015-003.

I have applied Update 2015-003 to Yosemite.
After booting the progress bar hangs at about 30% for over an hour.
The hardware is a MacBook Pro with a SSD harddrive.

Take each of these steps that you haven't already tried. Stop when the problem is resolved.
To restart an unresponsive computer, press and hold the power button for a few seconds until the power shuts off, then release, wait a few more seconds, and press it again briefly.
Step 1
The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
Step 3
Sometimes a startup failure can be resolved by resetting the NVRAM.
Step 4
If a desktop Mac hangs at a plain gray screen with a movable cursor, the keyboard may not be recognized. Press and hold the button on the side of an Apple wireless keyboard to make it discoverable. If need be, replace or recharge the batteries. If you're using a USB keyboard connected to a hub, connect it to a built-in port.
Step 5
If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
Step 6
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
Step 7
If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
Start up in safe mode. Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 8
Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
Step 9
If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.
Step 10
Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 11
Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
Step 12
This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 13
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

Can't boot after system update - INIT: No inittab file found

Hi i've a pc where i installed arch linux more than one year ago
Its a:
PentiumII 400mhz
192mb ram
2 harddrives (don't know if i use them as a lvm or if each consists of 2 partitions used as mountpoints)
graphic card nvidia TNT2
i wanted to update it using "pacman -Syu" but it didnt worked because TNT2 needed nvidia legacy treiber 71xx don't work with kernel > 2.6.26
so i removed currently used nvidia treiber with pacman and installed the xf86-nv driver using pacman...
after that i think i updated just the kernel (pacman -S kernel26)
and than the system (pacman -Syu)
that was successfully....but after my reboot the shock
INIT: No inittab file found
Enter runlevel:
doesnt matter what runlevel i try i can't get further
what should i do now? please help me and provide me something like a step by step guide

menhir wrote:
what kind of live cd should i use?
is there a arch live cd that has the initscripts package include that i don't require to have my wlan working?
where can i find a good tutorial for "chroot" rescue in my case?
Just use the Arch installation disc

Hangs during boot after Security Update 2007-006 Installed

Hello out there,
As I said in the Subject, I installed Security Update 2007-006 on my MacBook Pro running OSX 10.4.9 and now it wont boot. just from playing around with it in single user mode I think it hangs sometime when configd is starting, but I don't know exactly when or why it's not booting correctly.
Any suggestions on what to do? Any help would be greatly appreciated.
MacBook Pro Core Duo Mac OS X (10.4.9)
Mac OS X (10.4.9)

The A&I, saving user and network settings, installation, just moves all current OS required stuff into a previous system folder and installs all new OS stuff. Afterwards, you'll have to bring it up to the latest version. It doesn't wipe the HD. If that doesn't work, then you can try via the other computer. If neither work, then you'll be forced to do an erase and install. That's why a bootable backup/clone is so valuable.

Lack of 3g after system update

Hello :-)
It's problem with Xperia E dual
Few days ago I updated the system to the 4.1.1 version (compilation 11.3.A.1.39).
Unfortunatelly after updating I've discovered that smartphone don't works with 3G. On the display I've only icon "E". Before updating there was typically "H". Of course now the transfer is slower than before and of course I'm not happy of that.
I try to solve this problem - choose in menu list of available provider and... there are only 2G nets. Because I've functioning still in the same place of live and the problem has occured after the updating I'm sure that it's strictly connected.
Is there any solution for that?
Another problem is with trying to call. After system updating typically twice a day I have to restart smartphone because it's totally hanged. No one can connect with me and I can't call to anybody. Smartphone looks normally and doesn't give any siglan that something is wrong. But when I try to connect to somebody I direst the number and... there is no signal at all. After few seconds telephon return to main menu. There is also no record about this trial of connection in the list of done connections. It's very uncomfortable situation.
Sure, there are also some adventages with the system updating but problems mentioned above are really annoing.
Have you any solutions for it?
Thanks in advance.
Rafal
Solved!
Go to Solution.

Hi, try repairing phone software with PC Companion or Update Service.
http://www.sonymobile.com/gb/tools/pc-companion/
http://www.sonymobile.com/gb/tools/update-service/
Be aware that this will erase phone data completely, backup if necessary.
Before proceeding with software repair, confirm with your Network Operator that there is nothing wrong with the network. Also, remove and reinsert SIM card and try again (have a close look at the contact surface, ensure that it is relatively clean).
Don't forget to mark correct answer as Accepted Solution.
If you find the post helpful, press Kudos.

Macbook pro won't boot after installing update 10.9.3

macbook pro won't boot after installing update 10.9.3

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode.
Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

[SOLVED] Arch won't boot after I created a separate /var parition

Arch won't boot after I created a separate /var parition on an existing installation.And let me confess: it was maybe stupid trying to do it on an existing install.
I edited the fstab correctly, copied the files using rsync preserving permissions. Then I kept a backup of /var using tar. Then went on to delete everything under /var, ie /var/*, the /var folder is still there. All this I did from a live CD. After that I booted into my arch linux. Here I get messages about systemd successfully finishing fsck on each of my partitions, then the screen starts blinking. And there is no more output. Pressing Ctrl+Alt+Delete causes systemd to stop its services and reboot.
Having realized I had borked my system, I removed the /var line from fstab and restored /var from the tar file I made earlier. Again I did this from a live cd. Rebooted into my arch system, and again similar issues, namely that after fsck and messages informing a few services had started, the screen keeps blinking.
The live cd I used for reorganizing my partitions was elementary OS freya. They have GParted in there. I also have an arch install iso lying aroung from May 2013. If necessary, I can download the latest version. I am currently typing from a Windows installation I dual boot from.
I don't know how to extract any boot logs as I am locked out of the system. Here is my fstab in any case:
# Filesystem information
# /dev/sda5 LABEL=fs_root
UUID=b9d739cf-fd8c-46dd-a919-bd827dc47c66 / ext4 rw,noatime,data=ordered 0 1
# /dev/sda9 LABEL=fs_var
UUID=ec0f7a49-dccd-43ab-8651-9aa3fdb41cc7 /var ext4 rw,noatime,data=ordered 0 2
# /dev/sda2 LABEL=fs_boot
UUID=0e8ab31a-3bda-4b85-a901-a36f21b1583d /boot ext2 rw,noatime 0 2
# /dev/sda6 LABEL=fs_home
UUID=d9e63c47-274e-447f-ad01-0d97afe0fd34 /home ext4 rw,noatime,data=ordered 0 2
# /dev/sda7 LABEL=fs_swap
UUID=7301227c-e9f3-41b8-9d0f-4cf3c159491c none swap defaults 0 0
# /dev/sda3 LABEL=fs_win
UUID=12B639D1B639B5D7 /fs_win ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,nofail,noauto,x-systemd.automount 0 0
# /dev/sda3 LABEL=fs_share
UUID=D272269772268079 /fs_share ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,noauto,nofail,x-systemd.automount 0 0
I would greatly appreciate any help.
Last edited by richcocoa (2015-05-03 18:04:44)

Have you moved everything from /var to /new_var (i named it for learning purpose)? You shoud copy content from /var but not on the fly but booting from arch iso cd, and than you shoud mount your / into arch-chroot environement, mount all of your mount points and than copy content from default /var to new /var. The copying should be done with this
cp -rax
and you can add -v switch to verbose output. I have my own /var moved the same way.
The simples way is:
-boot the arch iso cd
-mount all of your mount point (i created here in this step /new_var to move /var to a new place, and this /new_var i put in /etc/fstab as /var later)
-copy /var to /new_var with -rax or -vrax (recursive, archive, this filesystem or verbose, recursive, archive, this filesystem switches)
-umount all of it
-reboot.
Last edited by firekage (2015-05-02 07:49:20)

Wont boot after windows update

M y Sateite A305 s6916 wont boot after windows updates tried to install.

Satellite A305-S6916
tried .. every option on F8
Try this. Download a repair disc from here.
   Windows Vista Recovery Environment ISO X64 version (64 bit)
If you can reach the Recovery Environment by booting that, try the Startup Repair and let us know what happens. Sometimes you need to run it more than once.
   Startup Repair: frequently asked questions
Also try a System Restore.
   What are the system recovery options in Windows Vista?
-Jerry

Leopard USB install no longer boots after software update

Hi all,
I have recently installed Leopard onto a USB partition in order to perform maintenance on my main Leopard installation. Installation proceeds without a problem however after downloading software updates the USB partition will not boot successfully, despite there being no problems with the disk / volume structures / apparently anything at all. In desperation I also tried to install Tiger, which worked, however I have the same problem after updating - it will not boot! I don't think my hardware is at fault - Techtool Pro tells me all is in order.
Has anyone had this problem and if so, how did you fix it?
Thanks,
Jason

I just installed Leopard onto a USB 2.0 external hard drive for a dual-boot. It booted fine at 10.5.1 but is taking ridiculously long to boot after 10.5.2 (I just got it to finally boot after the update while waiting more than 40 minutes!).
It seems that you may want to attempt booting several times - maybe turning off the machine in between or booting to the internal OS first and then to the external. Can't help you much beyond that as this is my introductory experience with this mess.

My iMac running very slow some times its hang, its happened after I update Lion, please anybody advice me what to do?

My iMac running very slow some times its hang, its happened after I update Lion, please anybody advice me what to do?

See:
Mac Maintenance Quick Assist,
Mac OS X speed FAQ,
Speeding up Macs,
Macintosh OS X Routine Maintenance,
Essential Mac Maintenance: Get set up,
Essential Mac Maintenance: Rev up your routines,
Maintaining OS X,
Five Mac maintenance myths, and
Myths of required versus not required maintenance for Mac OS X for information.

How to turn off alarm after system update?

I get alarm when restarting my T400 after system update. Can anyone give me suggestions to turn off this alarm?
Thanks,

I have no display > powercontrol in openbox, gnome or fluxbox, What are you talking about?

Initramfs seems broken, system hangs at boot after gummiboot menu

Did a full system update yesterday, and when rebooting the system hanged directly after the gummiboot menu with a black screen and a rainbowlike-colored bar in a pattern that looks like pink noise covering the top 10% of the screen. It seems to be a problem when loading the initial ramdisk. I have tried rebuilding with mkikitcpio, tested downgrading the kernel and rebuilding initramfs, triple-double-checked the filenames, and even verified that it doesn't look like that when the filenames are wrong. I also tried simply reinstalling the latest kernel from a chroot, but it didn't help.
I have pinned down the problem to the initial ramdisk, but can't figure out what else to do with this. I don't really want to do a full reinstall if it's possible to avoid. The system is a lenovo thinkpad w530 and I boot arch linux in uefi mode using gummiboot.

Unfortunately, no, I still use EXT4 on my system. However, what do you mean when you say "got unmarked as the default one"? Is that something local to rEFInd, or what do you mean?
I have tried downgrading to Linux 3.7.5-1, but that did not help unfortunately. My system worked with 3.7.5-1, when I upgraded to 3.7.6-1 it stopped working, and downgrading didn't help. I'll try downgrading to a 3.6 version though.
Last edited by MFserver (2013-02-10 22:34:10)

[Solved] UEFI. System hangs on boot after successfully activating swap

Alright.
Unnecessary Background:
I've been using Arch for years. I just bought a stupidly good computer with a bunch of specs that I don't think are relevant, except for the fact that I am using an X99-pro. It has RAID support, but I am not using that currently. I bought all the parts and finished constructing it this morning (I live in Japan, so that was a while ago). Normally, I have no problems with installation; however, I wanted to do this one UEFI mode. After booting into the live disk, I checked to make sure everything was working as it should. Arch recognized my graphics card, most of my ram (one of the cards is a bit finicky for some reason), my SSD and HDD, along with the built-in WiFi (although it is an annoying broadcom one, so I need to install the driver separately later). Now, there are plenty of sources of error in here:
Problem:
I got through the arch installation and tried gummiboot. It would hang every time after successfully activating swap. I tried grub, too, but had the same problem. Because gummiboot is much less cumbersome, I switched back to that. Interestingly, systemd will sometimes recognize my drive twice before activating swap, and if I edit my fstab to ignore the swap completely, it hangs on the next step with is mounting the boot partition. I would like to point out that because I am not able to successfully boot my system, I cannot provide the exact messages for you guys, which may pose a problem.
Solutions I have tried:
1. Chrooting / mkinitcpio -p linux
2. modifying fstab / removing swap from it completely
3. fresh re-install
Sources of error:
1. Construction. Everything seems appropriate on the live usb, but maybe there is a problem in which ports I used for the SSD and HDD
2. UEFI. It could be that UEFI just doesn't like mounting multiple things and freezes up when put on the spot.
3. Legacy. It could be that this is not a problem with UEFI or my construction, but something I missed in the installation.
Additional info:
Partitioning scheme:
sda1: ~500MiB boot / EFI partition
sda2: ~4G swap
sda3: ~110G /
sdb: ~2T, untouched (for storage later)
I apologize for any typos and hope it was readable. I am super exhausted and going to take a nap. I'll check back in on this in the morning.
Last edited by Leios (2015-02-08 00:16:27)

Please post the output of:
# gdisk -l /dev/sda
lsblk -f
And the contents of your gummiboot loader.conf and arch.conf (or whatever you've called it).
Post the output of the commands after you have mounted all your partitions and (arch-)chroot'd into your system.
You can use wgetpaste to post the outputs, as described by @ewaller here:
https://bbs.archlinux.org/viewtopic.php … 8#p1500528
Alternatively, pipe the command output to a text file and export it (using a live distribution or a USB stick).
You should remove swap from your fstab -- systemd mounts it automatically anyway.

Arch hangs on boot after system update

Similar Messages

Maybe you are looking for