<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div>I did have initrd.img.gz, and /boot is on UFS. I never touched initd.img as far as I know, I do have root and swap encrypted, but just however the installer did it. Would the upgrade process have messed with that?<br></div>
<div> </div>
<div>I tried rebuilding initrd.img.gz as per Matthias' suggestion just in case, but no dice. Nothing I'm finding poking around in man pages seems to explain where ms0d0 comes from or why it would cease to exist. Can anyone point me in the right direction?<br></div>
<div> </div>
<div>Thanks,<br></div>
<div>Curtis</div>
<div> </div>
<div> </div>
<div>On Fri, Jul 3, 2015, at 07:51 AM, Tim Darby wrote:<br></div>
<blockquote type="cite"><div dir="ltr"><div style="font-family:'trebuchet ms', sans-serif;font-size:small;">I don't know if this is your situation or not, but I have a customized initrd.img for booting into my encrypted root and the upgrade process deletes this file. So, after every upgrade, I have to be sure to copy my initrd.img back.<br></div>
<div><div> </div>
<div><div><div> </div>
<div>Tim<br></div>
</div>
</div>
<div> </div>
<div><div>On Fri, Jul 3, 2015 at 2:37 AM, Matthias Play <span dir="ltr"><<a href="mailto:matthias_play@gmx.net">matthias_play@gmx.net</a>></span> wrote:<br></div>
<blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex;"><div>Be sure you have initrd.img.gz in /boot/kernel and /boot is on an UFS formatted partition. If not, try regenerating it with "mkinitrd -b bootdir".<br></div>
<div> </div>
<div>
Regards,<br></div>
<div>
Matthias<br></div>
<div><div><div> </div>
<div> </div>
<div>
On 02.07.2015 23:12, Curtis Gagliardi wrote:<br></div>
<blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex;"><div>I just went through this process upgrading from 4.2.0 to 4.2.1 and now<br></div>
<div>
I'm getting errors with mounting the filesystem.<br></div>
<div> </div>
<div>
A potential key piece of info is that I'm dual booting with debian,<br></div>
<div>
which is the first OS on the disk and has an encrypted lvm group.<br></div>
<div> </div>
<div>
I'm seeing dm_target_[error/zero/crypt]: successfully initialized and<br></div>
<div>
then an attempt to mount "ufs:msdos0"<br></div>
<div>
with an error about there being so such disk.<br></div>
<div> </div>
<div>
Full errors here:<br></div>
<div> <a href="http://i.imgur.com/QFxfOHt.jpg">http://i.imgur.com/QFxfOHt.jpg</a><br></div>
<div> </div>
<div>
Anyone know what's going wrong, or how I can start going about debugging<br></div>
<div>
this? My initial guess is that it's trying to mount my debian<br></div>
<div>
partition. I used the ? command to list the disk devices, and tried<br></div>
<div>
each one by running "hammer:<device>", but they all failed.<br></div>
<div> </div>
<div>
Thanks,<br></div>
<div>
Curtis<br></div>
<div> </div>
<div>
On Wed, Jul 1, 2015, at 06:31 PM, Justin Sherrill wrote:<br></div>
<blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex;"><div>Yep, it's a 0.0.1 release, to fix a bug in i915 support. If you<br></div>
<div>
aren't running an Intel chipset, there's no urgent need to update.<br></div>
<div>
You do not have to be at 4.2.0 to update to 4.2.1; for all intents and<br></div>
<div>
purposes, 4.2.1 can be treated the same as 4.2.0.<br></div>
<div> </div>
<div>
I've uploaded the new images and they should be showing up on mirrors<br></div>
<div>
shortly.<br></div>
<div> </div>
<div>
For those already running DragonFly, the same update methods as before<br></div>
<div>
apply:<br></div>
<div> </div>
<blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex;"><div>cd /usr/src<br></div>
<div>
git fetch origin<br></div>
<div>
git branch DragonFly_RELEASE_4_2 origin/DragonFly_RELEASE_4_2<br></div>
<div>
git checkout DragonFly_RELEASE_4_2<br></div>
<div>
git pull<br></div>
</blockquote><div> </div>
<div>
And then rebuild:<br></div>
<div> </div>
<blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex;"><div>make buildworld<br></div>
<div>
make buildkernel<br></div>
<div>
make installkernel<br></div>
<div>
make installworld<br></div>
<div>
make upgrade<br></div>
</blockquote><div> </div>
<div>
Any existing 4.2 packages you have installed are completely compatible.<br></div>
</blockquote></blockquote></div>
</div>
</blockquote></div>
</div>
</div>
</blockquote><div> </div>
</body>
</html>