LinuxMCE Forums

General => Installation issues => Topic started by: rocketlynx on July 19, 2009, 06:35:24 pm

Title: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: rocketlynx on July 19, 2009, 06:35:24 pm
I Need Help!

In order for anyone to support me, I will try to give as much detail as I possibly can.

I have an 810 Alpha2-Latest Core that apparently has a Core Boot Drive (sda1) that has become corrupt while working.  The system has been up and working without any problems for about 2 months.  It is running Alpha2.24, up until now, without any glitches.

I went to my windows vista orbiter and up popped "A new Hard Drive has been found, do you want to use it?"   Seeing that it was referring to my Core's primary hard drive (sda1), I knew something was screwed up.  I then went to the core and the onscreen orbiter was displaying the same message and running painfully, painfully slow.  Not knowing the consequences of any relpy, I selected on the orbiter, Admin, restart the core and after the orbiter took it's slow running self it said restarting the Core.  After the Core shut down and restarted there was the A/V Wizard.  Oh Crap, now I knew I was in trouble.

The Core now has NO Orbiter, that can be found, and just a blank screen with an arrow cursor after Kubuntu 810 starts and LinuxMCE begins to Init.  No Media Directors, Windows Orbiters or my WebDT 366 can properly and completely boot from the core.  There are NO Internal Network problems causing this (verified).  DCERouter is running because my primary Diskless Media Director sees the Core and begins to boot all the way to Orbiter time and then ends up with the same blank screen with an arrow cursor.

Before going to the blank screen w/cursor, I managed to catch the media director finishing it's boot from the core, quickly saying, Error - Unable to connect to the MYSQL server.  Evidently the Diskless Image, on the Core, can be found or the MD would not have gotten that far.

The only clue I have as to what possibly might have happened is my family was watching a movies on the MD and told me that a Blue-Screen Message popped up and said, the disk drive was full or getting full.  I wasn't home so I do not have more precise error message info.

I need to try and trap the Core while booting and get to a console or KDE Desktop, to see what's going on with the Core's Boot Drive (sda1).

How do I let Kubuntu boot and stop LinuxMCE from starting on the Core?  Are there any control key combinations I can use?

Any help would be greatly appreciated as I'm trying to avoid a complete re-installation as I have several camera logs on the primary drive, and the loss of about 190 DVD movies on (sdb1), a 1.5T drive, would be catastropic.

Thanks,
Charles
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: niz23 on July 19, 2009, 06:50:58 pm
Hi.

Sounds like you have no space left on dev/sda1.
Can you access the shell or ssh into your box?
If you can, check with df how much space you have left on your partitions.
If filesystem is full check under /var/log/pluto for extraordinary big files.
Files that are several GB in size.

If you cannot get into your box you can use kubuntu cd and boot the live environment and then mount your filesystems from local hdd and delete appropriate files.


/niz23
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: rocketlynx on July 19, 2009, 07:01:12 pm
Hi.

Sounds like you have no space left on dev/sda1.
Can you access the shell or ssh into your box?
If you can, check with df how much space you have left on your partitions.
If filesystem is full check under /var/log/pluto for extraordinary big files.
Files that are several GB in size.

If you cannot get into your box you can use kubuntu cd and boot the live environment and then mount your filesystems from local hdd and delete appropriate files.


/niz23

Thanks niz23 for the quick reply.  That's what I figured, but how can I try to get to a shell on the core without it going to LMCE and a blank screen?  Any key combinations? 

On my external network, I could previously , from a browser, http://192.168.0.191, or, http://192.168.80.1  and get the linuxMCE admin or on my network list, in vista, see the DECrouter and then log in and see LMCE user folders, but all of that is not working anymore.
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: pigdog on July 19, 2009, 07:01:22 pm
Hi,

Here's something about the low disk space message and large log files.

http://forum.linuxmce.org/index.php?topic=8534.0

Might be something in there.

Good Luck.  (Have you thought about a separate drive running the OS and another drive with your media?)

P.S.  Can you do <CTRL/ALT> F1 and open a console?
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: rocketlynx on July 19, 2009, 07:04:26 pm
Hi,

Here's something about the low disk space message and large log files.

http://forum.linuxmce.org/index.php?topic=8534.0

Might be something in there.

Good Luck.  (Have you thought about a separate drive running the OS and another drive with your media?)

I have seperate drives.  The 810 LMCE is on sda1 (no media).  All of the dvd movies and audio files are on (sdb2) a seperate 1.5TB sata drive.  Two surveilance cameras, though, are logging to the primary.
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: pigdog on July 19, 2009, 07:09:16 pm
I added a Postscript to my reply...

Can you do <CTRL/ALT> F1 and open a console?
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: rocketlynx on July 19, 2009, 07:12:29 pm
I added a Postscript to my reply...

Can you do <CTRL/ALT> F1 and open a console?

That's what I was looking for.  Thanks, I'll try that now.
Charles
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: pigdog on July 19, 2009, 07:19:05 pm
If that hadn't worked for you one can always reboot and when the see the GRUB message hit ESCAPE and select kernel recovery mode.

This will provide you some choices...

   - resume   resume normal boot
   - clean      Try to make free space
   - dpkg      Repair broken packages
   - fsck      File system check
   - root      Drop to root shell prompt

If you drop to root you'll get the dcerouter prompt.

Good Luck.
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: rocketlynx on July 19, 2009, 07:23:28 pm
Thanks, I'm In!  <CTRL/ALT> F1 Worked!

Since I'm not a Linux Guru command line wizard, I can look up any commands that I need on listing and searching the drive but is there any way, at this point, to execute the KDE Desktop from the Konsole and get it up and running to look at the drives (sda1) and (sdb1) using Dolphin?  Not only checking the primary drive for logs and camera files, I'm also really concerned about the 1.4TBs of movies that have already been ripped.
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: pigdog on July 19, 2009, 07:39:09 pm
Hi,

You could try 'startx' or 'startx kde' maybe.
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: rocketlynx on July 19, 2009, 07:49:46 pm
Hi,

You could try 'startx' or 'startx kde' maybe.

No Go.  Thanks pigdog, it says there's another lock on it.
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: pigdog on July 19, 2009, 08:02:36 pm
Hi,

Looks like you'll have to cd into directories and look around or you could tree the grub boot 'thang do a file system check, repair broken packages, etc.
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: rocketlynx on July 19, 2009, 08:28:56 pm
Hi,

Looks like you'll have to cd into directories and look around or you could tree the grub boot 'thang do a file system check, repair broken packages, etc.

Did that, repair broken packages and all from grub.

Here's what it seems:  LinuxMCE Orbiters fail and MDs get stuck at **ERROR** Cannot connect to MySql Server (or database - Not an exact quote).  Some corruption lies in a damaged MYSql database, MYSql engine or maybe just a config file somewhere in LinuxMCE that holds the MYSql ID and password to connect to the database.

If I'm really screwed, I can re-install the 810 LinuxMCE Alpha2-Latest on a MUCH Larger hard drive, no problem.  I'm hoping when that is done, I can reconnect the (sdb1) drive, reboot the core, and from admin - media files area, I can use the re-sync, or whatever it's called, and let the system see the video and media on the 1.5TB drive (sdb1) that are not in the LinuxMCE MYSql database, and bring them in.  I then can go and clean up the Video titles, for example, and re-edit the info from Admin, as I have when I ripped them so they display correctly on the MDs.  I dont mind reinstalling LinuxMCE from scratch on a larger drive if that's what I have to do to cut my loss.  But, I'll spend hours, trying to fix (sda1), however, if it means that I have to re-rip about 200 2-hour DVDs to the second drive because a new LinuxMCE installation won't recognize the drive from a previous installation.  
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: pigdog on July 19, 2009, 09:06:21 pm
Hi,

Have you tried ...mysqlcheck --all-databases?

You need to do this from the mysql prompt.

Log in to the Mysql database "sudo mysql -uroot"

Just hit enter when prompted for psswd.
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: stallione on July 19, 2009, 09:18:32 pm
sounds like a disk usage issue.. I ran into something similar couple of days ago
Post the output of the following commands, run as root or sudo
To become a superuser on command line type sudo su -
Code: [Select]
df -h

cd /var/log
du -h
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: rocketlynx on July 19, 2009, 09:26:21 pm
Hi,

Have you tried ...mysqlcheck --all-databases?

You need to do this from the mysql prompt.

Log in to the Mysql database "sudo mysql -uroot"

Just hit enter when prompted for psswd.



sudo mysql -uroot returns this error "ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)

It's like the MySQL server is gone.
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: pigdog on July 19, 2009, 09:49:49 pm
Hi,

I was going to say try from the console dpkg-reconfigure -a but you said you'd already tried the repair package thing from grub.

I'm out of ideas.  The only thing is I can suggest is reloading.

You did say that your Core/MD was on a separate HDD (sda1).   All of the dvd movies and audio files are on (sdb2) a separate 1.5TB sata drive.

Then when MCE comes online it should recognize the other drive and want to add it.

I have two HDD's a 1TB and a 500GB (in a NAS) but the data has been around since 7.04. 

It's just data and not affected by how many times I've changed or reloaded the LMCE software on my Core HDD.

Unless I've misunderstood how you are setup.
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: rocketlynx on July 19, 2009, 10:08:01 pm
Hi,

I was going to say try from the console dpkg-reconfigure -a but you said you'd already tried the repair package thing from grub.
I'm out of ideas.  The only thing is I can suggest is reloading.
You did say that your Core/MD was on a separate HDD (sda1).   All of the dvd movies and audio files are on (sdb2) a separate 1.5TB sata drive.
Then when MCE comes online it should recognize the other drive and want to add it.
I have two HDD's a 1TB and a 500GB (in a NAS) but the data has been around since 7.04.  
It's just data and not affected by how many times I've changed or reloaded the LinuxMCE software on my Core HDD.
Unless I've misunderstood how you are setup.

Simple Setup:

Core/Hybride  (used as Core only in Control Room Closet - not worried about fancy video, just simple monitor setup for admin)
ASUS P4P800 MB (2 GB Memory - 2 SATAs, 1 Used, 1 Open - Eth0 LAN - Sound on MB)
Geforce 6200 AGP Video Card
IDE Boot Drive 810 LinuxMCE-latest (sda1)
Seagate 1.5 TB SATA for media (sdb1)
1 free SATA for future
1 3Com PCI Card for Eth1 (internal)
1 PCI PVR-143, 4 port capture Card for Cameras

All Media on (sdb1) second drive
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: pigdog on July 19, 2009, 10:39:15 pm
OK,

Reload should be fine.  Watch the logs later to see if they are being appended to and not recreated.

I'd better look through mine as well.  I don't want a disk space warning.

Oh, here's something to look at...If you've been watching movies and have had them freeze, stutter etc,  connect to the drive and check the folders for 0 byte cifsXXXX files.

I found some movie folders that had tons of them.  Some with 3 and 4 thousand of these 0 byte files. 

Just interested if you find any.  Might be another issue to report.

Cheers.
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: rocketlynx on July 19, 2009, 11:09:38 pm
Going to get a much larger hard drive to serve as (sda1) and then do a re-install.  Hope it installs as easily as it first did.  Just not looking forward to all the MD recreations, WebDT 366 orbiter, Vista Orbiters, Lignting, surveilance cameras... Oh I'm getting a migrane just thinking about it.

I hope there's a good way to back this crap up, external of the system, often so I won't go through this again.
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: colinjones on July 19, 2009, 11:15:56 pm
have you tried niz's suggestion of a live CD? Just put in the Kubuntu CD and boot from it. It will boot into Kubuntu directly from the CD and not even touch the disk, so you will have full KDE and access to your disks so you can work out what is going on. It certainly sounds like your system partition is just full so the various processes can't start up properly. Identify what is taking the space and delete/move it.

Using a terminal shell to do this is very useful - df will list your partitions and you will be able to see immediately which is full. You can then use df inside that partition to list every folder and its size to see where its coming from (probably your security camera logs)
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: rocketlynx on July 19, 2009, 11:41:48 pm
df shows 100% usage with 0% available in /dev.static/dev.   Now I have to see which subs (folders) are the culprits.  Has anyone had any luck cleaning the junk out and then the system rebooting correctly?  Or, does the system just start munching on itself when the OS disk is full?

Charles
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: rocketlynx on July 20, 2009, 01:01:42 am
Booting with Kubuntu 810 CD and using Dolphin, I have found a file "20_LaunchOrbiter.sh.log" in the "/var/log/Pluto" directory that is of a size "50,335,342,700". 

Am I understanding this correctly?  50 Gig?  Why is it so big and can I safely get rid of it?  Also, it's read-only.  Will I have any trouble deleting it using Dolphin from Live CD?

-Charles
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: colinjones on July 20, 2009, 10:24:22 am
50GB is ridiculous, yes that's your problem! No, it doesn't "munch" itself, just make space and it will be fine (unless you've been screwing with things trying to get it working!)

It is perfectly safe to delete the log files, it will just create new ones. However, you need to read the log first and find out what is bloating it, sounds like you have an underlying issue.

Go to a terminal shell

less /var/log/pluto/20_LaunchOrbiter.sh.log and start paging through. Note I quick way to get to the end is hit SHIFT-F which starts "tailing" the end of the log file, then hit CTRL-C so that you can page up and read backwards through the log file.

When ready to delete it, at the shell type

sudo rm /var/log/pluto/20_LaunchOrbiter.sh.log   and then enter your linuxmce password when it prompts

You will probably find /var/log/pluto/20_LaunchOrbiter.sh.log.1/2/3 etc files as well that you can delete
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: stallione on July 20, 2009, 04:43:14 pm
I have the exact same problem. It has happened twice to me, the first time, mysql database got corrupt. This time, I caught it early and was able to reboot before it took the server down. My LaunchOrbiter.sh was filled with the following error
Code: [Select]
01      07/19/09 14:36:38.202           GenericHIDInterface::DecodeEventInFD: Short read from fd 0 <0xb303fb90>
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: rocketlynx on July 20, 2009, 06:20:57 pm
50GB is ridiculous, yes that's your problem! No, it doesn't "munch" itself, just make space and it will be fine (unless you've been screwing with things trying to get it working!)
It is perfectly safe to delete the log files, it will just create new ones. However, you need to read the log first and find out what is bloating it, sounds like you have an underlying issue.
Go to a terminal shell
less /var/log/pluto/20_LaunchOrbiter.sh.log and start paging through. Note I quick way to get to the end is hit SHIFT-F which starts "tailing" the end of the log file, then hit CTRL-C so that you can page up and read backwards through the log file.
When ready to delete it, at the shell type
sudo rm /var/log/pluto/20_LaunchOrbiter.sh.log   and then enter your linuxmce password when it prompts
You will probably find /var/log/pluto/20_LaunchOrbiter.sh.log.1/2/3 etc files as well that you can delete
Nope.  Deleting it alone didn't fix the system, there are other corrupted items.  After completing my investigation and fix of my Core, I'll get back and post the problem source, symtoms, and avoidance for next time.  I want to do this because I want to be sure and post the correct information, so as not to confuse anyone on the forum.
Thanks,
Charles
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: niz23 on July 20, 2009, 07:53:05 pm
rocketlynx,
Booting with Kubuntu 810 CD and using Dolphin, I have found a file "20_LaunchOrbiter.sh.log" in the "/var/log/Pluto" directory that is of a size "50,335,342,700". 

Am I understanding this correctly?  50 Gig?  Why is it so big and can I safely get rid of it?  Also, it's read-only.  Will I have any trouble deleting it using Dolphin from Live CD?

-Charles

Have had this problem myself. Had a 125GB LaunchOrbiter.log file.
There is a (known) problem that is triggered if you add/remove a hid device when Orbiter is running.
In my file I saw around 40-50 log entries per second all related to HID.

If you add/remove a hid device. Reboot your core and you´ll be fine for now.

/niz23
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: stallione on July 20, 2009, 11:07:29 pm
On IRC, Thom told me that if you unplug a usb device, LMCE doesn't handle it well and will start to fill up the LaunchOrbiter.sh.log with HIDINterface events.

Solution:- Don't unplug any USB discs/devices without removing them from the web admin first. (This also applies to USB KVMs)
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: rocketlynx on July 21, 2009, 08:34:54 pm
50GB is ridiculous, yes that's your problem! No, it doesn't "munch" itself, just make space and it will be fine (unless you've been screwing with things trying to get it working!)
It is perfectly safe to delete the log files, it will just create new ones. However, you need to read the log first and find out what is bloating it, sounds like you have an underlying issue.
Go to a terminal shell
less /var/log/pluto/20_LaunchOrbiter.sh.log and start paging through. Note I quick way to get to the end is hit SHIFT-F which starts "tailing" the end of the log file, then hit CTRL-C so that you can page up and read backwards through the log file.
When ready to delete it, at the shell type
sudo rm /var/log/pluto/20_LaunchOrbiter.sh.log   and then enter your linuxmce password when it prompts
You will probably find /var/log/pluto/20_LaunchOrbiter.sh.log.1/2/3 etc files as well that you can delete
Nope.  Deleting it alone didn't fix the system, there are other corrupted items.  After completing my investigation and fix of my Core, I'll get back and post the problem source, symtoms, and avoidance for next time.  I want to do this because I want to be sure and post the correct information, so as not to confuse anyone on the forum.
Thanks,
Charles



Well, I said that I would get back so here it is.  This thread probably could have been avoided if I knew more about what occurred.  Comments later, but please be kind.

I have had a very good LinuxMCE 810 Alpha2-Latest system running for several months complete with several Windows Orbiters, an ASUS diskless MD with DVD drive for ripping, MCE Remote and a bluetooth dongle.  I also have a CM11 for x10 on the Core's COM1, a Bluecherry PVR-143 for Outdoor Cameras, 1 IP D-Link camera connected to the my home networks LAN of which the Core's External LAN is connected to for Internet access.  The Internal LAN of the Core connects to a AirLink 101 wireless router used as a switch only, (wired and wireless), that connects the MD's ethernet and a newly added WebDT 366 WebOrbiter using the wireless portion of the Core's Internal LAN's switch, all working great.  

The Core's Firewall is presently disabled so that my home network devices such as IP Cameras, Windows LinuxMCE Orbiters can be found by LinuxMCE and so I can HTTP into the WebAdmin of my Core from any Computer on my existing home network.  I am still presently hardware fire-walled with my Linksys Router to my DSL Modem.  

All that being said, I believe that I could have "Drove a Stake" through the heart of my Core unknowingly.  In my shop, which also has Internet access from my Home LAN (of which My system's Core can see), I was helping a friend set up a new LinuxMCE Core.  I, not thinking, connected his new proposed Core's External LAN, to my network for access to updates for Kubuntu 810 and then, of course, to install LinuxMCE-Alpha2-Latest from the web.  All went well until his Core's installation was setting itself up (final parts of install) and seemed to be fighting to get the Core's Internal OnScreen Orbiter #20 created.  It never happened. It seemed to be looping a we gave up because it was 2 am and had enough.  I didn't unplug it or shut it down.  The next day, gone to a friend's for dinner, about 24hrs  later,  I discovered that my Core's OnScreen Orbiter was processing extreamly slow.  Not knowing what the hell was happening, I finally managed to get the Orbiter's screen to get to the Reset Core button, and execute that command.  

When my Core restarted, I was presented with the AV-Wizard on my Core, as if it didn't have the #20 Orbiter anymore.  Also it was running very slow and then couldn't get anywhere very fast at all.  I had to wait until the next  morning to ask my daughter if there were any messages on the MD last night because I knew they were watching a Video on it.  She said that during the movie a box popped up saying something about "running out of disk space or disk full", she wasn't sure.

If I would have been home and I was watching and saw this message this would have made me snap and look into it immediatly, but I was gone and things were taking a turn for the worse as both Cores, (I suspect),  were doing it to each other and probably no one got kissed before.  Now, an already too long story, after the help and suggestions from you guys on the forum, I found the log file, 20_LaunchOrbiter.sh.log at 50 gig and filling up my small OS drive.  I have completed New-Install on a much larger drive.

Now for all of you who have helped me in the past, it already hurts if I did this to myself, but the question remains, Did I Cause This?  I mean, did the 2 Cores on the same network stop the New install from completing at the #20 OnScreenOrbiter creation and cause my Core to corrupt it's #20 OnScreenOrbiter consequently filling up it's log?  I have been aware that you don't need or use 2 Cores, I would have disconnected my system from the network to set up my friends new Core if I would have just realized what I was setting myself up for.

Allright, let me have it...

Thanks,
Charles
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: niz23 on July 21, 2009, 08:50:50 pm
There is a problem that trigger massive growth of launchorbiter log.

Problem:
If you add/remove a usb device it´ll trigger massive logging in launchorbiter log file (40-50 entries per second).
That´ll quickly fill up any hdd.

Workaround:
After ad/remove of usb device do a reboot of your machine.

I cannot explain why AVWizard start when hdd is full. It did that for me too when I had the same issue.
For me a simple delete of the log file and a reboot solved it all. Had to rerun AVWizard though.

If your mysql db still do not start try to run mysql repair tools.
In the future you´ll want to have a backup of your db.
You can do that from within lmce-admin.

/niz23



Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: rocketlynx on July 22, 2009, 09:19:02 pm
There is a problem that trigger massive growth of launchorbiter log.

Problem:
If you add/remove a usb device it´ll trigger massive logging in launchorbiter log file (40-50 entries per second).
That´ll quickly fill up any hdd.

Workaround:
After ad/remove of usb device do a reboot of your machine.

I cannot explain why AVWizard start when hdd is full. It did that for me too when I had the same issue.
For me a simple delete of the log file and a reboot solved it all. Had to rerun AVWizard though.

If your mysql db still do not start try to run mysql repair tools.
In the future you´ll want to have a backup of your db.
You can do that from within lmce-admin.

/niz23




No USBs unplugged.  Just as I described.  If a developer would like to comment, please feel free.  I would really like to know if what I described was possibly what could have happened.  

I'm fully reinstalled on a larger OS drive and the system with 6 users, about 15 lighting devices, 2 MDs and 3 Orbiters in addition to the OnScreenOrbiters on the MDs and 2 cameras, takes up only about 16Gigs so far on the OS (sda1) drive.   I have an additional 1.5TB data drive with 185 DVD images on it, no media is on the OS drive.  I know (sda1) will grow in time with logs and cameras recording, but for now after 24 hrs since reinstallation, all seems well and no runaway logs.

Charles
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: niz23 on July 22, 2009, 10:22:43 pm
rocketlynx,

As far as I know the only way the launchorbiter logfile grow to the size you said is because of the hid problems I described earlier.
I understand that you want a developer to comment but still, but without a log(evidence) file it´s will only be a wild guess.

During our 0810 alpha releases I have installed it around 25-30 times and the only times I have seen such a big logfile (or fast growing) is when I add/remove my mce remote usb receiver or usb keyboard/mouse to the system when it is running.
After a reboot everything is fine again (and log file at grow normal).

/niz23
Title: Re: Working 810 Alpha2-Latest - Core Now Corrupt
Post by: rocketlynx on July 22, 2009, 10:40:11 pm
rocketlynx,

As far as I know the only way the launchorbiter logfile grow to the size you said is because of the hid problems I described earlier.
I understand that you want a developer to comment but still, but without a log(evidence) file it´s will only be a wild guess.

During our 0810 alpha releases I have installed it around 25-30 times and the only times I have seen such a big logfile (or fast growing) is when I add/remove my mce remote usb receiver or usb keyboard/mouse to the system when it is running.
After a reboot everything is fine again (and log file at grow normal).

/niz23
Thanks!  If I could have had the presence of mind and a means of saving a 50GB Log file of my core's ID20 LaunchOrbiter, I would have.  I just had to boot from the Kubuntu live CD to manipulate it and didn't have a location to mount and move it to so I just deleted it without looking inside of it.  I attempted to with Kate but it was so large and taking so long to load I don't if I would have ever got it opened to see the last entrys before it all died. 

Thanks again for everyone's support and hand-holding when I have a disaster which is also getting me up to speed in the Linux world.  Go LinuxMCE!
Rocketlynx (Charles)