Can't boot notebook from SSD

[Ken D'Ambrosio]

On 2017-05-03 08:49, Liam Proven wrote:

> This means that if they are wiped, you can brick your system.
> http://www.phoronix.com/scan.php?page=news_item&px=UEFI-rm-root-directory

That link provided interesting reading, but I'm not buying the word 
"brick" in the sense that I normally reserve it for (e.g., ARM-based 
devices that you now need to hook up to debugging hardware to revive) -- 
if so, it would mean that your hard disk dying would render your entire 
system dead.  Pretty sure the author goofed on that particular choice of 
word.  Though I suppose that if you keep secure EFI enabled, a dead disk 
might make that seem like the case, in which case you'd have to play 
games in the firmware of your system.

> Ergo, there must be enough space to _write_ to those files, or it won't 
> boot.

I didn't get that from the article, either.  Writing to NVM -- or BIOS 
-- is something you want to do some times, sure, but I'm hard-pressed to 
think of a situation where that would actually prevent a boot, instead 
of simply throwing an error or two.  Thus my original suggestion that 
the OP disable splash and quiet in the kernel boot line in order to 
root-cause the issue at-hand.

-Ken