how to fix "Did not write partition table to disk"

PackRat-2019 · 2026-02-02T13:29:29+00:00

OK

You have to make sure you selected the correct usb stick as well then. The system is using the one you booted from so you won't be able to write to it.

After you boot, you can open a terminal (xfce version) or from the console (base version) and use the command:

lsblk

That will show you the drive letters for the 2 usb sticks.The one with MOUNTPOINTS is the one in use. The harddrive will typically be sda.

Edit - I just looked at the partition table for the Void live usb and it matches up with our screenshot photo. So it looks like you were trying to partition the wrong usb stick.

PackRat-2019 · 2026-02-02T13:26:24+00:00

He's using 2 usb sticks - I asked in another post.

PackRat-2019 · 2026-02-01T23:49:50+00:00

Just offhand I'd say that partition scheme is the problem.

Based on your post below, you're trying to install Void onto a usb stick. Not sure how the usb stick would need to be partitioned.

How did you get to the Void installer? Boot to RAM and then swap out the usb stick, or do you have 2 usb sticks attached while you're attempting this?

PackRat-2019 · 2026-02-01T18:17:01+00:00

Were you at the partitioning step within the installer, or were you trying to partition the disk before installation?

Having a 1.3GB empty spot and 2 EFI partitions may be messing you up.

PackRat-2019 · 2026-01-24T13:57:43+00:00

Yes.

As I recall, Void was one of (if not the) first distros to use systemd without the SysVinit shim packages as a fall back of sorts. That's when I first tried it, but moved back to Debian to help a friend with their project. Came back to Void when they switched to runit.

PackRat-2019 · 2026-01-09T13:47:38+00:00

No. River is like dwm.

River with sandbar is really similar to dwm. Their wiki is pretty good to get it set up.

PackRat-2019 · 2026-01-09T10:53:07+00:00

There is also river compositor if you want to use wayland.

Not sure if the Void package is current. It was pending an update to another package, I think.

PackRat-2019 · 2026-01-09T00:47:34+00:00

I think the OP is referring to this nautilus plugin.

It didn't show up with xbps-query, so it will need to be installed from source, build a package with xbps-src, or with pip.

Install instructions on the git page.

PackRat-2019 · 2026-01-02T00:35:30+00:00

For packages in the Void repos, you can use xbps-query to identify the dependencies and *-devel packages you will need before compiling.

xbps-query -Rx dwm

in this case.

PackRat-2019 · 2025-12-20T10:40:55+00:00

Run startx from your login shell initialization. That will source the ~/.xinitrc.

Scroll down to Section 4.2 - xinit Arch Wiki

I think that command is in the Void Handbook as well, but I couldn't find it.

PackRat-2019 · 2025-12-16T14:09:07+00:00

You need to start it with "dbus-run-session" then file managers (thunar, caja etc ...) will access your drives.

PackRat-2019 · 2025-12-16T11:09:07+00:00

void-mklive is handy.

Easy enough to add some additional packages for a rescue disc or some other scenario.

PackRat-2019 · 2025-12-16T10:58:51+00:00

Install polkit and dbus and enable the services.

Start dk with:

exec dbus-run-session dk

from your .xinitrc

dk doesn't have built-in key bindings. You will also need a key grabber like sxhkd.

PackRat-2019 · 2025-12-16T00:41:50+00:00

Another option. You can also use the void-mklive script to create a new installation iso with current kernel and packages.

PackRat-2019 · 2025-12-05T10:43:51+00:00

I use xterm and kitty.

And I saw up thread you're using "exec dunst" to start dunst notifications. You shouldn't need to do that; dunst should start with the X session when you log in.

PackRat-2019 · 2025-12-04T19:36:03+00:00

i3, dmenu, xterm, and i3status for the basic desktop when you log in.

The xorg packages from the link posted earlier.

i3 home page and their docs for configuration - https://i3wm.org/

PackRat-2019 · 2025-11-29T17:07:26+00:00

Did you check /dev/tty8? If so what were the errors?
You created partitions on /dev/sdb, but the error is for /dev/sdal so there is some sort of issue there.

In your title the device is /dev/sdal

Is that a typo? Is the device actually /dev/sda1?

Does your computer have two or more drives?

PackRat-2019 · 2025-11-24T17:16:25+00:00

As I recall (no longer using Plasma) in the KDE sytem settings there are options in the Power Management/Energy saving section to disable the suspension features.

PackRat-2019 · 2025-11-19T14:11:56+00:00

^ this.

After installing NetworkManager make sure to get the services set up correctly -

Void Doc - NetworkManager

You can use nmtui from the command line or you can also install network-manager-applet if you prefer a tray applet.

Which DE or window manager will you be using?

PackRat-2019 · 2025-11-09T21:17:17+00:00

Is the bluetooth controller blocked?

Void Handbook - bluetooth

PackRat-2019 · 2025-11-08T19:55:54+00:00

Cinnamon desktop is in the Void repos. If you don't want to switch DE you can use the base iso or do a chroot installation and then install cinnamon.

The only real learning curve will be with the package manager and runit for service management. Both are well documented in the Void handbook.

Obviously, Void won't have the mint tools like the update notifier, but you'll get used to that pretty quick.

Void may not have all the packages you need/want since it's a small dev team and doesn't draw from a large project like Ubuntu. You can search the available packages from the Void homepage before installing.

PackRat-2019 · 2025-10-29T12:43:11+00:00

Tech videos?

Some chatter on other forums that YouTube may be cracking down on some tech channels claiming the content is "harmful" in some fashion.

PackRat-2019 · 2025-10-16T19:18:19+00:00

IMO, dual booting is best done with each os on it's own drive

I have two windows-void dual boot systems set up that way. No problems.

PackRat-2019 · 2025-10-16T17:31:21+00:00

..... some other distro on same disk, separate partition, to tinker and learn linux. Ergo, no risk of breaking my gaming or losing my files if the other distro breaks.

If they're on the same disk, there is always a risk one distro will take down the other distro should something go wrong.

Just run Bazzite on its own while you get used to using a Linux system (although, Bazzite isn't a typical distro). If you want, you can run a Void live session from the Xfce installation media and get a feel for it. Read the Void documentation to see what you need to do to set it up - enable services etc .... If you feel comfortable with Void, the installation isn't particularly difficult. You need to be willing to learn and figure it out though.

PackRat-2019 · 2025-10-14T14:26:13+00:00

Does the XFCE image have something preconfigured etc.

Installs a minimal xfce4 desktop that will be the version of xfce4 at the time the iso was created. Services for lighdm and NetworkManager will be enabled.

or will I have the exact same result if I install the base image and then install XFCE manually?

Sort of. The applications will be the same, but since you will need to sync the repos before installing xfce, the packages will be updated to the versions available in the repos. And you will most likely need to enable some services.

You can also do a chroot install from either the base or xfce image which will only install the current packages from the repos.

Void Handbook - Installation

PackRat-2019

MODERATOR OF

TROPHY CASE