You are not logged in.
Pages: 1
The hinge on my dell xps 13 9350 ripped the palm rest, so I had to take every component out and put it into a new palm rest.
Everything seems to be working up until selecting a grub boot entry. Both Arch Linux and Windows will not boot.
Arch gives the following error message:
Starting version 235
ERROR: device 'UUID=...' not found. Skipping fsck.
mount: /new_root: can't find UUID=...
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned offGiven that this wasn't a problem before reassembling my laptop, its probably a hardware error, but since everything seems to be working including the nvme, I can't figure out what is wrong.
Thanks for your time!
Last edited by arghlinux (2018-08-21 16:40:48)
Offline
Run blkid in the emergency shell (or a chroot) and see what the UUIDs actually are..
Offline
I tried running blkid but it didn't output anything. Not even an error.
Offline
Go to bios and redefine boot options manually - that worked for me in similar case whe I replaced MB in my 9360
Last edited by Asriel (2018-08-21 09:17:26)
Offline
Asriel, any BIOS/firmware is already detecting the dist and starting the boot loader on the disk and even (technically) successfully booting the kernel. That is an init error.
If the BIOS/firmware were not set to boot to the correct disk, the process wouldn't even get nearly that far.
OP, do you have a live usb handy? Boot to that and see if you can mount your partition(s) and chroot.
Last edited by Trilby (2018-08-21 12:59:07)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I've tried mounting the drives with linux mint, fdisk doesn't seem to detect my nvme ssd. only loop and the live usb itself.
Offline
Check your UEFI and look whether the drive is set up as some RAID mode or similar and disable/switch that to AHCI
Offline
That did it. I'm guessing that it wasn't set to RAID before, so how did it change?
Thanks for the help everyone
Offline
Well did you completely use all the same parts or is it technically a new motherboard and you just replaced the drives? Whether that or any other reason, likely your BIOS settings reset (maybe you accidentally (re)moved the CMOS battery and your settings reset to factory defaults)
Offline
Pages: 1