=== SteveH0_ is now known as SteveH0 | ||
SteveH0 | I have a dying hard drive (hardware errors) and after I reinitialize a replacement, I'd like to know what the easiest method would be to move the old configuration and data (shows) onto the new drive. Any assistance would be most appreciated! | 01:54 |
---|---|---|
Hydr0p0nX | dd | 02:18 |
SteveH0_ | I have a dying hard drive (hardware errors) and after I reinitialize a replacement, I'd like to know what the easiest method would be to move the old configuration and data (shows) onto the new drive. Any assistance would be most appreciated! | 02:19 |
Hydr0p0nX | dd | 02:19 |
=== SteveH0_ is now known as SteveH0 | ||
SteveH0 | Thanks for the comment about dd, but as I said, the drive is dying. I'm really looking for which directories or files I need to try to move. | 02:21 |
Hydr0p0nX | just worried about recordings ? | 02:22 |
SteveH0 | some about the shows, but also my canned searches. | 02:23 |
Hydr0p0nX | then, database backup + your media directory | 02:26 |
Hydr0p0nX | i use dd or ddrescue in those cases though | 02:29 |
Hydr0p0nX | and I just dealt with it a few months back | 02:29 |
SteveH0 | Not sure about db backup? Is this a MySQL thing? (Sorry, my SIL called to wish me happy veterans day) | 02:32 |
Hydr0p0nX | yep | 02:42 |
Hydr0p0nX | http://www.mythtv.org/wiki/Backup_your_database | 02:44 |
SteveH0 | OK, I see the recordings at /var/lib/mythtv. I'll look at your link. | 02:44 |
Hydr0p0nX | once you have those backed up | 02:46 |
Hydr0p0nX | try a dd or ddrescue | 02:46 |
Hydr0p0nX | you might be able to get everything mirrored | 02:46 |
Hydr0p0nX | dd is just, dd if=/dev/src of=/dev/dest | 02:48 |
Hydr0p0nX | ddrescue is covered pretty well here: http://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html | 02:48 |
SteveH0 | Hydr0p0nX: Thanks! I have made several back ups, and have stored at least one off the dying drive. | 03:58 |
qwebirc17277 | I've installed mythtv on top of ubuntu 12.04.1, and for some reason, when mythfronted starts up, my keyboard doesn't work until I click the mouse - any ideas? | 14:08 |
skd5aner | superm1: ping, you around? | 15:14 |
superm1 | Yep | 15:14 |
skd5aner | hey, had a quick question about the current upstart script you guys use... | 15:15 |
skd5aner | I can't seem to get it to work for me - I run vanilla ubuntu server, and had used an older version of the script you posted to the wiki for probably 3+ years... | 15:16 |
skd5aner | however, I tried to pull in the changes from the latest you have in the packaging folder on git, but now whenever I try to do a "service mythtv-backend start", it basically just hangs and never launches mythbackend - any ideas? I'm not exactly sure how to even troubleshoot upstart | 15:17 |
skd5aner | superm1: ^ :) | 15:18 |
superm1 | skd5aner: which version of ubuntu? | 15:19 |
skd5aner | 12.10 | 15:19 |
superm1 | ok so not the super newest version of upstart at least | 15:19 |
superm1 | and i'm assuming you're using master version of packaging and master mythtv too? | 15:20 |
skd5aner | nope, but I am considering upgrading to 13.10 probably sometime soon | 15:20 |
skd5aner | 0.27-fixes | 15:20 |
skd5aner | for both | 15:20 |
superm1 | Oh ok | 15:20 |
skd5aner | sorry - I thought I mentioned... | 15:21 |
skd5aner | I compile mythtv from source :) | 15:21 |
skd5aner | I don't actually use mythbuntu, but I do like to mirror some of things you guys do (like upstart) :) | 15:21 |
superm1 | right i knew you compiled from source, just wasn't sure what you were compiling these days | 15:21 |
skd5aner | gotcha :) | 15:21 |
superm1 | so have you already tried to make sure those pre-start parts work? | 15:21 |
skd5aner | I'm wondering if that's actually the problem... | 15:22 |
skd5aner | just a quick sec | 15:22 |
superm1 | i mean it should only hang for 15 seconds or so if the pre-start part fails | 15:22 |
superm1 | but mythbackend also wouldn't start | 15:22 |
skd5aner | here's what the script looks like | 15:24 |
skd5aner | yea, I've waited for several mins just to make sure I wans't impatient, heh | 15:24 |
skd5aner | http://pastebin.com/Wk3gC7g0 | 15:25 |
skd5aner | actually | 15:25 |
skd5aner | I commented out that pre-start section just to test | 15:26 |
skd5aner | and it still doesnt' work | 15:26 |
superm1 | oh ok | 15:26 |
superm1 | and already tried to comment out the ulimit change? | 15:26 |
skd5aner | well, hang on... :P | 15:26 |
skd5aner | I hadn't tried to work on this in about a month | 15:26 |
skd5aner | so I forgot where i left off... | 15:26 |
skd5aner | lol | 15:26 |
superm1 | and the other change you have is syslog logging, idk does that syntax still work in 0.27? i know we had to make changes for syslog7 | 15:27 |
superm1 | if neither of those yield anything, next thing you should go investigate is /var/log/upstart and see if there is a myth related log sitting in there | 15:28 |
skd5aner | ok, ok... | 15:29 |
skd5aner | I remember sorta where I left off - sorry for mumbling through my self-made confusion here... | 15:29 |
skd5aner | the version I sent you is from my slave backend... I commented out the pre-startup stuff because I don't have mysql on that machine... | 15:29 |
skd5aner | my mbe is in the process of rebooting and has still not come backonline, I think it's checking disks... | 15:30 |
skd5aner | superm1: yea, that log was very vauge... | 15:30 |
skd5aner | also, I don't use syslog, that was one of the differences I made in the script, I output to a file | 15:30 |
superm1 | ah | 15:30 |
skd5aner | I made only a very few slight tweaks... 1) path to mythbackend was slightly different, and 2) syslog to logfile/path | 15:31 |
superm1 | well if /var/log/upstart isn't too useful when the MBE comes up, you can --verbose to your kernel command line to get upstart into a more verbose mode (http://upstart.ubuntu.com/wiki/Debugging) | 15:31 |
skd5aner | beyond that, it's almost identical | 15:31 |
skd5aner | k, let me see where I get... it had stumped me for quite a while and I just gave up and started using the CLI to launch mythbackend in the interim :/ | 15:32 |
skd5aner | thanks for the leads, I'll keep you posted | 15:32 |
superm1 | sure | 15:32 |
skd5aner | also, thanks for all the hard work on mythbuntu! I'm possibly going to be implementing a new frontend soon and I think I'll just go the straight mythbuntu route this time :) | 15:33 |
superm1 | awesome :) | 15:34 |
superm1 | if your timing lines up with our 14.04 ISOs starting to stabilize it would be great to have a live tester on them | 15:34 |
superm1 | right now they're a bit of a mess since the installer switched to python3 and not everything is ported yet for the mythbuntu apps | 15:34 |
skd5aner | superm1: cool - I'll let you know, it may be at least until Christmas before I'd even consider spending money on hardware | 15:40 |
skd5aner | funds are tied up for other reasons this time of year :) | 15:40 |
skd5aner | superm1: ok, ran to the basement and my mbe had a kernel panic during reboot (odd)... just came back up... | 15:42 |
skd5aner | superm1: so, during boot, the upstart script appears to work. Mythbackend is running.... | 15:42 |
superm1 | cool on the new HW, that's closer to when i'll have more contiguous free time to be fixing 14.04 stuff anyhow | 15:42 |
skd5aner | however, when I do a service mythtv-backend stop, nothing happens | 15:43 |
superm1 | can you pastebin the script as it is? are you maybe missing some fork or --daemon or exec lines? | 15:43 |
superm1 | we did make some changes there specifically in the past months | 15:43 |
skd5aner | http://pastebin.com/HCpZs40C | 15:44 |
superm1 | yep you're missing the exec command at the start of your mythbackend call | 15:45 |
skd5aner | omg | 15:45 |
skd5aner | UGH! | 15:45 |
superm1 | haha, it's always the small things! | 15:45 |
skd5aner | superm1: good eye, but I definitely feel like I have egg on my face now | 15:47 |
skd5aner | I swear it had to have been something like that at first and thought I went through it with a fine tooth comb line by line | 15:47 |
skd5aner | made the change, trying now | 15:48 |
skd5aner | hmmmm | 15:49 |
skd5aner | not sure that "fixed it" | 15:49 |
superm1 | you'll need to reboot most likely | 15:49 |
superm1 | we made that change because upstart was getting in this weird state where it couldn't properly track processes | 15:49 |
skd5aner | ah | 15:49 |
skd5aner | k, rebooting | 15:50 |
skd5aner | superm1: works after a reboot! | 16:15 |
skd5aner | thanks superm1, really... that was starting to get under my sking, thanks for the second set of eyes :S | 16:15 |
superm1 | woot. sure glad to help | 16:15 |
skd5aner | s/sking/skin | 16:15 |
skd5aner | superm1: out of curiosity... if mythbackend were to segfault, would the upstart script attempt to relaunch? | 16:19 |
superm1 | Yep | 16:19 |
skd5aner | ok, that's great news! | 16:20 |
superm1 | that's what that respawn thing should do for you | 16:20 |
skd5aner | Right now, mythbackend segfaults for me every morning... I've got a couple bug reports in | 16:20 |
superm1 | if it respawns more than twice within 3600 seconds though it won't do it again | 16:20 |
skd5aner | gotcha | 16:21 |
skd5aner | that makes sense given the context of the script | 16:21 |
skd5aner | I thought that's what those lines did, but I know very little about upstart :) | 16:21 |
superm1 | yeah it's one of the big benefits imo on how it does process tracking and can do that | 16:23 |
superm1 | we do the same thing with mythfrontend with a wrapper around it | 16:23 |
superm1 | for 14.04 we might actually make mythfrontend an upstart tracked job though too since it can track user jobs in 14.04 | 16:23 |
skd5aner | superm1: yea, I "borrowed" your idea for mythfrotnend too... I used to use gdm with an .xsession, and when mythfrontend died, it'd restart the gdm session. However, when I switched to lightdm, it didn't handle the auto-login as gracefully | 17:13 |
skd5aner | superm1: so, I saw how you guys did it with the loop and now it's rediculously quick to recover | 17:14 |
skd5aner | that's been a very welcome addition | 17:14 |
Jay2k1 | how cool is that | 17:15 |
Jay2k1 | i mapped a shell script to the power button on my remote which does a killall mythfrontend.real and then starts it again because it freezes every now and then | 17:16 |
=== dahlSTROM|sleep is now known as dahlSTROM | ||
qwebirc66608 | Hello room | 19:12 |
=== dahlSTROM is now known as dahlSTROM|sleep | ||
=== dahlSTROM|sleep is now known as dahlSTROM | ||
TandyUK | hey guys having issues with one of my frontends | 20:53 |
TandyUK | several of my channels show up as unknown(unknown) on the frontend, with no channel data. If i watch it however, i am viewing the correct channel | 20:54 |
TandyUK | if i access mythweb however, all listings are present and correct | 20:54 |
TandyUK | i have 2 frontends and one backend, both frontends have the problem | 20:55 |
TandyUK | any idea what is wrong? | 20:56 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!