# Lambda Quad: boot stuck on purple Ubuntu loading screen

**URL:** <https://deeptalk.lambda.ai/t/lambda-quad-boot-stuck-on-purple-ubuntu-loading-screen/304>\
**Category:** Technical Help\
**Created:** [May 15, 2018, 9:14pm UTC](https://deeptalk.lambda.ai/t/lambda-quad-boot-stuck-on-purple-ubuntu-loading-screen/304 "2018-05-15T21:14:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mpb](https://avatars.discourse-cdn.com/v4/letter/m/ed8c4c/32.png) [@mpb](https://deeptalk.lambda.ai/u/mpb)\
**Post date:** [May 15, 2018, 9:14pm UTC](https://deeptalk.lambda.ai/t/lambda-quad-boot-stuck-on-purple-ubuntu-loading-screen/304/1 "2018-05-15T21:14:08Z")

</div>

When I boot my computer, it gets stuck on the Ubuntu splash screen with the loading dots. It just hangs on this loading screen forever. See below:

 ![splash](https://us1.discourse-cdn.com/flex019/uploads/deeptalk/original/1X/4caf95210424c00f05bd9f7fb04e294fc8b1e22e.png)

---

<div class="post-metadata">

**Author:** ![mpb](https://avatars.discourse-cdn.com/v4/letter/m/ed8c4c/32.png) [@mpb](https://deeptalk.lambda.ai/u/mpb)\
**Post date:** [May 15, 2018, 9:25pm UTC](https://deeptalk.lambda.ai/t/lambda-quad-boot-stuck-on-purple-ubuntu-loading-screen/304/2 "2018-05-15T21:25:43Z")

</div>

There are many reasons why this might happen. I’ve listed some potential fixes:

**SOLUTION #1 – USE THIS IF YOUR MACHINE HAS A RAID ARRAY**  
When your machine get stuck in the above screen…

- Press CTRL+ALT+F1 simultaneously, then press CTRL+ALT+F7 simultaneously
- The following dialogue should appear:

 ![IMG_5774](https://us1.discourse-cdn.com/flex019/uploads/deeptalk/original/1X/bb62b1e8519b914ce530a283be90d9dc18de7373.jpg)

- Press the ENTER key; you will be dropped into a root shell.

- Use your favorite text editor to open the file /etc/fstab. There will be line like the following:

Comment out this line by adding a `#` to the font of it. It should now look like this:

```auto
#/dev/md0 /data ext4 defaults,nofail,discard 0 0

```

Now reboot the machine; it should no longer hang on the Ubuntu loading screen. However, your RAID will no longer automatically mount on boot. You’ll need to manually mount your raid using a command like:

`sudo mount /dev/md127 /data`

We’re currently looking into the best way to re-name the Linux MD RAID so that it can be consistently mounted using `/etc/fstab`.
