# Installing UmbrelOS 1.2.1 on 8tb Drive

**URL:** <https://community.umbrel.com/t/installing-umbrelos-1-2-1-on-8tb-drive/18485>\
**Category:** Support and Troubleshooting\
**Created:** [July 23, 2024, 4:29am UTC](https://community.umbrel.com/t/installing-umbrelos-1-2-1-on-8tb-drive/18485 "2024-07-23T04:29:30Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![aeon](https://avatars.discourse-cdn.com/v4/letter/a/57b2e6/32.png) [@aeon](https://community.umbrel.com/u/aeon)\
**Post date:** [July 23, 2024, 5:12pm UTC](https://community.umbrel.com/t/installing-umbrelos-1-2-1-on-8tb-drive/18485/4 "2024-07-23T17:12:12Z")

</div>

Ok so usually this bug can be observed on virtual machines, but apparently it’s also found on phyiscal machines. I found one of the threads where the same behaviour is described:

> [@UmbrelOS 1.1.1 on a Intel NUC has /data filesystem full](https://community.umbrel.com/t/umbrelos-1-1-1-on-a-intel-nuc-has-data-filesystem-full/16883/6):
>
> Hey @Ebelloli sorry this slipped under our radar, would you be able to get us the full logs from your device so we could take a look at what went wrong with the fs expansion logic? You can get them with sudo journalctl | gzip \> journal.log.gz You can DM it to me if you don’t want to post your logs publicly. Also does rebooting solve the issue? The filesystem expansion logic runs on each boot so potentially if something went wrong on the first boot and reboot could resolve it.

Afaik @lukechilds has been interested in solving this issue. Maybe you can post your system logs here for him.

edit: here’s another thread:

[https://community.umbrel.com/t/after-fresh-install-no-disk-space](https://community.umbrel.com/t/after-fresh-install-no-disk-space)

---

_[View the full topic](https://community.umbrel.com/t/installing-umbrelos-1-2-1-on-8tb-drive/18485)._