From owner-freebsd-sparc64@freebsd.org Fri Feb 17 07:14:04 2017 Return-Path: Delivered-To: freebsd-sparc64@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 36EC5CE26C9 for ; Fri, 17 Feb 2017 07:14:04 +0000 (UTC) (envelope-from gordonzaft@gmail.com) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EE4FE1893 for ; Fri, 17 Feb 2017 07:14:03 +0000 (UTC) (envelope-from gordonzaft@gmail.com) Received: by mail-it0-x231.google.com with SMTP id x75so6786652itb.0 for ; Thu, 16 Feb 2017 23:14:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=66FkaOSWXOkeK09U6djcoNL3/rzlxXOA/f9TIjYxdtA=; b=W2KzGAsonQvTHItZzqDPj3ioEIUz7AgS/bzyhPqJMvx0ZTPpSkZ+Sbg4lQld8e+OdL D6rcC6boyp7j8st7BBuN1auDuP11tO+WnAuPE7yC9H6+25/e+bbEIdHV7IpizkcVKsTL EbQ4K8I9goLWrS3ocZV2aDJIpjUrRSfPqUnhbBtFpc+2J8NxRV/9yc1bXlRQ8GNpQ2bW ro5uF8PRb/gN/b0TW3YeJqhRM/ORQtI6D7GoFs4jqSVx1qQlwN61k50g0aUATW+4HsAr uy2Y2yQdXSRcH8UNZ2kD3M3wB/LrIESCLG6t4HKqa98JhxMhFwAXeURxWahnVhnj2jg0 xWNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=66FkaOSWXOkeK09U6djcoNL3/rzlxXOA/f9TIjYxdtA=; b=K9r7IAUobexSTwAvcmkebiSc/mN6X+zJ+T1TBwGP4wG3nVan7st4jqLVt6lZT3gW6s 1fNcW5sudc7fId77EJqb6Fcx0My4Pkpkrems1SkpHhI/HzPplqLtIt6S20sIwrO8IPo/ gtTMbyZ1lNWru2CBJUtei/GZuFA3RgfmkqoOck3+zgM37RAwAWNNhYzF3RPaDxF9cBxG AnZJgWNf+WM+s/+uC+45tSh9M7Q6p/O2F/Bmcfmf8oxJrhWQCDEMxcex+Are7aC/M3t+ MsA4KB34Kx7zZk9ODbdmSCo/Hy1emBdZ7WIAJkz/lkv8+Fv85wyulHfN8DdXJzyS9JC7 mtbA== X-Gm-Message-State: AMke39nGmkhE2Xxw3OH0KA97/SsVD4vUvtIgrkXqPggqme0GGS3PT1TzafQhp14xsUr357/cQ1Sa/Og8Azhw0A== X-Received: by 10.107.59.205 with SMTP id i196mr5673146ioa.114.1487315643153; Thu, 16 Feb 2017 23:14:03 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.15.93 with HTTP; Thu, 16 Feb 2017 23:14:02 -0800 (PST) In-Reply-To: References: From: Gordon Zaft Date: Fri, 17 Feb 2017 00:14:02 -0700 Message-ID: Subject: Re: compiler issues To: Joe Nosay Cc: freebsd-sparc64@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Feb 2017 07:14:04 -0000 I wanted to follow up on this post. I've discovered that if I build manually (i.e. "make install") instead of using portmaster, I can successfully build large packages. When I get the segmentation fault I simply restart (make install again) and as one would hope it picks up where it left off. I was able to build and install gcc 4.9.4 this way (it took a long time!). Note that portmaster won't work because it does a make clean when it fails, so you are starting from scratch every time. It's a feature, but one that's not helpful in this particular case. G On Wed, Nov 30, 2016 at 11:04 AM, Joe Nosay wrote: > Give it a try and report your progress to the community. > > > On Wed, Nov 30, 2016 at 12:54 PM, Gordon Zaft wrote: >> >> Hmm. So you are saying you think this stuff would build with clang >> and doesn't with gcc? I thought others were able to build this >> stuff... >> >> G >> >> On Wed, Nov 30, 2016 at 9:59 AM, Joe Nosay wrote: >> > This may bounce. There are not enough developers available to port clang >> > and >> > llvm to SPARC64 at the moment. >> > >> > On Tue, Nov 29, 2016 at 5:04 PM, Gordon Zaft >> > wrote: >> >> >> >> I am still experiencing this building a variety of ports, most >> >> recently binutils. >> >> >> >> internal compiler error: Segmentation fault >> >> >> >> I'm wondering if there is something deeper going on? Still don't have >> >> a way out of this at this point. >> >> >> >> G >> >> >> >> On Mon, Oct 31, 2016 at 2:17 PM, Gordon Zaft >> >> wrote: >> >> > Sun U5 running 11.0, 512MB memory >> >> > >> >> > I'm trying to do some updates and I keep getting segmentation faults >> >> > while >> >> > compiling. I got this for llvm37, spidermonkey170 and ... something >> >> > else. >> >> > >> >> > I looked at my install and realized the gcc I installed with 10.x was >> >> > 4.2.1 >> >> > which is pretty old, so I decided to update to 4.91 in hopes that >> >> > would >> >> > solve some of these issues. >> >> > >> >> > Alas, I get: >> >> > >> >> > In file included from >> >> > /usr/ports/lang/gcc49/work/gcc-4.9.4/gcc/c-family/c-common.c:11936: >> >> > >> >> > ./gt-c-family-c-common.h:254: internal compiler error: Segmentation >> >> > fault >> >> > >> >> > Please submit a full bug report, with preprocessed source if >> >> > appropriate. >> >> > >> >> > I'm going to try updating to something not so recent but i'm >> >> > wondering >> >> > if >> >> > others have seen this issue. >> >> > >> >> > -- >> >> > Gordon Zaft >> >> > Province 35 Governor >> >> > Phi Mu Alpha Sinfonia Fraternity >> >> > gordonzaft@gmail.com >> >> >> >> >> >> >> >> -- >> >> Gordon Zaft >> >> Province 35 Governor >> >> Phi Mu Alpha Sinfonia Fraternity >> >> gordonzaft@gmail.com >> >> _______________________________________________ >> >> freebsd-sparc64@freebsd.org mailing list >> >> https://lists.freebsd.org/mailman/listinfo/freebsd-sparc64 >> >> To unsubscribe, send any mail to >> >> "freebsd-sparc64-unsubscribe@freebsd.org" >> > >> > >> >> >> >> -- >> Gordon Zaft >> Province 35 Governor >> Phi Mu Alpha Sinfonia Fraternity >> gordonzaft@gmail.com > > -- Gordon Zaft Province 35 Governor Phi Mu Alpha Sinfonia Fraternity gordonzaft@gmail.com From owner-freebsd-sparc64@freebsd.org Fri Feb 17 08:05:25 2017 Return-Path: Delivered-To: freebsd-sparc64@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 C4BD6CE29DA for ; Fri, 17 Feb 2017 08:05:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AE78311B7 for ; Fri, 17 Feb 2017 08:05:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1H85P5J058949 for ; Fri, 17 Feb 2017 08:05:25 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-sparc64@FreeBSD.org Subject: [Bug 195934] clang350-import branch not working on sparc64 Date: Fri, 17 Feb 2017 08:05:25 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: edinaclark11@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: dim@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Feb 2017 08:05:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D195934 Edina Clark changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |edinaclark11@gmail.com --- Comment #21 from Edina Clark --- it isn't a processor you can drop into a PC motherboard and have work. You would require whatever remains of the supercomputer to really make utilizat= ion of the processors - it will have huge numbers of them. I am hardware engine= er and writer at http://www.essaycampus.co.uk. These machines commonly require some fairly radical cooling and it isn't remarkable for fluid nitrogen to be utilized to this end. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-sparc64@freebsd.org Sat Feb 18 04:20:54 2017 Return-Path: Delivered-To: freebsd-sparc64@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 05975CE40B8 for ; Sat, 18 Feb 2017 04:20:54 +0000 (UTC) (envelope-from gordonzaft@gmail.com) Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C42B3CDD for ; Sat, 18 Feb 2017 04:20:53 +0000 (UTC) (envelope-from gordonzaft@gmail.com) Received: by mail-it0-x234.google.com with SMTP id h10so37608315ith.1 for ; Fri, 17 Feb 2017 20:20:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=6FjWdXOh5aLOKbIHIdxu1Gf496aFyxNims+acqt1gp0=; b=l5q0q2xBq2BINTqYFFZFhuFJj5FTjNnnC53hpJk5a9p6Lm8t3FJMZp4TheYmYQFsQr xaRAW3NT/d724EszEnwObXDkqBjdW2sv6ZxJjkqWZr/g/rMVD3JbKkJQM4CHp/VANuWF 9qyXgiVJDMzHk6zIf5wisoDYYwiF7CHQU3DRR+JciUPmkgsTfPWCZCHkEErSkvcFrIf2 qSi0XZsTkKQ9fA3tSPZSZnka4yLvkcXK4/xYv2mwBeQovlDUoZSryGxgyReWdiW0ieWM qyD5QjJTbdl17Gj1kn6lgLves7LHpJDgMSFKWeU6ZVzFZZmxTasK9uwvP/9xyKHnWiiM VGqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=6FjWdXOh5aLOKbIHIdxu1Gf496aFyxNims+acqt1gp0=; b=fMP1YUVqbciFgtzHpgOYewdS0KWJi53aMg+0FnSt6YzEsl32bkKZTqlLip9isOtrr7 lNePqoXn4XO5PTKIVgjrGW5jFI89wKZ5F7XdNHR/xvvOr5MIAYLH3vT5fFlqVD9OE0SQ TDq0DAcW1nyl0Ey2lbpPXeU6AKflK4Wn2ZBtJAjqNAia6oZzMYf5EqXxvx9U6+vI27d8 G5GozAF0ls2w6WuJChiEOJ2dHifvU1CvGw+GrcZyXLUQ9whPZxD+w930gTZ5cDubGQkZ eWur0cTqpiQJSB4mBBhX4RDSqhDyTW5WjgVNHXTRbFi0QVky8dOaugPsmjrLDwDv6ijO 0ATQ== X-Gm-Message-State: AMke39mwEt4hngotJaqpAKWaGAukriuYjqdEparQ+NAVPJpgtUycBJ8VRYOLW/e/tUUoc61OB2wsqHheCAJEDw== X-Received: by 10.36.206.2 with SMTP id v2mr8286439itg.74.1487391652775; Fri, 17 Feb 2017 20:20:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.15.93 with HTTP; Fri, 17 Feb 2017 20:20:52 -0800 (PST) In-Reply-To: References: From: Gordon Zaft Date: Fri, 17 Feb 2017 21:20:52 -0700 Message-ID: Subject: Re: Adding disk on Sun Fire V245 w/FreeBSD 11 To: freebsd-sparc64@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Feb 2017 04:20:54 -0000 I finally figured this out and figured I should document for posterity... I realized I had not tried to do a probe-scsi from the OBP prompt, so I did that. I got an endless cascade of Base SAS World Wide ID is 0! This must be fixed immediately using set-sas-wwid So digging into this document https://docs.oracle.com/cd/E19088-01/v215.srvr/819-3040-18/Disk-vols.html I realized the onboard RAID was messing me up. Following the directions, and the ok> prompt: setenv auto-boot? false setenv fcode-debug? true reset-all Then a ok>show-disks Select the SCSI disk controller (for me it was b) ) ok>select ^Y (inserts the line from show-disks; trim off the /disk) doing ok>show-volumes showed that the disks that I wasn't seeing were listed as disabled (or inactive) volumes. To fix this I deleted each volume ok>0 delete-volume ok>1 delete-volume ok>show-volumes now shows no volumes. Doing a ok>setenv fcode-debug? false ok>reset-all when the system came back a probe-scsi showed the disks now, and when I boot they are in dmesg. I still had to put a VTOC on them since, in my case they were IBM disks, or wiped Sun disks: /sbin/gpart create -s VTOC8 da1 Then /sbin/gpart add -t freebsd-ufs da1 to create one big partition. Then a newfs as usual and you're good to go! G On Fri, Nov 18, 2016 at 9:35 PM, Gordon Zaft wrote: > > I have a Sun Fire V245 running 11.0. It had one 146GB hard disk in it. I > went to add a second similar disk but the OS doesn't seem to see it. I can > tell the hardware sees it as if I pull it out while the machine's on I get > an alert from the ALOM. But I don't see a "da1" device in dmesg. > > What am I doing wrong? > > Thanks in advance! > > -- > Gordon Zaft > Province 35 Governor > Phi Mu Alpha Sinfonia Fraternity > gordonzaft@gmail.com > -- Gordon Zaft Province 35 Governor Phi Mu Alpha Sinfonia Fraternity gordonzaft@gmail.com From owner-freebsd-sparc64@freebsd.org Sat Feb 18 04:21:38 2017 Return-Path: Delivered-To: freebsd-sparc64@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 4E285CE4107 for ; Sat, 18 Feb 2017 04:21:38 +0000 (UTC) (envelope-from gordonzaft@gmail.com) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 19645DA4 for ; Sat, 18 Feb 2017 04:21:38 +0000 (UTC) (envelope-from gordonzaft@gmail.com) Received: by mail-io0-x22c.google.com with SMTP id j18so5002204ioe.2 for ; Fri, 17 Feb 2017 20:21:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=Uhdhjm1p+skE9wZuWpG5I9g5KIEA0IWV69Jlub7Z//Q=; b=VL+us5rowVN5i3rOI1pTWrPDwmt37OrP7ojaxuYt4ddUuBd5B/N9uMgY6T/uN1GmeL lPbzfp2ObfvQsYlqBklpGlHPqXjNcpn9TysclFc8KDIGyJddYj3MtifxnBwEamuGbpuJ MxAZabhMOYLaU/EAmCMPw39CROlWQFSOz7Z776AXhxtaAYZvtXuTbRRA+IjQLPAcN4BA 23rIVmujouQF62LykkpIv+qINlMnxwUUniEFqLl0JVMhQQ5TuQPr5HyEFIhRxhNq9OZM f4MTfMJetW9dzDbxUDKUlxqcN/cAbEJRGjA+LsmNNTkp3WJ8G8jhgEc2+PuJMZhy7T1L vopw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=Uhdhjm1p+skE9wZuWpG5I9g5KIEA0IWV69Jlub7Z//Q=; b=a/diNF+/KJNuB9VZRm3dY3cwc9psCmGMqH7Y31Ak0dxGQaK0BnkOZOhR3Fzeo4UMhO IiuAuNZfP2jBrViU4cshnIANCeEuCtXv8EW08W2eoBuUfdFzqDii+jy7XeLClWDoA4Bs uiIHczgsSefHsIe6WfuLO7S3DJNE+4/NltD3e8KP2C+mxk0aQdC02EfEiywcECqHaPoW 5YKpVqEgLrf1zNytiSsD91XQeIzYyOV7r1tjwx/mp6ouIROd7+osk48nwJy6gdoJ0mno FtjiUyZkj+o8mzk7hUAVsyw0KEUmsx7tplQ6RVF6uI/+yUykNbt2rdEe6c9TIo0lFPh0 pyfQ== X-Gm-Message-State: AMke39msqYmYlhqo2VcTS1b9liHTleUoNiiTP922tjDnLHAECXFB3Lp1++jD7FONoWux+Jga5P0Gvr+HttWqmg== X-Received: by 10.107.15.70 with SMTP id x67mr9114583ioi.103.1487391697033; Fri, 17 Feb 2017 20:21:37 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.15.93 with HTTP; Fri, 17 Feb 2017 20:21:36 -0800 (PST) In-Reply-To: References: From: Gordon Zaft Date: Fri, 17 Feb 2017 21:21:36 -0700 Message-ID: Subject: Re: Adding disk on Sun Fire V245 w/FreeBSD 11 To: freebsd-sparc64@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Feb 2017 04:21:38 -0000 Sorry, was not in plain text mode: I finally figured this out and figured I should document for posterity... I realized I had not tried to do a probe-scsi from the OBP prompt, so I did that. I got an endless cascade of Base SAS World Wide ID is 0! This must be fixed immediately using set-sas-wwid So digging into this document https://docs.oracle.com/cd/E19088-01/v215.srvr/819-3040-18/Disk-vols.html I realized the onboard RAID was messing me up. Following the directions, and the ok> prompt: setenv auto-boot? false setenv fcode-debug? true reset-all Then a ok>show-disks Select the SCSI disk controller (for me it was b) ) ok>select ^Y (inserts the line from show-disks; trim off the /disk) doing ok>show-volumes showed that the disks that I wasn't seeing were listed as disabled (or inactive) volumes. To fix this I deleted each volume ok>0 delete-volume ok>1 delete-volume ok>show-volumes now shows no volumes. Doing a ok>setenv fcode-debug? false ok>reset-all when the system came back a probe-scsi showed the disks now, and when I boot they are in dmesg. I still had to put a VTOC on them since, in my case they were IBM disks, or wiped Sun disks: /sbin/gpart create -s VTOC8 da1 Then /sbin/gpart add -t freebsd-ufs da1 to create one big partition. Then a newfs as usual and you're good to go! On Fri, Feb 17, 2017 at 9:20 PM, Gordon Zaft wrote: > > I finally figured this out and figured I should document for posterity... > > I realized I had not tried to do a probe-scsi from the OBP prompt, so I did > that. I > got an endless cascade of > > Base SAS World Wide ID is 0! > This must be fixed immediately using set-sas-wwid > > So digging into this document > https://docs.oracle.com/cd/E19088-01/v215.srvr/819-3040-18/Disk-vols.html I > realized the onboard RAID was messing me up. > > Following the directions, and the ok> prompt: > > setenv auto-boot? false > setenv fcode-debug? true > reset-all > > Then a > ok>show-disks > > Select the SCSI disk controller (for me it was b) ) > > ok>select ^Y (inserts the line from show-disks; trim off the /disk) > > doing > > ok>show-volumes > > showed that the disks that I wasn't seeing were listed as disabled (or > inactive) volumes. To fix this I deleted each volume > > ok>0 delete-volume > ok>1 delete-volume > > ok>show-volumes > > now shows no volumes. Doing a > > ok>setenv fcode-debug? false > ok>reset-all > > when the system came back a probe-scsi showed the disks now, and when I boot > they are in dmesg. > > I still had to put a VTOC on them since, in my case they were IBM disks, or > wiped Sun disks: > > /sbin/gpart create -s VTOC8 da1 > > Then > > /sbin/gpart add -t freebsd-ufs da1 > > to create one big partition. > > Then a newfs as usual and you're good to go! > > G > > > > On Fri, Nov 18, 2016 at 9:35 PM, Gordon Zaft wrote: >> >> >> I have a Sun Fire V245 running 11.0. It had one 146GB hard disk in it. I >> went to add a second similar disk but the OS doesn't seem to see it. I can >> tell the hardware sees it as if I pull it out while the machine's on I get >> an alert from the ALOM. But I don't see a "da1" device in dmesg. >> >> What am I doing wrong? >> >> Thanks in advance! >> >> -- >> Gordon Zaft >> Province 35 Governor >> Phi Mu Alpha Sinfonia Fraternity >> gordonzaft@gmail.com > > > > > -- > Gordon Zaft > Province 35 Governor > Phi Mu Alpha Sinfonia Fraternity > gordonzaft@gmail.com -- Gordon Zaft Province 35 Governor Phi Mu Alpha Sinfonia Fraternity gordonzaft@gmail.com From owner-freebsd-sparc64@freebsd.org Sat Feb 18 04:24:38 2017 Return-Path: Delivered-To: freebsd-sparc64@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 5E4A0CE429B for ; Sat, 18 Feb 2017 04:24:38 +0000 (UTC) (envelope-from gordonzaft@gmail.com) Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 28988ECA for ; Sat, 18 Feb 2017 04:24:38 +0000 (UTC) (envelope-from gordonzaft@gmail.com) Received: by mail-io0-x232.google.com with SMTP id j18so5017890ioe.2 for ; Fri, 17 Feb 2017 20:24:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=Hr+hpLWt+DOLp23ekayglRpW/CZE0VUzPLp2miOmOeg=; b=rOghgqoKCaTwzLz6y5ViZYOZsCKyPiTZq6kdAS1+iQqGO76AHCyNcMDWeifnHWWDjZ 9zGwHwUnWv9o+zMvUCr3ALVZq9m2YIMskFQ/+z5aL5GLWgUytyCga3ABgKaJn/91Ds45 5YfaDyfGxU5TFvnWmQKgAax6MspBk56hLyIlj3NuuEK3GCIe4O8lOWNgRcnhT/UfsFKc /rYuA3S3xWk0YGPg6baS12w3lq0TmFZAnlDfOvZm7FyIwyL8OZK9o3CYZSsgvD0a9kF8 YJI0jlcQinrzbq+1vYDJS3GOuqQoi8qiYw44ZOryQig81Sejg1WY9Oly+mbGPdjRcBvT TwQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=Hr+hpLWt+DOLp23ekayglRpW/CZE0VUzPLp2miOmOeg=; b=WGP/AdvQGIit7EPXAjh51LCNPawXtsE/vrTXZzHVr9OMIIR+hrm0JIp0Ws9ch5A03W zciYG4XGvlUIYaJeAlH2vrXpaDhipsmNuZmt7YQnwXk89Rc6TOgF14iQ0twwj3aQZ7Di nISdn8h8efGPmNWUW1n4FPfKoYpdfr/qpVvThDxMY0vH+thbXxU9OvJHIG5ceswvuwA+ XyGK7XkdfsUYzJpO+OcIwWKc4TKEnRASkFwTc/TAjiWFh2rPQMZE4suhBlq2LKCbes9Y /X40Lr7LKGLl4K1woZ9y2LmpCr5JT+TMQGL3ia752le75AI//+Vz6xtVCQJNEmEgda22 FalA== X-Gm-Message-State: AMke39mEqIA/2ClvpAbZt5vFG11inxhOam6W1uJ/AaBrvbJnLOcWN1LbCRbiOx4cjT0U9hiaHtqWivyQutWoig== X-Received: by 10.107.59.205 with SMTP id i196mr9517625ioa.114.1487391877256; Fri, 17 Feb 2017 20:24:37 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.15.93 with HTTP; Fri, 17 Feb 2017 20:24:36 -0800 (PST) In-Reply-To: References: From: Gordon Zaft Date: Fri, 17 Feb 2017 21:24:36 -0700 Message-ID: Subject: Re: Adding disk on Sun Fire V245 w/FreeBSD 11 To: freebsd-sparc64@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Feb 2017 04:24:38 -0000 Sorry, I left out a step. It may be necessary to do a gpart destroy da1 before the create. Fixed below. --------------- I finally figured this out and figured I should document for posterity... I realized I had not tried to do a probe-scsi from the OBP prompt, so I did that. I got an endless cascade of Base SAS World Wide ID is 0! This must be fixed immediately using set-sas-wwid So digging into this document https://docs.oracle.com/cd/E19088-01/v215.srvr/819-3040-18/Disk-vols.html I realized the onboard RAID was messing me up. Following the directions, and the ok> prompt: setenv auto-boot? false setenv fcode-debug? true reset-all Then a ok>show-disks Select the SCSI disk controller (for me it was b) ) ok>select ^Y (inserts the line from show-disks; trim off the /disk) doing ok>show-volumes showed that the disks that I wasn't seeing were listed as disabled (or inactive) volumes. To fix this I deleted each volume ok>0 delete-volume ok>1 delete-volume ok>show-volumes now shows no volumes. Doing a ok>setenv fcode-debug? false ok>reset-all when the system came back a probe-scsi showed the disks now, and when I boot they are in dmesg. I still had to put a VTOC on them since, in my case they were IBM disks, or wiped Sun disks: /sbin/gpart destroy da1 (just in case) /sbin/gpart create -s VTOC8 da1 Then /sbin/gpart add -t freebsd-ufs da1 to create one big partition. Then a newfs as usual and you're good to go! -- Gordon Zaft Province 35 Governor Phi Mu Alpha Sinfonia Fraternity gordonzaft@gmail.com