https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082007-08-29T05:18:02ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #795: not always reproducable installer problemhttps://bugs.dragonflybsd.org/issues/795?journal_id=36022007-08-29T05:18:02Zdillon
<ul></ul><p>:Justin suggested I send the details to this list. dmesg from the two <br />:affected systems follows. 1.8.x installs fine on both and ad0 is probed<br />:correctly. 1.10.x installed on neither system last week but installs fine on<br />:same hardware today, though ad0 probes with an error.<br />:<br />:Dru<br />:<br />:---<br />:<br />:Now I'm perplexed as I can't reproduce the error on the same hardware and am <br />:trying to figure out what factor(s) caused the original failure.<br />:<br />:Last week when I tested, both 1.10.0 and 1.10.1 started acting weird as soon as <br />:I typed "installer" and went to the "GUI". It would hang for a minute just <br />:before asking for the language. In the Select Disk screen, ad0 showed as <br />:FAILURE - SET_MULTI status=51<READY,DSC,ERROR> error=4<ABORTED>. (This BTW <br />:still happens while 1.8.x on the same system correctly probes ad0.)<br />:<br />:However, last week fdisk would fail, and always at 81% I can't remember the <br />:exact error message, something about a wrong boundary and the error is <br />:different than the one you get if you accidently try to fdisk acd0. This was<br />:the error I tried reproducing last night and this morning--but now fdisk works. <br />:Also, last week, I could not get past this error, even if I tried booting with <br />:ACPI disabled or in safe mode--fdisk always failed at 81%. Also, if I retried <br />:fdisk, I'd cause a kernel panic at around the 4th retry.<br />:<br />:...<br />:<br />:I thought perhaps it was because Ubuntu and grub were installed on the system <br />:previously and this confused the installer. So I reinstalled Ubuntu, then <br />:dragonfly, but still no error.<br />:<br />:Now I am trying to think what else I've done differently...</p>
<pre><code>There are several possibilities. It could be a driver issue (1.8 used<br /> the original ATA driver while 1.10.x uses NATA), but driver issues<br /> usually have more consistent failures.</code></pre>
<pre><code>It could also be cabling or heat related. I noticed that the driver<br /> connected to the drive at UDMA100. Is this an old machine? Is it a<br /> laptop or desk top?</code></pre>
<pre><code>Getting stuck for long periods of time between menus sounds like it<br /> is having problems accessing the CD, but that would make it more likely<br /> to be a driver issue since the two are on separate cables.</code></pre>
<pre><code>You might be getting some meaningful messages on the error console,<br /> which you can flip to from the installer using ALT-F1, ALT-F2, ALT-F3,<br /> etc. Errors are logged to one of those (I forget which).</code></pre>
<pre><code>-Matt</code></pre> DragonFlyBSD - Bug #795: not always reproducable installer problemhttps://bugs.dragonflybsd.org/issues/795?journal_id=36032007-08-29T05:47:01Zdlavigne6
<ul></ul><p>On Tue, 28 Aug 2007, Matthew Dillon wrote:</p>
<p>Could possibly be heat... System 1 is an older desktop. System2 is a <br />newer laptop which I usually leave plugged in and on 24/7.</p>
<p>System 1 was cool when I tested last night/this morning; I didn't retry <br />on system2 as I had just reinstalled it. I'll try leaving system1 on for a <br />while then check if the error is reproducable.</p>
<p>Thanks for the prompt reply,</p>
<p>Dru</p>