2006-12-06: Oliver Maunder dixit: > Uh-oh - riocp killed my karma!!! Oh! bad guy this riocp :( > Well - it might have done, or it might be a coincidence. > > I ran 'riocp -b' from a terminal to try and rebuild my > database. It took about a minute, and completed without any > errors.
This is as expected. > I then tried to copy an mp3 using riocp, and it segfaulted. This is bad. This may have resulted in a corrupted or empty smalldb in your RK. This happened to me many times, long time ago during the early development and test of the smalldb support code. > I then tried restarting the karma and it entered a cycle where > it boots, gets to the point where the hard-drive spins up and > then restarts itself, gets to the point where the hard-drive > spins up and then restarts itself... This carried on until I > found a pin and hit the reset button. Did you try to power-on it again? As far as I remember, a bad or empty smalldb does NOT kill the RK; instead, when it is switched on and it finds no or bad smalldb, it automatically starts Rescan Music, after which the RK is again fully functional. The only downside is that all the info that was only in the the smalldb but not in the *1 files (notably play counts) is lost. Another (remote) possibility is an OMFS trouble. In this case, you won't even get the automatic Rescan Music. It also happened to me some times, and I did manage to solve all of them (with much help from Bob, of course), without even having to reflash or reformat, but I don't really remember how... > Now I'm not saying riocp caused this - the karma hard-disks do > have a, uh, temperamental reputation. But the timing does seem > suspicious. Yes, it is very suspicious. > Could this sort of behaviour be caused by a corrupted DB? Ditto. > Does anyone have any ideas on how to fix this? I'll try > reflashing the firmware when I get home, and reformatting as a > last resort (is there any way to do this in Linux?). Unfortunately not. > And then if that doesn't work I'll hit it very hard. Don't do it! Your trouble is 99.9% probably software/firmware caused. As a very last resort I think you should take the disk out of the RK and fix the bad isuues by connecting it directly to the IDE of your computer. > If I do get it up and running, I'll try another 'riocp -b' and > see if it breaks again. > > Fingers crossed Please let us know how it goes... Best, EV. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-karma-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-karma-devel
