<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Dec 19, 2018 at 9:49 AM Stephen Worthington <<a href="mailto:stephen_agent@jsw.gen.nz">stephen_agent@jsw.gen.nz</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, 19 Dec 2018 06:11:56 -0500, you wrote:<br>
<br>
>On Wed, Dec 19, 2018, 3:44 AM Stephen Worthington <<a href="mailto:stephen_agent@jsw.gen.nz" target="_blank">stephen_agent@jsw.gen.nz</a><br>
>wrote:<br>
><br>
>> On Tue, 18 Dec 2018 23:03:14 -0500, you wrote:<br>
>><br>
>> >Greetings Mythizens, I received my replacement drive from Amazon used<br>
>> >"rsync" to copy the files from my revived (previously "about to fail")<br>
>> >drive, swap the two drives and the box doesn't boot. Unswitch and it boots<br>
>> >fine... unmount storage2, and switch drives and the FE finds storage2<br>
>> >recordings (on the "rsync'd" drive) then a reboot fails. "fstab" is lookng<br>
>> >to mount storage1,2&3, storage directories are back to original form, all<br>
>> >default group, granted it doesn't take much, but I'm stumped! What do I<br>
>> >need to do to make this drive acceptable to my box? the first of this type<br>
>> >of drive worked fine, the odds of getting lemons back to back I woud<br>
>> >imagine to be quite high...Please help, TIA Daryl<br>
>><br>
>> Rsync does not copy the labels and UUIDs of partitions. Check your<br>
>> fstab to see what you specify for the boot partition, and make sure<br>
>> the partition on the new drive matches the fstab name or UUID.<br>
>> _______________________________________________<br>
>> mythtv-users mailing list<br>
>> <a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
>> <a href="http://lists.mythtv.org/mailman/listinfo/mythtv-users" rel="noreferrer" target="_blank">http://lists.mythtv.org/mailman/listinfo/mythtv-users</a><br>
>> <a href="http://wiki.mythtv.org/Mailing_List_etiquette" rel="noreferrer" target="_blank">http://wiki.mythtv.org/Mailing_List_etiquette</a><br>
>> MythTV Forums: <a href="https://forum.mythtv.org" rel="noreferrer" target="_blank">https://forum.mythtv.org</a><br>
><br>
><br>
>At one time, long ago, this was a boot drive, it hit me while on the<br>
>pillow, so after booting and switching drives will runing "update-grub" be<br>
>the cure? Or will I have to use the boot-repair live CD?<br>
<br>
Changing drives can upset the BIOS settings and make a different drive<br>
become the boot drive, especially if you replace the boot drive. It<br>
all depends on what is actually your current boot drive. The BIOS<br>
settings determine that. If the new drive is supposed to be the boot<br>
drive, where grub is installed, then running grub-install on that<br>
drive should help. If your SSD is supposed to be where grub is, then<br>
check the BIOS settings to make sure the SSD is set as the boot drive,<br>
and then if necessary run grub-install on the SSD. That may need to<br>
be done from a live CD - it is a bit of a complicated process, but the<br>
net has good instructions.<br>
<br>
The next possible problem is just what partitions you have in<br>
/etc/fstab. If you have a partition in fstab set up in the normal<br>
way, systemd will require that the partition be mounted before it will<br>
start up most other things. If the new drive does not have the same<br>
partition names or UUIDs for the partitions (as set up in fstab), then<br>
systemd will keep on trying to mount the old partitions, and as they<br>
are no longer there, it will do that for a long time before it times<br>
out. So it can take several minutes before it will give up and try to<br>
complete the booting process. In 16.04, if that happens, the boot<br>
never completes properly as other things have timed out in the mean<br>
time, and it will never give you a GUI screen. You then have to use<br>
Ctrl-Alt-F1 to get a text console and fix fstab by commenting out the<br>
partitions that are no longer available and using the reboot command.<br>
In 18.04, although I have not tested it much, things seem to be much<br>
better and it may complete the booting process fairly normally, but it<br>
will still be delayed a long time by the missing partitions.<br>
_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
<a href="http://lists.mythtv.org/mailman/listinfo/mythtv-users" rel="noreferrer" target="_blank">http://lists.mythtv.org/mailman/listinfo/mythtv-users</a><br>
<a href="http://wiki.mythtv.org/Mailing_List_etiquette" rel="noreferrer" target="_blank">http://wiki.mythtv.org/Mailing_List_etiquette</a><br>
MythTV Forums: <a href="https://forum.mythtv.org" rel="noreferrer" target="_blank">https://forum.mythtv.org</a></blockquote><div><br></div><div>fstab looks in order, but, thanks Stephan, BIOS boot order was not correct, now pointing to the Kingston SSD I'm hoping for better results</div><div> </div></div></div>