[mythtv-users] Errors from upgrade

Roger Siddons dizygotheca at ntlworld.com
Fri Aug 22 21:15:26 UTC 2014


On Fri, 22 Aug 2014 17:18:12 +0100, Daryl McDonald <darylangela at gmail.com>  
wrote:

>
>> Primarily I use Gparted for cloning, sometimes when I can't unmount a  
>> partition I use "dd".Below is output from the terrabyte:
>>
terrabyte fstab:

>> UUID=10b4bdaf-d0f0-4f4d-b003-8049f075c12a /               ext4     
>> errors=remount-ro 0       1
>> UUID=3769e2e8-adde-456c-86e4-0402be737ef6  /media/storage   ext4    
>> defaults  0  1

250 fstab:

> UUID=10b4bdaf-d0f0-4f4d-b003-8049f075c12a /               ext4     
> errors=remount-ro 0       1
> UUID=3769e2e8-adde-456c-86e4-0402be737ef6  /media/storage   ext4    
> defaults  0  1


250:
> /dev/sda1: UUID="10b4bdaf-d0f0-4f4d-b003-8049f075c12a" TYPE="ext4" 
> /dev/sda6: UUID="13d595a4-710e-4e30-bf1e-92a8e462214e" TYPE="ext4"

terrabyte:
> /dev/sdb1: UUID="10b4bdaf-d0f0-4f4d-b003-8049f075c12a" TYPE="ext4" 
> /dev/sdb3: UUID="3769e2e8-adde-456c-86e4-0402be737ef6" TYPE="ext4"
>
You can see that sda1 & sdb1 both have the same UUID (because you cloned  
one from the other).

The /etc/fstab tells the boot process which partitions to use for your  
'system', 'storage' etc on startup, so if you boot with both drives  
connected then it will get confused over which one to use. In practice it  
will just use the first one it finds, but this may be different on every  
reboot (very confusing!).

Now I haven't been following closely and it's difficult to follow the  
archives, but have you ever tried to upgrade without the terrabyte  
attached ?

It sounds like you've been disconnecting drives during boot to either get  
around the duplicate UUIDs, but then connecting both because the 250 needs  
your storage on the terrabyte (sdb3). Note that sda6 doesn't seem to be  
used by anything currently.

As the discussion seems to have moved on to grub/initfs, I'm wondering if  
you're trying to upgrade the 250 system whilst the terrabyte is connected,  
in which case the duplicate UUIDs may be confusing the process, resulting  
in all those alarming errors, and muddying the waters of this thread!

If so, then I would suggest you try upgrading the 250 again without the  
terrabyte connected. Ubuntu doesn't need it and you should be able to just  
skip mounting it ("S") when it complains about a missing disk.  
Alternatively you could comment it out in the 250's /etc/fstab.

In theory this will just get you back to square 1, ie. upgrading before  
you cloned, but may clear some fog.

Rewinding somewhat, the fontconfig errors you mentioned aren't critical  
and aren't (I believe) related to Ubuntu or Myth. They may arise from  
other applications you've installed (I'm guessing you're not using  
Steam!). You could try uninstalling any dodgy/unnecessary things before  
you upgrade.

To avoid duplicate UUIDs, gparted has a menu option to assign a "New UUID"  
to your cloned partitions. Then you can leave both disks connected at all  
times. However, if you want to boot from the clone, or use it to restore  
your system, then you'll have to edit the /etc/fstab to match.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20140822/7c98a49d/attachment.html>


More information about the mythtv-users mailing list