<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><br><br>--- On <b>Thu, 3/29/12, Rick Lane <i><rick@timeforabrew.com></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>From: Rick Lane <rick@timeforabrew.com><br>Subject: Re: [mythtv-users] OT: Wierd boot issue<br>To: "Discussion about MythTV" <mythtv-users@mythtv.org><br>Date: Thursday, March 29, 2012, 3:01 PM<br><br><div id="yiv2028429770"><p><br>
On Mar 29, 2012 7:51 PM, "Neil Cooper" <<a rel="nofollow" ymailto="mailto:neilcoo@yahoo.co.uk" target="_blank" href="/mc/compose?to=neilcoo@yahoo.co.uk">neilcoo@yahoo.co.uk</a>> wrote:<br>
><br>
> This is somewhat off-topic for a MythTV forum but I can't find an answer anywhere else. Mostly because grub doesn't seem to have a good support website anywhere.<br>
><br>
> My MythTV box is a combined 0.24 backend/frontend running over Ubuntu 10.04. It has a single WD 2TB hard drive. It uses ACPI bios wakeup to wake itself up in time for recordings.<br>
><br>
> Every now and again when it wakes itself up, instead of booting properly it fails somewhere at the grub stage. The screen is completely black other than a message "File not found".<br>
><br>
> After power cycling (all you can do from that point), the grub boot menu appears and doesn't time out even though its set to.<br>
><br>
> This is bloody inconvenient because my myth box is normally keyboardless so I have to go get a keyboard just to hit "enter" on the grub menu to have it boot.<br>
><br>
> Subsequent (re)boots work fine again without Grub bringing up its menu until sometime later I get the dreaded "file not found" issue abnd go round the loop again.<br>
><br>
> The main fix would be to get to the bottom of why every now and again grub cannot find vmlinuz (which is basically what I'm guessing is causing the 'File Not Found" issue). The drive is alive enough for grub to load so its not a drive powerup timeout issue.<br>
><br>
> If the main problem is not answerable, the workaround would be to get the grub menu to always time out. It seems grub has detected that the previous boot failed so is 'intelligently' (and annoyingly) bringing up the boot menu for the user on the next boot instead of following its default/configured behaviour. Is this intelligence disableable somehow?<br>
><br>
> Thanks guys,<br>
> Neil Cooper.<br>
><br>
> _______________________________________________<br>
> mythtv-users mailing list<br>
> <a rel="nofollow" ymailto="mailto:mythtv-users@mythtv.org" target="_blank" href="/mc/compose?to=mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
> <a rel="nofollow" target="_blank" href="http://www.mythtv.org/mailman/listinfo/mythtv-users">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br></p>
<p>I fell into grubs new trap too.</p>
<p>To disable:</p>
<p>open the grub header file:<br>
sudo nano /etc/grub.d/00_header</p>
<p>Line 242 looks like this:<br>
set timeout=-1</p>
<p>Change to:<br>
set timeout=10</p>
<p> and then save the file and run</p>
<p>sudo update-grub</p>
<p>This will mean if your boot fails, it won't disable default selection completely, it'll just pause for ten seconds and then boot as normal.</p>
<p>Can't really help with your other issue though. Could it be a flaky sata cable? I thought my disk was dying on me for a while when I was getting randomly disappearing disks at boot and it turned out to be the cable. At least its a cheap enough test...</p>
<p>Rick <br>
</p>
</div><br>-----Inline Attachment Follows-----<br><br><div class="plainMail">_______________________________________________<br>mythtv-users mailing list<br><a ymailto="mailto:mythtv-users@mythtv.org" href="/mc/compose?to=mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br><a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-user</a><br><br>Excellent! Thanks Rick!<br></div></blockquote></td></tr></table>