[mythtv-users] sluggish system, potential HD failure, and how best to get back up and runnin
Hika van den Hoven
hikavdh at gmail.com
Tue Mar 4 18:48:54 UTC 2014
Tuesday, March 4, 2014, 6:32:25 PM, you wrote:
> Hoi Gabe,
> Tuesday, March 4, 2014, 5:47:02 PM, you wrote:
>> Thanks, these are all great tips and I will use them in the future.
>> I think I can get to the data on the OS disc, it is just slow as
>> heck to boot up from that and I believe it starts up in read only mode.
>> I do a DB backup every night. I am pretty sure I have the backup
>> go to my other drive, because that would be the smart thing to do,
>> but I will have to check. Obviously my first issue will be locating
>> that backup and putting it on a safe location.
>> I have wanted to do a backup of the full disc as a cron job for a
>> while and back it up to my windows box. I just did not know what
>> the best way to do that is, so the script will be implemented when I
>> get my system back up and running.
>> The key questions I have are, is a SSD a good option considering
>> the DB gets many writess a day and I thought SSDs fail after a
>> certain amount of writes. Even if that is not an issue, is the cost
>> worth it? I don't neccesarily want to replace this drive with a HDD
>> because I only need about 50-100 gigs for the system drive (maybe
>> more, I am forgetting how large the db can get).
>> Once I replace the drive, what is the easiest way to mirror the old
>> drive onto the new one and any gotchas (for example, I think I can't
>> just my old fstab file because it has entries specific to the actual
>> drives and not just their labels). I realize there will be some
>> work migrating, but hoping not a ton.
>> Thanks again!
> I don't know about the average livecycle of HDD drives. But if you
> boot your system from cd or usbstick you can use cp -rpd to copy the
> partition to a new one r for subdirectories p for preserve ownwership
> etc. and d for not following simlinks. You can add -v for verbose.
> After that you have to chroot in to your new disk: chroot /mnt/newdisk
> /bin/bash and configure your boorloader.
> Tot mails,
> Hika mailto:hikavdh at gmail.com
> "Zonder hoop kun je niet leven
> Zonder leven is er geen hoop
> Het eeuwige dilemma
> Zeker als je hoop moet vernietigen om te kunnen overleven!"
> De lerende Mens
Oh, I forgot. before you chroot into your new disk you have to mount
your sys, proc and dev partition ito it
mount -t proc none /mnt/newdisk/proc
mount --rbind /sys /mnt/newdisk/sys
mount --rbind /dev /mnt/newdisk/dev
also if your boot partition is separate you have to copy and mount it.
Hika mailto:hikavdh at gmail.com
"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"
De lerende Mens
More information about the mythtv-users