# Issue with Intel® NUC tutorial

**URL:** <https://hub.mender.io/t/issue-with-intel-nuc-tutorial/1010>\
**Category:** General Discussions\
**Tags:** yocto, intel, thud\
**Created:** [September 12, 2019, 5:33pm UTC](https://hub.mender.io/t/issue-with-intel-nuc-tutorial/1010 "2019-09-12T17:33:47Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![SteeveGLDev](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/steevegldev/32/349_2.png) [@SteeveGLDev](https://hub.mender.io/u/SteeveGLDev)\
**Post date:** [September 12, 2019, 5:33pm UTC](https://hub.mender.io/t/issue-with-intel-nuc-tutorial/1010/1 "2019-09-12T17:33:47Z")

</div>

I have a issue with the tutorial [Intel® NUC](https://hub.mender.io/t/intel-nuc/308)

All build with success. When I put the \*.uefiimg.bz2 file on an USB drive, I got an error. It’s look like a kernel panic.

 ![IMG_20190912_133124](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/1X/40f054b7f20e020ee91a0b67a5c6ac37071fbe95.jpeg)

---

<div class="post-metadata">

**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\
**Post date:** [September 12, 2019, 8:20pm UTC](https://hub.mender.io/t/issue-with-intel-nuc-tutorial/1010/2 "2019-09-12T20:20:32Z")

</div>

The relevant bits seem to have scrolled off the screen but I suspect it’s just not able to find the root filesystem device. The default setting in the meta-mender-intel layer is /dev/mmcblk0:  
{quote}  
MENDER\_STORAGE\_DEVICE = “/dev/mmcblk2”  
MENDER\_GRUB\_STORAGE\_DEVICE = “hd0”  
{quote}

It’s likely that on your NUC those device nodes need to be updated. I suspect “hd0” is fine for Grub but you need to figure out exactly what the rootfs device node is. I have a NUC that uses /dev/nvme-something but it will vary depending on the type of disk in your system.

---

<div class="post-metadata">

**Author:** ![SteeveGLDev](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/steevegldev/32/349_2.png) [@SteeveGLDev](https://hub.mender.io/u/SteeveGLDev)\
**Post date:** [September 12, 2019, 8:39pm UTC](https://hub.mender.io/t/issue-with-intel-nuc-tutorial/1010/3 "2019-09-12T20:39:47Z")

</div>

I’m trying to boot on the usb drive, so I use `MENDER_STORAGE_DEVICE = "/dev/sda"`

---

<div class="post-metadata">

**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\
**Post date:** [September 13, 2019, 1:11pm UTC](https://hub.mender.io/t/issue-with-intel-nuc-tutorial/1010/4 "2019-09-13T13:11:46Z")

</div>

It’s possible that the USB drive is not /dev/sda. Do you have another OS disk you can use to check? I _think_ on my NUC, the USB drive shows up as /dev/hda but I’m away from the office and cannot confirm.

You may also see the device nodes during the kernel boot logs as it scans the devices. It’s difficult without a serial port but taking a video of the boot sequence may be instructive.

---

<div class="post-metadata">

**Author:** ![SteeveGLDev](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/steevegldev/32/349_2.png) [@SteeveGLDev](https://hub.mender.io/u/SteeveGLDev)\
**Post date:** [September 16, 2019, 3:51pm UTC](https://hub.mender.io/t/issue-with-intel-nuc-tutorial/1010/5 "2019-09-16T15:51:57Z")

</div>

Yes, I used a live linux to check the disk and the usb is sda.

The last think I tested is disabling the onboard mmc. Now I got a more readable message.

 ![IMG_20190916_114719](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/1X/0b79e99fa05aa902b693612f7e260e37de2fe93f.jpeg)

The usb drive is not available in the boot process?

---

<div class="post-metadata">

**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\
**Post date:** [September 17, 2019, 8:35am UTC](https://hub.mender.io/t/issue-with-intel-nuc-tutorial/1010/6 "2019-09-17T08:35:10Z")

</div>

It does not seem that you any devices visible above.

Can you check if you have `rootwait` defined in Linux kernel arguments? You can check this by inspecting the `grub.cfg` file on the first partition of your USB flash drive.

---

<div class="post-metadata">

**Author:** ![SteeveGLDev](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/steevegldev/32/349_2.png) [@SteeveGLDev](https://hub.mender.io/u/SteeveGLDev)\
**Post date:** [September 17, 2019, 3:10pm UTC](https://hub.mender.io/t/issue-with-intel-nuc-tutorial/1010/7 "2019-09-17T15:10:30Z")

</div>

Nope, no `rootwait` in `grub.cfg`: `set console_bootargs="console=tty0,115200n8 console=ttyS0,115200n8 console=ttyO0,115200n8 console=ttyAMA0,115200n8"`

I thought it was fixed with [https://github.com/mendersoftware/grub-mender-grubenv/pull/7](https://github.com/mendersoftware/grub-mender-grubenv/pull/7)

Anyway, has workaround I booted with a live linux and dd the IMG to the MMC

---

<div class="post-metadata">

**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\
**Post date:** [September 17, 2019, 7:29pm UTC](https://hub.mender.io/t/issue-with-intel-nuc-tutorial/1010/8 "2019-09-17T19:29:21Z")

</div>

That fix may be in the mender-grub-grubenv source but the Yocto branch you are on may not yet have it. If you can test it and submit a PR against meta-mender that would be most appreciated.
