[mythtv-users] impending failure
Curtis Gedak
gedakc at gmail.com
Mon Oct 29 15:51:36 UTC 2018
If you have done a complete image copy of the old drive to the new
drive, or else copied the partition and restored the ability of GRUB to
boot [1] on the new drive, then the replacement drive should be good to go.
[1]
https://gparted.org/display-doc.php?name=help-manual#gparted-fix-operating-system-boot-problems
One extra thing to check is that your BIOS/EFI is set to use the new
drive as the boot drive. Otherwise it might be looking for the old
drive, or a different fall-back drive. Usually the BIOS/EFI set up is
entered by pressing a key like DELETE or some other key [2].
[2]
https://gparted.org/display-doc.php?name=gparted-live-manual#gparted-live-preparing-bios
'Hope that helps.
Curtis
On 2018-10-29 5:21 a.m., Daryl McDonald wrote:
> the box didn't boot yesterday with the new drive but did with the old
> going to try clonezilla again today, unless there re better ideas out there.
>
> On Sun, Oct 28, 2018, 7:15 AM Daryl McDonald <darylangela at gmail.com> wrote:
>
>>
>>
>> On Sun, Oct 28, 2018, 4:49 AM Simon Hobson <linux at thehobsons.co.uk> wrote:
>>
>>> Stephen Worthington <stephen_agent at jsw.gen.nz> wrote:
>>>
>>>> When you are copying a failing drive, the best tool to use is ddrescue
>>>> (from the gddrescue package - do not use dd_rescue which is a
>>>> different program).
>>>
>>> +1 for that, it's the most brilliant tool.
>>>
>>> The only time it's failed on me was with a Seagate drive - they went
>>> through a phase when the drive would, after encountering a certain error,
>>> then fail to respond properly until power cycled. Thus ddrescue would
>>> progress so far, the drive would encounter an error, then every block after
>>> that would get marked as failed. Lets just say it didn't improve my opinion
>>> of Seagate !
More information about the mythtv-users
mailing list