1 |
I had the same issue. I fixed it by disabling GRUB's automatic UUID |
2 |
kernel parameter and using my own. |
3 |
|
4 |
/etc/default/grub: |
5 |
|
6 |
GRUB_DISABLE_LINUX_UUID=true |
7 |
GRUB_CMDLINE_LINUX="root=/dev/sda5 rootfstype=ext4" |
8 |
|
9 |
Regenerate the grub config after editing it (grub-mkconfig). |
10 |
|
11 |
|
12 |
On 01/25/2017 04:38 PM, Alan Grimes wrote: |
13 |
> After 7 long years, the peace of mind feature on my Velociraptor HD had |
14 |
> finally given up the ghost. |
15 |
> |
16 |
> So I get a new SSD, that's slightly smaller but still a large multiple |
17 |
> of what I actually need the drive for. =P |
18 |
> |
19 |
> To be fully trendy (and finally wanting to put the 1980's to bed) I try |
20 |
> to set up UEFI on gpt partitions, so the new boot partition, which is |
21 |
> also excessively large, now has a EFI directory. |
22 |
> |
23 |
> ############################ |
24 |
> |
25 |
> localhost new_uefi # tree -L 2 |
26 |
> . |
27 |
> ├── config-4.6.7 |
28 |
> ├── EFI |
29 |
> │ ├── BOOT |
30 |
> │ └── gentoo |
31 |
> ├── grub |
32 |
> │ ├── default |
33 |
> │ ├── device.map |
34 |
> │ ├── e2fs_stage1_5 |
35 |
> │ ├── fat_stage1_5 |
36 |
> │ ├── ffs_stage1_5 |
37 |
> │ ├── fonts |
38 |
> │ ├── grub.cfg |
39 |
> │ ├── grubenv |
40 |
> │ ├── i386-pc |
41 |
> │ ├── iso9660_stage1_5 |
42 |
> │ ├── jfs_stage1_5 |
43 |
> │ ├── locale |
44 |
> │ ├── minix_stage1_5 |
45 |
> │ ├── reiserfs_stage1_5 |
46 |
> │ ├── splash.xpm.gz |
47 |
> │ ├── stage1 |
48 |
> │ ├── stage2 |
49 |
> │ ├── |
50 |
> stage2_eltorito |
51 |
> |
52 |
> │ ├── |
53 |
> themes |
54 |
> |
55 |
> │ ├── |
56 |
> ufs2_stage1_5 |
57 |
> |
58 |
> │ ├── |
59 |
> vstafs_stage1_5 |
60 |
> |
61 |
> │ ├── |
62 |
> x86_64-efi |
63 |
> |
64 |
> │ └── |
65 |
> xfs_stage1_5 |
66 |
> |
67 |
> ├── |
68 |
> memtest86plus |
69 |
> |
70 |
> │ ├── |
71 |
> memtest |
72 |
> |
73 |
> │ └── |
74 |
> memtest.netbsd |
75 |
> |
76 |
> ├── |
77 |
> System.map-4.6.7 |
78 |
> |
79 |
> └── |
80 |
> vmlinuz-4.6.7 |
81 |
> |
82 |
> |
83 |
> |
84 |
> 10 directories, 23 |
85 |
> files |
86 |
> |
87 |
> localhost new_uefi # |
88 |
> ############################ |
89 |
> |
90 |
> Okay, |
91 |
> |
92 |
> I copy GRUB into BOOT and test it, I unplugged the 'raptor to make it a |
93 |
> good test. It got to the point of kernel loading where it stalled |
94 |
> presumably because the kernel couldn't find root. But I had TESTED GRUB |
95 |
> AND IT WORKED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!11 |
96 |
> |
97 |
> <catches breath> |
98 |
> |
99 |
> Okay... |
100 |
> |
101 |
> I then use a parted CD and tried to rsync my data across, got bitten by |
102 |
> the goddamned trailing / missfeature, ended up using mv and fixed the |
103 |
> directory entries instead of putting another 50gb of wear on my new drive. |
104 |
> |
105 |
> **** |
106 |
> Side note: these boot CDs disable my mouse because it's using a USB port |
107 |
> that's mapped to the same IO address space as another USB port and, due |
108 |
> to my CPU/MOBO combination, I need about a dozen kernel parameters to |
109 |
> unhose using IOMMU. |
110 |
> **** |
111 |
> |
112 |
> So I've tested grub, it got to the kernel, |
113 |
> |
114 |
> Now I have a root filesystem so the kernel should work. |
115 |
> |
116 |
> Now to juggle the cables |
117 |
> |
118 |
> Grub now dies before accomplishing anything whatsoever complaining that |
119 |
> it can't find a specific uuid. |
120 |
> |
121 |
> I have one thing to say about UUID's at this point: |
122 |
> |
123 |
> BURN |
124 |
> -- IN -- |
125 |
> HELL. |
126 |
> |
127 |
> Before I had been indifferent because I could ignore them completely |
128 |
> with no ill effects, |
129 |
> |
130 |
> Now it's failing in a way that I don't even know what's going on. jeez! |
131 |
> |
132 |
> So what I did was pray to almighty GooG and was provided with a grub |
133 |
> boot repair disk.. Which wouldn't work because it refused to touch a |
134 |
> UEFI system from a legacy-booted CD... So I reformatted my only CF disk |
135 |
> (which was reserved for BIOS images) and got it to do the work. The |
136 |
> keyboard input barely worked because there was almost no visible |
137 |
> feedback of the cursor position when the gui was operated by keyboard... |
138 |
> Anyway, I set the settings the way I wanted and it stopped dead at "plz |
139 |
> wait a few minutes while botching up your kernels "... I came back the |
140 |
> next morning and it was still frozen so I juggled the cables back and am |
141 |
> therefore able to write this e-mail. =\ |
142 |
> |