# Error installing StartOS on an ARM SBC

**URL:** <https://community.start9.com/t/error-installing-startos-on-an-arm-sbc/418>\
**Category:** DIY Community\
**Created:** [June 11, 2023, 3:44pm UTC](https://community.start9.com/t/error-installing-startos-on-an-arm-sbc/418 "2023-06-11T15:44:35Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![laconick](https://community.start9.com/letter_avatar_proxy/v4/letter/l/df788c/32.png) [@laconick](https://community.start9.com/u/laconick)\
**Post date:** [June 11, 2023, 3:44pm UTC](https://community.start9.com/t/error-installing-startos-on-an-arm-sbc/418/1 "2023-06-11T15:44:35Z")

</div>

Hi, I’m trying to install StartOS on an Odroid-M1 SBC, I’m using the aarch64 image flashed on an USB stick.  
I managed to boot from the USB (with some tweaks) and the browser opens the StartOS setup page. I’ve installed a Samsung 970 evo plus NVMe M.2 SSD that is detected by the system and displayed as an option when I’m asked to select a disk for installation. The next page, Install Type, presents only one button: Install StartOS. Clicking on it, a pop up message warns that this action will completely erase the disk, that’s fine, accepted, but the process stops with the red message:  
_RPC ERROR: Disk Management Error mkfs.vfat: unable to open /dev/nvme0n1p1: No such file or directory_  
Any ideas?  
Thanks for helping

---

<div class="post-metadata">

**Author:** ![George](https://community.start9.com/user_avatar/community.start9.com/george/32/91_2.png) [@George](https://community.start9.com/u/George)\
**Post date:** [June 11, 2023, 9:30pm UTC](https://community.start9.com/t/error-installing-startos-on-an-arm-sbc/418/2 "2023-06-11T21:30:03Z")

</div>

I’m not sure exactly what the problem could be but when we had users getting this error on the raspi, we had them:

Insert disk into another computer  
Use the disk utility to wipe all partitions  
Create a new partition and format it with exfat (or whatever fs)  
replace it into the server you’re trying to install StartOS on

Then try again. The installer doesn’t wipe partitions so if it doesn’t exactly like the partitions you’ve already setup, errors will occur.

There’s an (yet unfixed) issue about it here:  
[https://github.com/Start9Labs/start-os/issues/2168](https://github.com/Start9Labs/start-os/issues/2168)

Please let us know if this does or doesn’t work.

---

<div class="post-metadata">

**Author:** ![laconick](https://community.start9.com/letter_avatar_proxy/v4/letter/l/df788c/32.png) [@laconick](https://community.start9.com/u/laconick)\
**Post date:** [June 12, 2023, 12:08pm UTC](https://community.start9.com/t/error-installing-startos-on-an-arm-sbc/418/3 "2023-06-12T12:08:56Z")

</div>

That was the problem. Thank you very much.  
I haven’t been able to finish the installation yet, bu this is one step forward.

---

<div class="post-metadata">

**Author:** ![start9dave](https://community.start9.com/user_avatar/community.start9.com/start9dave/32/6_2.png) [@start9dave](https://community.start9.com/u/start9dave)\
**Post date:** [June 12, 2023, 8:09pm UTC](https://community.start9.com/t/error-installing-startos-on-an-arm-sbc/418/4 "2023-06-12T20:09:59Z")

</div>

We’d love to add an ODroid to our [Known-Good Hardware List](https://community.start9.com/t/known-good-hardware-master-list-hardware-capable-of-running-startos/66). Let us know if you get it running!

---

<div class="post-metadata">

**Author:** ![laconick](https://community.start9.com/letter_avatar_proxy/v4/letter/l/df788c/32.png) [@laconick](https://community.start9.com/u/laconick)\
**Post date:** [June 20, 2023, 5:04pm UTC](https://community.start9.com/t/error-installing-startos-on-an-arm-sbc/418/6 "2023-06-20T17:04:32Z")

</div>

> [@start9dave](#):
>
> Let us know if you get it running!

I give up. I’d say that at the moment it’s not possible. Sorry

---

<div class="post-metadata">

**Author:** ![start9dave](https://community.start9.com/user_avatar/community.start9.com/start9dave/32/6_2.png) [@start9dave](https://community.start9.com/u/start9dave)\
**Post date:** [June 22, 2023, 3:29pm UTC](https://community.start9.com/t/error-installing-startos-on-an-arm-sbc/418/7 "2023-06-22T15:29:23Z")

</div>

We have a long list of hardware to test - I’ll add this to it, as I have an old ODroid laying around, but it may take some time. It will be posted to the master hardware list if/when we get it sorted. Thanks for your efforts!

---

<div class="post-metadata">

**Author:** ![laconick](https://community.start9.com/letter_avatar_proxy/v4/letter/l/df788c/32.png) [@laconick](https://community.start9.com/u/laconick)\
**Post date:** [June 23, 2023, 12:51pm UTC](https://community.start9.com/t/error-installing-startos-on-an-arm-sbc/418/8 "2023-06-23T12:51:47Z")

</div>

Thank you, appreciated.  
A couple of hints, since I’ve already gone through this:

1. the firmware supplied by the manufacturer doesn’t support EFI boot, there is workaround explained [here](https://forum.odroid.com/viewtopic.php?p=370800#p370800).
2. Mainline kernel support for the Rockchip RK3568 has been added in 6.2.0-rc1, while currently StartOS is using an 6.1.0 kernel. Looks like someone has been able to make the M1 work even with 5.18, but I’m not one of those ☹

I’ll keep an eye on the forum.

---

<div class="post-metadata">

**Author:** ![start9dave](https://community.start9.com/user_avatar/community.start9.com/start9dave/32/6_2.png) [@start9dave](https://community.start9.com/u/start9dave)\
**Post date:** [June 23, 2023, 1:48pm UTC](https://community.start9.com/t/error-installing-startos-on-an-arm-sbc/418/9 "2023-06-23T13:48:50Z")

</div>

Good to know, thank you for the tips. Quick note that EFI boot is not required, you can definitely boot in Legacy. In regard to kernel RCs, we are very unlikely to go that bleeding edge, as kernel updates are already a source of strife. We will keep an eye on it as that version stabilizes however.

---

<div class="post-metadata">

**Author:** ![lip](https://community.start9.com/letter_avatar_proxy/v4/letter/l/eb9ed0/32.png) [@lip](https://community.start9.com/u/lip)\
**Post date:** [August 10, 2024, 5:29pm UTC](https://community.start9.com/t/error-installing-startos-on-an-arm-sbc/418/10 "2024-08-10T17:29:08Z")

</div>

I am also interested on running start 9 on an odroid M1.

---

<div class="post-metadata">

**Author:** ![Swerl](https://community.start9.com/letter_avatar_proxy/v4/letter/s/e47774/32.png) [@Swerl](https://community.start9.com/u/Swerl)\
**Post date:** [August 27, 2025, 3:57pm UTC](https://community.start9.com/t/error-installing-startos-on-an-arm-sbc/418/11 "2025-08-27T15:57:34Z")

</div>

Hi @George !  
I’m having a similar error mentionned above when trying to install Start9 on a Dreamquest mini-pc. After pressing “Install StartOS”, i get this error:

RPC ERROR: Disk Management Error mkfs.vfat: unable to open /dev/sdal: No such file or directory

I saw your solution post from June 2023. When you say “Insert disk into another computer” as step 1, are you talking about the USB stick that’s been flashed, or the 1Tb SSD inside the mini-pc? I’m sorry i’m a beginner in this hehe. The USB stick is brand new and already formatted to exfat, so I’m wondering why it doesn’t work. I read that Fat32 might work better in some cases?

By the way, I’m using “startos-0.3.5.1-39de098\_x86\_64-nonfree” on the USB stick.

Thank you for helping!

---

<div class="post-metadata">

**Author:** ![Swerl](https://community.start9.com/letter_avatar_proxy/v4/letter/s/e47774/32.png) [@Swerl](https://community.start9.com/u/Swerl)\
**Post date:** [August 27, 2025, 4:59pm UTC](https://community.start9.com/t/error-installing-startos-on-an-arm-sbc/418/12 "2025-08-27T16:59:18Z")

</div>

Actually, problem might be happening sooner in the process.  
I realized that when booting the Mini pc with the USB-stick with non-free StartOS iso on it (also Secure boot disabled in BIOS), i’m stuck at this error page that keeps refreshing every 5-10 seconds. The 2nd image is another error page that appears only once about audio codecs missing, but then i comes back to the 1st image on repeat. I tried booting with no monitor/HDMI attached and going to start.local, still get the same error.

I have a Dreamquest minipc, Intel N150, 16GB DDR4, 1TB M.2 SSD

Any idea? Thanks!

 ![01](https://community.start9.com/uploads/default/original/2X/8/82127c06fa3078fa4aba56e86828c065b13cdb0c.jpeg)  
 ![02](https://community.start9.com/uploads/default/original/2X/c/c4d25c5a0c3e0135dc6d01c2e2d8b17710fb13f8.jpeg)

---

<div class="post-metadata">

**Author:** ![Swerl](https://community.start9.com/letter_avatar_proxy/v4/letter/s/e47774/32.png) [@Swerl](https://community.start9.com/u/Swerl)\
**Post date:** [August 30, 2025, 2:46am UTC](https://community.start9.com/t/error-installing-startos-on-an-arm-sbc/418/13 "2025-08-30T02:46:52Z")

</div>

Is it possible the problem comes from the fact that I’m flashing from a 128Gb usb stick? I read that flashing with stick over 32Gb can sometimes cause problems. I just ordered a 16Gb one, should arrive in 2 days, will keep you posted.

---

<div class="post-metadata">

**Author:** ![George](https://community.start9.com/user_avatar/community.start9.com/george/32/91_2.png) [@George](https://community.start9.com/u/George)\
**Post date:** [October 15, 2025, 10:32pm UTC](https://community.start9.com/t/error-installing-startos-on-an-arm-sbc/418/14 "2025-10-15T22:32:38Z")

</div>

> [@Swerl](#):
>
> stuck at this error page that keeps refreshing every 5-10 seconds. The 2nd image is another error page that appears only once about audio codecs missing, but then i comes back to the 1st image on repeat. I tried booting with no monitor/HDMI attached and going to start.local, still get the same error.

Sorry for the slow response, I just saw this.

Inability to see the gui of the installer after booting the USB means either your monitor or graphics card in the pc is not supported even by the closed-source drivers included in the non-free ISO from the debian non-free repos. I’d try another monitor – but no matter, you should still be able to reach [http://start.local](http://start.local) via the network and see the same page that would be displayed on the monitor, and proceed from there, unless the PC’s network drivers are also not available.
