[OmniOS-discuss] Can't reinstall OmniOS on CF drive
I have a machine whose root disk is a 8GB CF. I installed OmniOS on
this drive a few weeks ago, but it won't let me do it again now (see
install_log below). The one crazy thing I see is that it's trying to
create a volume with a size of "3230.54765606m" - which seems like a
peculiar fraction to be passing into `zfs create`
How could it be that I could install 'stable' on this drive before and
now, using the exact same OmniOS install CD, it won't let me? Any ideas
how to clear or circumvent the issue?
Thanks,
Kent
2013-03-25 16:16:56,393 InstallationLogger INFO START
PROGRESS REPORT: progress percent:0 Preparing for Installation
PROGRESS REPORT: progress percent:100 TargetDiscovery completed.
2013-03-25 16:17:30,672 InstallationLogger INFO Going to perform
final validation of desired target
2013-03-25 16:17:30,697 InstallationLogger.sysconfig INFO Opening
keyboard device: /dev/kbd
2013-03-25 16:17:30,698 InstallationLogger.sysconfig INFO Detected
following current keyboard layout: US-English
2013-03-25 16:17:30,698 InstallationLogger.sysconfig INFO console
type: Physical Console
2013-03-25 16:17:40,684 InstallationLogger.sysconfig INFO Configuring
NIC as: none
2013-03-25 12:17:00,022 InstallationLogger INFO Installation
Device Size: 7.58gbMB
2013-03-25 12:17:00,022 InstallationLogger INFO Minimum required
size: 2.12gb
2013-03-25 12:17:00,022 InstallationLogger INFO Recommended
size: 4.12gb
2013-03-25 12:17:00,023 InstallationLogger INFO Swap type: ZVOL
2013-03-25 12:17:00,024 InstallationLogger INFO Swap size: 3.15gb
2013-03-25 12:17:00,024 InstallationLogger INFO Dump type: ZVOL
2013-03-25 12:17:00,024 InstallationLogger INFO Dump size: 807.00mb
PROGRESS REPORT: progress percent:0 Preparing for Installation
PROGRESS REPORT: progress percent:100 PrepareTransfer completed.
PROGRESS REPORT: progress percent:0 Preparing for Installation
PROGRESS REPORT: progress percent:0 Preparing for Installation
PROGRESS REPORT: progress percent:0 Preparing for Installation
PROGRESS REPORT: progress percent:1 Preparing for Installation
PROGRESS REPORT: progress percent:1 Preparing for Installation
PROGRESS REPORT: progress percent:1 Preparing for Installation
PROGRESS REPORT: progress percent:2 Preparing for Installation
PROGRESS REPORT: progress percent:2 Preparing for Installation
PROGRESS REPORT: progress percent:2 Preparing for Installation
PROGRESS REPORT: progress percent:3 Preparing for Installation
PROGRESS REPORT: progress percent:3 Preparing for Installation
PROGRESS REPORT: progress percent:3 Preparing for Installation
PROGRESS REPORT: progress percent:4 Preparing for Installation
PROGRESS REPORT: progress percent:4 Preparing for Installation
PROGRESS REPORT: progress percent:4 Preparing for Installation
PROGRESS REPORT: progress percent:5 VarSharedDataset completed.
2013-03-25 12:17:07,955 InstallationLogger ERROR cannot create
'rpool/swap': volume size must be a multiple of volume block size
2013-03-25 12:17:07,956 InstallationLogger ERROR Error occurred
during execution of 'TargetInitialization' checkpoint.
Traceback (most recent call last):
File
"/usr/lib/python2.6/vendor-packages/solaris_install/engine/__init__.py",
line 828, in _execute_checkpoints
checkpoint.execute(dry_run)
File
"/usr/lib/python2.6/vendor-packages/solaris_install/target/instantiation.py",
line 410, in execute
self.create_swap()
File
"/usr/lib/python2.6/vendor-packages/solaris_install/target/instantiation.py",
line 205, in create_swap
swap.create(self.dry_run)
File
"/usr/lib/python2.6/vendor-packages/solaris_install/target/logical.py",
line 723, in create
logger=ILN, env={"LC_ALL": "C"})
File
"/usr/lib/python2.6/vendor-packages/solaris_install/__init__.py", line
331, in check_call
raise CalledProcessError(popen.returncode, args, popen)
CalledProcessError: Command '['/usr/sbin/zfs', 'create', '-p', '-V',
'3230.54765606m', 'rpool/swap']' returned unexpected exit status 1
2013-03-25 12:17:07,970 InstallationLogger ERROR Checkpoint
TargetInitialization failed
2013-03-25 12:17:07,970 InstallationLogger ERROR Command
'['/usr/sbin/zfs', 'create', '-p', '-V', '3230.54765606m',
'rpool/swap']' returned unexpected exit status 1
2013-03-25 12:17:08,213 InstallationLogger ERROR Install FAILED.
Traceback (most recent call last):
File
"/usr/lib/python2.6/vendor-packages/solaris_install/text_install/ti_install.py",
line 336, in perform_ti_install
do_ti_install(install_data, screen, update_status_func)
File
"/usr/lib/python2.6/vendor-packages/solaris_install/text_install/ti_install.py",
line 270, in do_ti_install
raise ti_utils.InstallationError("Failed executing checkpoints")
InstallationError: Failed executing checkpoints
2013-03-25 12:17:16,549 InstallationLogger INFO User quit the
installer.
2013-03-25 12:17:16,549 Instal
Re: [OmniOS-discuss] Supermicro X9SRI-F NMI
On Mon, Mar 25, 2013 at 5:01 PM, Paul B. Henson wrote: > By default it only logs a message that it received an NMI, you need to add > "set pcplusmp:apic_panic_on_nmi=1" to /etc/system and reboot before it will > actually panic on one. I should have been more explicit-- I did have that set, but I never did find out why it wouldn't panic. It might be that on Sandy Bridge it's "apix" and not "apic" so maybe we should be setting "apix_panic_on_nmi" instead. I'm not even sure that tunable is namespaced that way... ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Highpoint 640 or 640L
On 3/25/2013 1:05 PM, Eric Sproul wrote: The other alternative is not to worry about SATA-III. A spinning hard drive can't saturate a SATA-II port as it is. Yeah, that :). The only reason SATA-III spinning rust exists is for marketing purposes and because eventually it will be cheaper to use SATA-III for everything rather than continuing to make separate SATA-II interfaces for hard disks. Unless you're planning to hook up an SSD (or one of the hybrid hard drives with a built-in SSD cache) there's really nothing gained from SATA-III. On Mon, Mar 25, 2013 at 3:54 PM, Fábio Rabelo wrote: This SI chip are SATA ll only ! My hard disks are Western Digital 4 TB sata 3 ! Are there any better option ? ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Supermicro X9SRI-F NMI
On 3/25/2013 12:45 PM, Eric Sproul wrote: Last year when I was testing KVM on a Sandy Bridge box, I was hitting https://github.com/joyent/illumos-kvm/issues/1 and trying to troubleshoot via NMI. I had the X9SRA board, which is similar to yours. I didn't have IPMI or a chassis button, so I was attempting to short the appropriate pins. I recall that I saw an NMI message on the console, but the system did not panic. By default it only logs a message that it received an NMI, you need to add "set pcplusmp:apic_panic_on_nmi=1" to /etc/system and reboot before it will actually panic on one. Thanks for the data point; I guess I'll go ahead and pop open the box and try shorting the jumpers directly to see if that behaves any differently. It will be disappointing if the ipmi interface isn't able to generate the same NMI functionality as the physical button, both from the lack of ability to do it remotely and that I'll need to get some physical button and wire it through a PCI slot blank or something 8-/. ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] changing rpool zfs properties prior to install
On 3/25/2013 12:41 PM, Eric Sproul wrote: A network install using Kayak is the best way to get what you want. The ISO installer is the most barely-functional version we could tolerate shipping, because we see network installs being the preferred method of getting bits on disk. Kayak sets compression=on by default for rpool, and can set up a mirror for you, given a suitable list of devices in the client config: http://omnios.omniti.com/wiki.php/Installation#Fromthenetwork I'm all over network installs for even medium-sized deployments :), but for the single box I'm building at the moment at home it's perhaps a touch more overhead than one would like ;). I see there's a page on the wiki talking about feeding the kayak client from a non-omnios server, maybe I'll take a shot at using some of my existing infrastructure at home to get that going. You don't happen to have a bloody equivalent to http://omnios.omniti.com/media/r151004.zfs.bz2 posted somewhere? The other (slightly (meh, considerably) more kludgy, but perhaps less effort required for a one off) option might be to pop into the shell after booting the ISO before starting the install and fiddling something (replace the zfs binary with a script that the detects rpool creation and tweaks it, start a script in the background looking for the rpool to show up and tweaking it when it does, …). Thanks much for the info. ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Highpoint 640 or 640L
Use a motherboard that has SATA-III onboard, such as recent Intel Sany Bridge and Ivy Bridge boards. Explore http://illumos.org/hcl/ for SATA-III parts. The other alternative is not to worry about SATA-III. A spinning hard drive can't saturate a SATA-II port as it is. Eric On Mon, Mar 25, 2013 at 3:54 PM, Fábio Rabelo wrote: > 2013/3/25 Eric Sproul >> >> On Mon, Mar 25, 2013 at 3:15 PM, Fábio Rabelo >> wrote: >> > Hi to all >> > >> > Someone knows if Marvel based SATA cards works ? >> > >> > http://www.highpoint-tech.com/USA_new/series_rr600-overview.htm >> > >> > Highpoint rocketraid 640L : based on Marvel 88se9235 >> > >> > Highpoint rocketraid 640 : based on masrvel 88se9128 >> >> I don't believe any Marvell 9xxx SATA chips have ever been supported >> in Solaris or any derivative. An inexpensive alternative would be >> something based on SiliconImage 3124 > > > This SI chip are SATA ll only ! > > My hard disks are Western Digital 4 TB sata 3 ! > > Are there any better option ? > > > Fábio Rabelo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Highpoint 640 or 640L
2013/3/25 Eric Sproul > On Mon, Mar 25, 2013 at 3:15 PM, Fábio Rabelo > wrote: > > Hi to all > > > > Someone knows if Marvel based SATA cards works ? > > > > http://www.highpoint-tech.com/USA_new/series_rr600-overview.htm > > > > Highpoint rocketraid 640L : based on Marvel 88se9235 > > > > Highpoint rocketraid 640 : based on masrvel 88se9128 > > I don't believe any Marvell 9xxx SATA chips have ever been supported > in Solaris or any derivative. An inexpensive alternative would be > something based on SiliconImage 3124 This SI chip are SATA ll only ! My hard disks are Western Digital 4 TB sata 3 ! Are there any better option ? Fábio Rabelo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Supermicro X9SRI-F NMI
On Mon, Mar 25, 2013 at 3:12 PM, Paul B. Henson wrote: > I've never actually tried this under OpenSolaris/illumos, but am assuming it > should work more or less the same as under Solaris 10? Has anybody tested > NMI functionality with a recent illumos and could give me at least a > starting point that it should be working :)? Last year when I was testing KVM on a Sandy Bridge box, I was hitting https://github.com/joyent/illumos-kvm/issues/1 and trying to troubleshoot via NMI. I had the X9SRA board, which is similar to yours. I didn't have IPMI or a chassis button, so I was attempting to short the appropriate pins. I recall that I saw an NMI message on the console, but the system did not panic. I would go with the assumption that it will work as it did for Solaris 10, until proven otherwise. :) Eric ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] changing rpool zfs properties prior to install
On Mon, Mar 25, 2013 at 3:17 PM, Paul B. Henson wrote: > Is there anyway to use the break out to the shell option in the installer to > go create the rpool manually, and then have the installer use it rather than > create its own? Or any other method by which you could customize zfs > properties on your rpool prior to the OS actually being installed? Paul, A network install using Kayak is the best way to get what you want. The ISO installer is the most barely-functional version we could tolerate shipping, because we see network installs being the preferred method of getting bits on disk. Kayak sets compression=on by default for rpool, and can set up a mirror for you, given a suitable list of devices in the client config: http://omnios.omniti.com/wiki.php/Installation#Fromthenetwork Eric ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] Irregularly scheduled SSD survey :)
It seems like it's been a while since there's been an SSD discussion; I'm in the market for a few and was wondering if anybody had any new favorites, or updated information about any previous candidates. I'm looking to get two of say 200G or larger, to create an rpool mirror across the first partition of each and have the second partition of each an independent L2ARC. Ideally I'd like to find a third small one with power failure protection to be a slog; if that doesn't work out I might carve out a third partition on each of the two big ones to create a slog mirror. Definitely not preferable, but it's a home server, so trade-offs might need to be made . Thanks in advance for any feedback. ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Highpoint 640 or 640L
On Mon, Mar 25, 2013 at 3:15 PM, Fábio Rabelo wrote: > Hi to all > > Someone knows if Marvel based SATA cards works ? > > http://www.highpoint-tech.com/USA_new/series_rr600-overview.htm > > Highpoint rocketraid 640L : based on Marvel 88se9235 > > Highpoint rocketraid 640 : based on masrvel 88se9128 I don't believe any Marvell 9xxx SATA chips have ever been supported in Solaris or any derivative. An inexpensive alternative would be something based on SiliconImage 3124. Eric ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] changing rpool zfs properties prior to install
Currently AFAIK there is no way to muck with the rpool during an omnios install. It's easy enough to attach another disk after the fact if you want a mirrored rpool, but I was thinking of trying out compression on my rpool, and turning that on after everything's already copied doesn't do much good :). Is there anyway to use the break out to the shell option in the installer to go create the rpool manually, and then have the installer use it rather than create its own? Or any other method by which you could customize zfs properties on your rpool prior to the OS actually being installed? Thanks… ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] Highpoint 640 or 640L
Hi to all Someone knows if Marvel based SATA cards works ? http://www.highpoint-tech.com/USA_new/series_rr600-overview.htm Highpoint rocketraid 640L : based on Marvel 88se9235 Highpoint rocketraid 640 : based on masrvel 88se9128 This cards are not for boot the system, just for zfs storage . I will put napp-it over Omni ... Thanks in advance Fábio Rabelo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] Supermicro X9SRI-F NMI
I'm building a storage server using a supermicro X9SRI-F motherboard, and I'm trying to set it up to panic on an NMI so in the (hopefully unlikely) case the server goes out to lunch at some point, I will be able to generate a crash dump and some diagnostics. Right now the box is running a test install of omnios bloody. The board has IPMI capability, and I'm running 'ipmitool -I lanplus -H host chassis power diag', which should generate an NMI. However, instead of a log message indicating an NMI has been received (I don't have the /etc/system setting in yet to actually panic), the box wedges hard and becomes completely unresponsive. The board also has an NMI header, although the chassis I have it in does not have a button to connect to it. I have not yet tried generating the NMI by shorting the jumper as opposed to via IPMI, so I'm not sure if that will do something differently. I've never actually tried this under OpenSolaris/illumos, but am assuming it should work more or less the same as under Solaris 10? Has anybody tested NMI functionality with a recent illumos and could give me at least a starting point that it should be working :)? Thanks much… ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] HCL: support Intel patsburg - C6xx - Sandy Bridge
On Mon, Mar 25, 2013 at 2:28 PM, Paul B. Henson wrote: > Joyent recommends the supermicro X9DRD-7LN4F-JBOD motherboard as one they > currently use in production, which has an C602J chipset as well as 8 SAS > ports from an LSI 2308 chipset in IT mode. I'm assuming they evaluated > compatibility fairly thoroughly :). The AHCI SATA ports should work fine, > although from what I understand the SCU SATA ports are not yet supported. That's correct, neither SCU SAS nor SCU SATA are supported. PCH/ICH SATA attach as AHCI and work just fine, as do board-level integrations like LSI SAS. On the network side, low-end Patsburg boards from Supermicro and Intel come with the 82579LM/82574L combo for dual-1G NICs, and both are supported by e1000g(7). Higher-spec boards typically include a dual I350, which is supported by igb(7). Eric ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] HCL: support Intel patsburg - C6xx - Sandy Bridge
On 3/25/2013 10:45 AM, srinivas jonn wrote: does anyone have success with running latest omniOS on Intel patsburg - ie C6xx chipset? Joyent recommends the supermicro X9DRD-7LN4F-JBOD motherboard as one they currently use in production, which has an C602J chipset as well as 8 SAS ports from an LSI 2308 chipset in IT mode. I'm assuming they evaluated compatibility fairly thoroughly :). The AHCI SATA ports should work fine, although from what I understand the SCU SATA ports are not yet supported. ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] HCL: support Intel patsburg - C6xx - Sandy Bridge
I've been running some Sandy Bridge, Intel C602-based systems in production for a few months now. No issues, but I also am also only using LSI SAS2008-based HBAs, I'm not using the SATA or SAS ports provided by the chipset. Greg Mason HPC Systems Administrator Michigan State University High Performance Computing Center web: www.hpcc.msu.edu email: gma...@msu.edu aim: gma...@msu.edu phone: (517) 353-8666 On Mar 25, 2013, at 1:45 PM, srinivas jonn wrote: > > quick question on support for Intel sandy bridge chipsets: > > does anyone have success with running latest omniOS on Intel patsburg - ie > C6xx chipset? > > success has been reported against Intel C2xx - Cougar Point. > > Nexenta fully supports these, and Oracle Solaris 11 too > > but there is no mention in the official Illumos HCL > > the "device driver utility" on OI 151-A7 reported several unknown system > devices on Xeon E5-26xx server > > mostly the CPU QPI modules were reported "unknown" - does this mean any known > limitations? > > thank you. > ___ > OmniOS-discuss mailing list > OmniOS-discuss@lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] HCL: support Intel patsburg - C6xx - Sandy Bridge
quick question on support for Intel sandy bridge chipsets: does anyone have success with running latest omniOS on Intel patsburg - ie C6xx chipset? success has been reported against Intel C2xx - Cougar Point. Nexenta fully supports these, and Oracle Solaris 11 too but there is no mention in the official Illumos HCL the "device driver utility" on OI 151-A7 reported several unknown system devices on Xeon E5-26xx server mostly the CPU QPI modules were reported "unknown" - does this mean any known limitations? thank you. ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
