From owner-freebsd-cloud@freebsd.org Wed Feb 10 01:59:35 2016 Return-Path: Delivered-To: freebsd-cloud@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7D9F9AA3C35 for ; Wed, 10 Feb 2016 01:59:35 +0000 (UTC) (envelope-from rj@obsigna.com) Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1E5431076 for ; Wed, 10 Feb 2016 01:59:34 +0000 (UTC) (envelope-from rj@obsigna.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1455069571; l=1021; s=domk; d=obsigna.com; h=Mime-Version:To:Date:Subject:Content-Transfer-Encoding:Content-Type: From; bh=Wr+0Rbs9K+zbn04+iVH191MQZ1tvYZFJBLUgjDRxOwA=; b=Ckmxyoux2WoPJKrJ/oIDpqjcSPg5sGkBMC69qmnfP9m1FSidvagmU2Z5Ak6brW1DkIv zYc0xFTLCUgn4rKITU+IoRSdLRJGyCQXtnR1DX0t/9YJAPwbD2kisEsSeABts2UBINeLM t4mJ4tJdorASTAHY/OQad8aUb9d0nOSJFw4= X-RZG-AUTH: :O2kGeEG7b/pS1EK7WHa0hxqKZr4lnx6UhToX1IWHkW4X7v2ImaU2CVqpyLmhQrgx3Ci16w== X-RZG-CLASS-ID: mo00 Received: from mail.obsigna.com (b1504ef0.virtua.com.br [177.80.78.240]) by smtp.strato.de (RZmta 37.18 DYNA|AUTH) with ESMTPSA id h0750bs1A1xU3GK (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate) for ; Wed, 10 Feb 2016 02:59:30 +0100 (CET) Received: from rolf.projectworld.net (rolf.projectworld.net [192.168.222.5]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.obsigna.com (Postfix) with ESMTPSA id 9AF1975900 for ; Tue, 9 Feb 2016 23:59:27 -0200 (BRST) From: "Dr. Rolf Jansen" Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: What is the best method to keep FreeBSD on AWS-EC2 up to date? Message-Id: Date: Tue, 9 Feb 2016 23:59:27 -0200 To: freebsd-cloud@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) X-Mailer: Apple Mail (2.3112) X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Feb 2016 01:59:35 -0000 Hello! I did a trial setup on AWS-EC2 using the FreeBSD 10.2 AMI by Colin = Percival from the AWS Marketplace. The installation went smooth by a few = clicks, and everything is running fine for now. However, I got some = doubts about the correct updating path, because the usage instructions = of the AMI descriptions state: > =E2=80=A6 =46rom there on, standard FreeBSD usage and system = configuration applies, except that freebsd-update cannot be used (due to = local patches needed for the FreeBSD/EC2 platform). When I cannot use freebsd-update, what else should I do to keep the = system updated? The AMI got FreeBSD Release 10.2-p12. I am mostly concerned about the = upcoming next patch levels. I guess, when it comes to a system upgrade, = it would be best to create a new clean instance with the new system, get = my stuff over and terminate the old instance. I only don't want to do = this for every security patch.=20 Many thanks in advance for your ideas. Best regards Rolf= From owner-freebsd-cloud@freebsd.org Wed Feb 10 06:59:56 2016 Return-Path: Delivered-To: freebsd-cloud@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A33DCAA35D8 for ; Wed, 10 Feb 2016 06:59:56 +0000 (UTC) (envelope-from 00000152c9fa95e9-5c023d6f-98aa-4ee3-a784-1b816d739bb3-000000@amazonses.com) Received: from a8-60.smtp-out.amazonses.com (a8-60.smtp-out.amazonses.com [54.240.8.60]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6DD38CC1 for ; Wed, 10 Feb 2016 06:59:56 +0000 (UTC) (envelope-from 00000152c9fa95e9-5c023d6f-98aa-4ee3-a784-1b816d739bb3-000000@amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=vnqrkfnvu6csdl6mwgk5t6ix3nnepx57; d=tarsnap.com; t=1455087588; h=Subject:To:References:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; bh=u5QA4HvGeevHbvz1AWyy/QYLkW3RVaaFbMM4LfG/ilQ=; b=ZoGlprosCZph0N7VFiEBE4trqLwgospIzMcGkyfJAzpwShEV7UUvm9Phfzwl14Q+ XtqwdfU1rpFmLliayIRDggW2s/7APNlSeNnXL2rx5UefuLXY/UPNqVL/J/dZU1Or5pk jKo7CyaC8AfS4mKpqq5J6sBO2tX0+o4SGBVbM4Ns= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1455087588; h=Subject:To:References:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:Feedback-ID; bh=u5QA4HvGeevHbvz1AWyy/QYLkW3RVaaFbMM4LfG/ilQ=; b=Hoz/NogOSDBuw7n76/Ika8QCwumOd05KMZz3xfUBjn40/SQEpfoXsB9NL4l8Vnow E2Hz5ms+MLQwIM486rG0oclzj5IbsnNlWN52jf+jX5EPxB7lD9crttrEQreEvstMx0c 2nmeEqBNLnFm59gAMttkhn/bneKtHZOUDYvAKYb4= Subject: Re: What is the best method to keep FreeBSD on AWS-EC2 up to date? To: "Dr. Rolf Jansen" , freebsd-cloud@freebsd.org References: From: Colin Percival Message-ID: <00000152c9fa95e9-5c023d6f-98aa-4ee3-a784-1b816d739bb3-000000@email.amazonses.com> Date: Wed, 10 Feb 2016 06:59:48 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-SES-Outgoing: 2016.02.10-54.240.8.60 Feedback-ID: 1.us-east-1.Lv9FVjaNvvR5llaqfLoOVbo2VxOELl7cjN0AOyXnPlk=:AmazonSES X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Feb 2016 06:59:56 -0000 On 02/09/16 17:59, Dr. Rolf Jansen wrote: >> … From there on, standard FreeBSD usage and system configuration applies, except that freebsd-update cannot be used (due to local patches needed for the FreeBSD/EC2 platform). > > When I cannot use freebsd-update, what else should I do to keep the system updated? You can use freebsd-update. The text on that Marketplace page is out of date. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid From owner-freebsd-cloud@freebsd.org Wed Feb 10 09:16:24 2016 Return-Path: Delivered-To: freebsd-cloud@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9F1DAA3E7E for ; Wed, 10 Feb 2016 09:16:24 +0000 (UTC) (envelope-from rj@obsigna.com) Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6A8DDE28 for ; Wed, 10 Feb 2016 09:16:23 +0000 (UTC) (envelope-from rj@obsigna.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1455095781; l=537; s=domk; d=obsigna.com; h=To:References:Content-Transfer-Encoding:Cc:Date:In-Reply-To:From: Subject:Mime-Version:Content-Type; bh=oLisbXUDbC8hC8jNL8wZw+DFV0U9kRuhK9BGAMXUUCE=; b=SyTuKiPE+87f/lKV1Fcnbd0N+4PwkmIKOez4PibpVlGvTl8DsX3V0F81sYDwHVUj2jY x966L2b8cEu7ID2K4SSHXzwbgx6O58Fg87ep7MavdQP/5AhwEJROPRN5hux7HJ3ioKc7E /rqJnmkbP9BkOynhyqJpUGNA7lmdaSr3KWY= X-RZG-AUTH: :O2kGeEG7b/pS1EK7WHa0hxqKZr4lnx6UhToX1IWHkW4X7v2ImaU2CVqpyLmhRLYu0vEWnk0= X-RZG-CLASS-ID: mo00 Received: from mail.obsigna.com (b150a194.virtua.com.br [177.80.161.148]) by smtp.strato.de (RZmta 37.18 DYNA|AUTH) with ESMTPSA id h04f97s1A9GJ6x5 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate); Wed, 10 Feb 2016 10:16:19 +0100 (CET) Received: from rolf.projectworld.net (rolf.projectworld.net [192.168.222.5]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.obsigna.com (Postfix) with ESMTPSA id A262675900; Wed, 10 Feb 2016 07:16:16 -0200 (BRST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: What is the best method to keep FreeBSD on AWS-EC2 up to date? From: "Dr. Rolf Jansen" In-Reply-To: <00000152c9fa9b4d-48381ee7-9b7a-4547-9981-3945dbd242dd-000000@email.amazonses.com> Date: Wed, 10 Feb 2016 07:16:14 -0200 Cc: freebsd-cloud@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <83A5F020-ABC6-4CA8-B78A-A2A84ABE509A@obsigna.com> References: <00000152c9fa9b4d-48381ee7-9b7a-4547-9981-3945dbd242dd-000000@email.amazonses.com> To: Colin Percival X-Mailer: Apple Mail (2.3112) X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Feb 2016 09:16:24 -0000 > Am 10.02.2016 um 04:59 schrieb Colin Percival : >=20 > On 02/09/16 17:59, Dr. Rolf Jansen wrote: >>> =E2=80=A6 =46rom there on, standard FreeBSD usage and system = configuration applies, except that freebsd-update cannot be used (due to = local patches needed for the FreeBSD/EC2 platform). >>=20 >> When I cannot use freebsd-update, what else should I do to keep the = system updated? >=20 > You can use freebsd-update. The text on that Marketplace page is out = of date. OK, thank you very much! From owner-freebsd-cloud@freebsd.org Thu Feb 11 09:46:03 2016 Return-Path: Delivered-To: freebsd-cloud@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AEEB6AA4998 for ; Thu, 11 Feb 2016 09:46:03 +0000 (UTC) (envelope-from scott.otis@tandemcal.com) Received: from Filter02.GreenHouseData.com (outmail.fchosted.com [205.234.75.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "filter.greenhousedata.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8FC3D13E1 for ; Thu, 11 Feb 2016 09:46:02 +0000 (UTC) (envelope-from scott.otis@tandemcal.com) X-ASG-Debug-ID: 1455183955-0a955d73331a7f6d0001-uSjTss Received: from mail.fchosted.com (mailflow.greenhousedata.com [10.36.251.68]) by Filter02.GreenHouseData.com with ESMTP id 1lfYc5lUxmt6fPWR (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO) for ; Thu, 11 Feb 2016 01:45:55 -0800 (PST) X-Barracuda-Envelope-From: scott.otis@tandemcal.com Received: from EVT01FEVWEXA001.fchosted.com ([10.10.2.130]) by sea02fevwexa001 ([10.10.2.131]) with mapi id 14.03.0266.001; Thu, 11 Feb 2016 01:45:54 -0800 From: Scott Otis To: "freebsd-cloud@freebsd.org" Subject: 10.2 Release crashing after 1 hr on Azure with "Standard DS" VM sizes Thread-Topic: 10.2 Release crashing after 1 hr on Azure with "Standard DS" VM sizes X-ASG-Orig-Subj: 10.2 Release crashing after 1 hr on Azure with "Standard DS" VM sizes Thread-Index: AdFksG7nSp1xugvKTs+ThlanyxiBtg== Date: Thu, 11 Feb 2016 09:45:54 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [24.19.233.47] MIME-Version: 1.0 X-Barracuda-Connect: mailflow.greenhousedata.com[10.36.251.68] X-Barracuda-Start-Time: 1455183955 X-Barracuda-Encrypted: AES128-SHA X-Barracuda-URL: https://Filter.GreenHouseData.com:443/cgi-mod/mark.cgi X-Barracuda-Scan-Msg-Size: 39424 X-Virus-Scanned: by bsmtpd at GreenHouseData.com X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using per-user scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests=HTML_MESSAGE X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.26941 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.00 HTML_MESSAGE BODY: HTML included in message Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2016 09:46:03 -0000 Been trying to get a FreeBSD VM server running on Azure on a "Standard DS" = size VM (so I have access to SSD storage for PostgreSQL). The "Standard DS= " series of VMs also have faster/newer CPUs than the original "Standard A" = series of VMs. I am using the image of FreeBSD from here: https://vmdepot.= msopentech.com/Vhd/Show?vhdId=3D56718&version=3D61117 . After setting up t= he VM it started rebooting every hour or so. Initially I thought this was = an Azure issue and Azure was forcibly rebooting the VM because it wasn't ge= tting health reports back. But I don't' believe this is the case anymore a= nd I think FreeBSD is crashing. (Note: I have setup a FreeBSD VM with a "S= tandard A" series VM and that seems to be running fine - though it looks li= ke it might have crashed after about 38 hours which is much better than cra= shing after 1 hour). Here is the "last" log from the last two days: [--redacted--] pts/2 [--redacted--] Fri Feb 5 21:10 still logged in [--redacted--] pts/1 [--redacted--] Fri Feb 5 21:10 still logged in [--redacted--] pts/0 [--redacted--] Fri Feb 5 20:58 - 21:10 (00:12) boot time Fri Feb 5 20:53 [--redacted--] pts/1 [--redacted--] Fri Feb 5 04:59 - crash (15:54) [--redacted--] pts/0 [--redacted--] Fri Feb 5 04:59 - 04:59 (00:00) boot time Fri Feb 5 04:41 boot time Fri Feb 5 02:16 [--redacted--] pts/1 [--redacted--] Fri Feb 5 00:36 - crash (01:40) [--redacted--] pts/0 [--redacted--] Fri Feb 5 00:36 - 00:36 (00:00) boot time Fri Feb 5 00:29 shutdown time Thu Feb 4 09:33 boot time Thu Feb 4 08:47 [--redacted--] pts/0 [--redacted--] Thu Feb 4 07:25 - crash (01:21) boot time Thu Feb 4 07:00 boot time Thu Feb 4 05:03 boot time Thu Feb 4 02:45 [--redacted--] pts/0 [--redacted--] Thu Feb 4 01:08 - crash (01:36) boot time Thu Feb 4 00:58 There are boot times without previous shutdown times - and there is that "c= rash" text (which is why I'm thinking it is a crash). I added this to /etc/rc.conf: dumpdev=3D"AUTO" dumpdir=3D"/var/crash" Here is the info on the swapfile: sudo swapinfo -h Device 512-blocks Used Avail Capacity /dev/gpt/swapfs 2097152 0B 1.0G 0% Server has 3.5 GB of RAM. Here is the boot log after a crash (says there are no core dumps found... a= ny way to figure out why it is not dumping the core?): -=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|= =08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08= \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/= =08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08[H[J-=08= \=08|=08/=08-=08\=08 [7;46H ``` `[8;46Hs` `.....---.= ......--.``` -/[9;46H+o .--` /y:` +.[10;46H yo`:. = :o `+-[11;46H y/ -/` -o/[12;46H .- = ::/sy+:.[13;46H / `-- /[14;46H`: = :`[15;46H`: :`[16;46H / = /[17;46H .- -.[18;46H -- = -.[19;46H `:` `:`[20;46H .-- `--.[21;46H= .---.....----.|=08/=08-=08\=08 [1;2H ______ ____ __= ___ _____ [2;2H| ____| | _ \ / ____| __ \ [3;2H| |___ _ __ = ___ ___ | |_) | (___ | | | |[4;2H| ___| '__/ _ \/ _ \| _ < \___ \| | |= |[5;2H| | | | | __/ __/| |_) |____) | |__| |[6;2H| | | | | | |= | | | |[7;2H|_| |_| \___|\___||____/|_____/|_____/ [10;2H|= [11;2H|[12;2H|[13;2H|[14;2H|[15;2H|[16;2H|[17;2H|[18;2H|[19;2H|[20;2H|[21;2= H|[10;44H|[11;44H|[12;44H|[13;44H|[14;44H|[15;44H|[16;44H|[17;44H|[18;44H|[= 19;44H|[20;44H|[21;44H|[9;3H=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D[22;3H=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D[9;2H+[22;2H+[9;44= H+[22;44H+[25;0H|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08[9;= 15HWelcome to FreeBSD[11;5H1 [11;6H.[11;8HBoot Multi User [Enter][12;5H2 [1= 2;6H.[12;8HBoot [S]ingle User[13;5H3 [13;6H.[13;8H[Esc]ape to loader prompt= [14;5H4 [14;6H.[14;8HReboot[16;5HOptions:[17;5H5 [17;6H.[17;8H[K]ernel: ker= nel (1 of 2)[18;5H6 [18;6H.[18;8HConfigure Boot [O]ptions...[25;0H[23;4HAut= oboot in 9 seconds. [Space] to pause[25;0H[23;4HAutoboot in 8 seconds. [Spa= ce] to pause[25;0H[23;4HAutoboot in 7 seconds. [Space] to pause[25;0H[23;4H= Autoboot in 6 seconds. [Space] to pause[25;0H[23;4HAutoboot in 5 seconds. [= Space] to pause[25;0H[23;4HAutoboot in 4 seconds. [Space] to pause[25;0H[23= ;4HAutoboot in 3 seconds. [Space] to pause[25;0H[23;4HAutoboot in 2 seconds= . [Space] to pause[25;0H[23;4HAutoboot in 1 seconds. [Space] to pause[25;0H= [23;4H [25;0H-=08\=08|=08/=08-=08\=08= |=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-= =08\=08|=08/=08/boot/kernel/kernel text=3D0xfc8de8 -=08\=08|=08/=08-=08\=08= |=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-= =08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08= /=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\= =08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08= -=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|= =08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08= \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08data=3D0x1283b0+0x207880 /=08-=08\= =08|=08/=08-=08\=08|=08/=08-=08syms=3D[0x8+0x145350\=08|=08/=08-=08\=08|=08= /=08-=08\=08|=08+0x8+0x15fe20/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08] Booting... |=08/=08-=08\=08|=08/=08Copyright (c) 1992-2015 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.2-RELEASE #0 r286666: Wed Aug 12 15:26:37 UTC 2015 root at releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 CPU: Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz (1109.29-MHz K8-class CPU) Origin=3D"GenuineIntel" Id=3D0x206d7 Family=3D0x6 Model=3D0x2d Steppi= ng=3D7 Features=3D0xf83fbff Features2=3D0x9e982203 AMD Features=3D0x20100800 AMD Features2=3D0x1 XSAVE Features=3D0x1 Hypervisor: Origin =3D "Microsoft Hv" real memory =3D 3758096384 (3584 MB) avail memory =3D 3515142144 (3352 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: random device not loaded; using insecure entropy ioapic0: Changing APIC ID to 0 ioapic0 irqs 0-23 on motherboard random: initialized kbd1 at kbdmux0 vmbus0: on motherboard acpi0: on motherboard acpi0: Power Button (fixed) cpu0: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177= ,0x376,0xffa0-0xffaf at device 7.1 on pci0 ata0: at channel 0 on atapci0 ata1: at channel 1 on atapci0 pci0: at device 7.3 (no driver attached) vgapci0: mem 0xf8000000-0xfbffffff irq 11 at devic= e 8.0 on pci0 vgapci0: Boot video device atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: console (115200,n,8,1) uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on= acpi0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 orm0: at iomem 0xc0000-0xcbfff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ppc0: cannot reserve I/O port range Timecounters tick every 1.000 msec random: unblocking device. Timecounter "TSC" frequency 1109287570 Hz quality 800 Timecounter "Hyper-V" frequency 10000000 Hz quality 10000000 storvsc0 on vmbus0 storvsc1 on vmbus0 hyperv-utils0 on vmbus0 hyperv-utils0: Hyper-V Service attaching: Hyper-V Heartbeat Service hyperv-utils1 on vmbus0 hyperv-utils1: Hyper-V Service attaching: Hyper-V KVP Service da0 at blkvsc0 bus 0 scbus1 target 0 lun 0 hyperv-utils2 on vmbus0 hyperv-utils2: Hyper-V Service attaching: Hyper-V Shutdown Service da0: Fixed Direct Access SPC-2 SCSI device hyperv-utils3 on vmbus0 hyperv-utils3: Hyper-V Service attaching: Hyper-V Time Synch Service da0: 300.000MB/s transfers hn0: on vmbus0 da0: Command Queueing enabled da0: 21505MB (44042240 512 byte sectors: 255H 63S/T 2741C) da1 at blkvsc1 bus 0 scbus2 target 1 lun 0 da1: Fixed Direct Access SPC-2 SCSI device da1: 300.000MB/s transfershn0: unknown status 1073872902 received hn0: unknown status 1073872902 received hn0: hv send offload request succeeded da1: Command Queueing enabled hn0: Using defaults for TSO: 65518/35/2048 hn0: Ethernet address: 00:0d:3a:31:0d:fc storvsc2 on vmbus0 da1: 7168MB (14680064 512 byte sectors: 255H 63S/T 913C) storvsc3 on vmbus0 Trying to mount root from ufs:/dev/gpt/rootfs [rw]... WARNING: / was not properly dismounted Setting hostuuid: 253d30c5-d221-8548-b887-f87baa231b2d. Setting hostid: 0xd995724c. Entropy harvesting: interrupts ethernet point_to_point swi. Starting file system checks: ** SU+J Recovering /dev/gpt/rootfs ** Reading 33554432 byte journal from inode 8. ** Biilding recovery table. ** Resolving unreferenced inode list. ** Processing journal entries. ** 1 journal records in 512 bytes for 6.25% utilization ** Freed 1 inodes (0 dirs) 0 blocks, and 0 frags. ***** FILE SYSTEM MARKED CLEAN ***** Mounting local file systems:. Writing entropy file:. Setting hostname: [--redacted--] hn0: link state changed to UP Starting dhclient. DHCPDISCOVER on hn0 to 255.255.255.255 port 67 interval 7 DHCPOFFER from 168.63.129.16 unknown dhcp option value 0xf5 DHCPREQUEST on hn0 to 255.255.255.255 port 67 DHCPACK from 168.63.129.16 unknown dhcp option value 0xf5 bound to 10.0.2.5 -- renewal in -1 seconds. Starting Network: lo0 hn0. lo0: flags=3D8049 metric 0 mtu 16384 options=3D600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 nd6 options=3D21 hn0: flags=3D8843 metric 0 mtu 1500 options=3D31b ether 00:0d:3a:31:0d:fc inet 10.0.2.5 netmask 0xffffff00 broadcast 10.0.2.255 nd6 options=3D29 Starting devd. add net fe80::: gateway ::1 add net ff02::: gateway ::1 add net ::ffff:0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1 ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib 32-bit compatibility ldconfig path: /usr/lib32 Creating and/or trimming log files. Starting syslogd. No core dumps found. Clearing /tmp (X related). Updating motd:. Mounting late file systems:. Performing sanity check on sshd configuration. Any help would be appreciated! Scott Otis CTO & Co-Founder Tandem www.tandemcal.com