Re: [OpenIndiana-discuss] Installation on HD = 2TB
On 02/ 2/13 04:47 AM, Jim Klimov wrote: Well, I'm still puzzled why OI installer and/or gparted won't show you any info about the drive This message is what he sent me a while ago: Jan 29 05:07:08 openindianadisk has 3907029168 blocks, which is too large for a 32-bit kernel ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Installation on HD = 2TB
On 2013-02-02 10:59, Udo Grabowski (IMK) wrote: On 02/ 2/13 04:47 AM, Jim Klimov wrote: Well, I'm still puzzled why OI installer and/or gparted won't show you any info about the drive This message is what he sent me a while ago: Jan 29 05:07:08 openindianadisk has 3907029168 blocks, which is too large for a 32-bit kernel Hm... makes sense... and there were discussions in the past on how to try and enforce a 64-bit kernel/userspace for the installer. Should in fact happen automatically (with $ISADIR in GRUB menu) but may fail due to misdetection on some hardware and other circumstances. Namely - did not fail for me when I was using an OI livecd to add a 3Tb HDD to a pool of an older (SXCE) server which did not fully see the disk natively - but agreed to use the GPT partitioning which I imposed with OI. I believe, the trick is to edit the GRUB menu during boot (press e) and modify the kernel and module lines to replace $ISADIR with explicit amd64, then press b to load this configuration. If this workaround is needed after installation, it may IMHO be regarded as a bug, but easily mended by editing the GRUB menu file in /rpool/boot/grub/menu.lst in a similar fashion (probably best is to clone the existing entries, to leave ones with autodetection for reference and to use ones with explicit 64-bitness). HTH, ///Jim Klimov ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Installation on HD = 2TB
On 2013-02-01 02:22, Edward Ned Harvey (openindiana) wrote: My only suggestion is to check the drive mode. I would guess you want AHCI, and I would guess it already is in AHCI mode, so I'm guessing this suggestion is no help. Or, as I suggested, check that other OSes did not layout this disk as GPT and thus clobbered it for non-GPT usage - as for installer. //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Installation on HD = 2TB
Well, I'm still puzzled why OI installer and/or gparted won't show you any info about the drive, however, your screenshot does tell a story: It seems the disk is laid out in MBR partitioning after all, however, it has all 4 primary partitions assigned (including one that holds the extended partition /dev/sda2 and a further extended /dev/sda5 in it). Since /dev/sda2 is as small as /dev/sda5 and only addresses the end of your disk, there are no more possible partitions to address the 900Gb you left for future. The solution in your case might be to extend or recreate /dev/sda2 to cover the whole space after the first 3 partitions. I am not sure however if OI/Solaris SMI label can reside in an extended partition or if it requires one of the primary ones. On 2013-02-02 04:28, Mirko Fluher wrote: On Fri, 2013-02-01 at 13:40 +0100, Jim Klimov wrote: On 2013-02-01 02:22, Edward Ned Harvey (openindiana) wrote: My only suggestion is to check the drive mode. I would guess you want AHCI, and I would guess it already is in AHCI mode, so I'm guessing this suggestion is no help. Or, as I suggested, check that other OSes did not layout this disk as GPT and thus clobbered it for non-GPT usage - as for installer. This could be where the problem is ... I didn't want to use the entire 2TB for a single system ... so I grabbed gparted and partitioned the disk with 3x 300g partitions and left the rest untouched. I then installed Linux Ubtuntu 12.10 in the first partition sda1 and Centos6.2 in the second ... which became sda3 ... sda4 is blank and was going to be for OpenIndiana ... see pics attached. When I loaded OI from liveDVD and proceeded to install, it simply could not see the HD ... the gparted on liveDVD could not see the partitions ... I have decided to just forget about 2TB HD OI..., and installed OI on a separate 500G ... happy with that. Thanks for all the replies. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Installation on HD = 2TB
On 2013-01-31 12:47, Mirko Fluher wrote: I recently tried .. to install OI 151a7 live on the following computer; cpu i7 mboard: gigabyte B75M-D3H HD: Segate SATA3 2TB with plenty of ram ... it simply wouldn't install ... it cannot see the partition .. yet on that HD I run linux Ubuntu Centos and have plenty of spare room. I then decided to use an old 250G SATA2 HD ... and no problems - same settings in the Motherboard. I'd take it, you also used the same SATA port for both drives, so that missing driver can be ruled out? My main guess would be that your other OSes mapped the disk as GPT and OI (older GRUB in particular, as well as installer and rpool support) are not yet compatible with it for a boot device (it's ok for storage pools). GPT involves a legacy MBR partition that addresses your whole disk and blocks non-GPT systems from using it and messing up. There are hacks to add either GPT support to legacy GRUB, or add an alternate MBR partition table to address the same sector ranges as GPT and thus fool an older OS into working with the disk, but these are tricks at the experimenter's risk. Alternately, you can wait for GRUB2 integration and related fixes to installer and rpool routines - or better yet, help it happen! ;) I told the installation program to use the entire HD. (snip) attached is a a dump of the output of 'gparted' as it is provided by the system. It complains about mount point ... but I assume there is a problem with gparted... I believe this problem is indeed in gparted. Seems like it was taken from a Linux/other OS source and used as is - with little integration to Solaris/ZFS realities. I'd guess it looks for the device node name in /etc/vfstab (if it's even smart enough to not use /etc/fstab as it would in many other OSes), and unable to find that match - complains. I'd say it is a cosmetical annoyance however ;) //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Installation on HD = 2TB
If you're not absolutely clear on how the partition table in the first sector on disk (aka fdisk or MBR partition) works, be very careful. You can easily trash the other installs. You're asking for an entry there to point to a Solaris partition table. I'm not current on what's going on w/ the various disk label schemes, but mostly because I avoid needing to know. That's likely to change shortly. What model disk? I'm about to do battle w/ installing OI_151a7 on 4k sector 2 TB Seagate disks in an HP N40L. You can't boot OI from disks over 2 TB as they require an EFI label. Solaris 11.1 is reported to have fixed the problem, but even the Oracle doc's have not caught up to the change. I can see the disks w/ format, but have not yet attempted to install. I ran a surface analysis first since I'm building a file server w/ 3 disks. Surface analysis on a 2 TB disk takes about 12 hours to run. Did you run format(1m) manually? I don't know what the current situation is, but years ago I installed FreeBSD, Linux Solaris on the same disk. It took probably a dozen install attempts to figure out. Ultimately I had to alter the fdisk partition type ID, install the next OS, and then change it back. There was also a particular order of install required because one of the installers was actively hostile to the others. I don't recall which though. IIRC (it was 10+ years ago) the main issue was Linux swap used the same fdisk partition ID as Solaris. After that I switched to using removable drive caddies. My current recommendation for laptops is to install to USB drives, but the 4k sector problem is making that difficult. But for a desktop system, the caddies are the way to go. Have Fun! Reg . --- On Thu, 1/31/13, Mirko Fluher m...@pax.apana.org.au wrote: From: Mirko Fluher m...@pax.apana.org.au Subject: [OpenIndiana-discuss] Installation on HD = 2TB To: openindiana-discuss@openindiana.org Date: Thursday, January 31, 2013, 5:47 AM I recently tried .. to install OI 151a7 live on the following computer; cpu i7 mboard: gigabyte B75M-D3H HD: Segate SATA3 2TB with plenty of ram ... it simply wouldn't install ... it cannot see the partition .. yet on that HD I run linux Ubuntu Centos and have plenty of spare room. I then decided to use an old 250G SATA2 HD ... and no problems - same settings in the Motherboard. I told the installation program to use the entire HD. mir@bigpax:~$ df -h Filesystem Size Used Avail Use% Mounted on rpool/ROOT/openindiana 196G 2.9G 193G 2% / swap 42G 404K 42G 1% /etc/svc/volatile /usr/lib/libc/libc_hwcap1.so.1 196G 2.9G 193G 2% /lib/libc.so.1 swap 42G 48K 42G 1% /tmp swap 42G 68K 42G 1% /var/run rpool/export 193G 32K 193G 1% /export rpool/export/home 193G 32K 193G 1% /export/home rpool/export/home/mir 193G 81M 193G 1% /export/home/mir rpool 193G 45K 193G 1% /rpool /export/home/mir 193G 81M 193G 1% /home/mir mir@bigpax:~$ attached is a a dump of the output of 'gparted' as it is provided by the system. It complains about mount point ... but I assume there is a problem with gparted... If anyone is running the above system on a 2TB HD, I would be curious to know how you did it ... ?? Cheers, -Inline Attachment Follows- ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Installation on HD = 2TB
On 01/31/13 11:02 PM, Jim Klimov wrote: On 2013-01-31 12:47, Mirko Fluher wrote: I recently tried .. to install OI 151a7 live on the following computer; cpu i7 mboard: gigabyte B75M-D3H HD: Segate SATA3 2TB with plenty of ram ... it simply wouldn't install ... it cannot see the partition .. yet on that HD I run linux Ubuntu Centos and have plenty of spare room. I then decided to use an old 250G SATA2 HD ... and no problems - same settings in the Motherboard. I'd take it, you also used the same SATA port for both drives, so that missing driver can be ruled out? same config. same hardware ... just different HD ... old 250g used to have a linux system on it. My main guess would be that your other OSes mapped the disk as GPT and OI (older GRUB in particular, as well as installer and rpool support) are not yet compatible with it for a boot device (it's ok for storage pools). GPT involves a legacy MBR partition that addresses your whole disk and blocks non-GPT systems from using it and messing up. There are hacks to add either GPT support to legacy GRUB, or add an alternate MBR partition table to address the same sector ranges as GPT and thus fool an older OS into working with the disk, but these are tricks at the experimenter's risk. Alternately, you can wait for GRUB2 integration and related fixes to installer and rpool routines - or better yet, help it happen! ;) I wish ... :) I told the installation program to use the entire HD. (snip) attached is a a dump of the output of 'gparted' as it is provided by the system. It complains about mount point ... but I assume there is a problem with gparted... I believe this problem is indeed in gparted. Seems like it was taken from a Linux/other OS source and used as is - with little integration to Solaris/ZFS realities. I'd guess it looks for the device node name in /etc/vfstab (if it's even smart enough to not use /etc/fstab as it would in many other OSes), and unable to find that match - complains. I'd say it is a cosmetical annoyance however ;) //Jim Thank you for the reply Jim. I'll just have to wait a little bit longer... Cheers, ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Installation on HD = 2TB
On 2013-01-31 13:27, Reginald Beardsley wrote: You can't boot OI from disks over 2 TB as they require an EFI label. I believe this is not technically precise. If you label a 3Tb disk with MBR, I think you can boot - but forfeit the extra terabyte of data. In some future case this might be acceptable - i.e. when a dirt-cheap replacement disk which is larger than your old one comes and is to be just plugged into a degraded pool. So you lose 1/3... well... it is cheap (i.e. in a year-two from now). //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Installation on HD = 2TB
On 01/31/13 11:27 PM, Reginald Beardsley wrote: What model disk? Seagate 2TB SATA3 I'm about to do battle w/ installing OI_151a7 on 4k sector 2 TB Seagate disks in an HP N40L. You can't boot OI from disks over 2 TB as they require an EFI label. Solaris 11.1 is reported to have fixed the problem, but even the Oracle doc's have not caught up to the change. I can see the disks w/ format, but have not yet attempted to install. I ran a surface analysis first since I'm building a file server w/ 3 disks. Surface analysis on a 2 TB disk takes about 12 hours to run. Did you run format(1m) manually? I just used the LiveDVD 'oi-dev-151a7-live' ... and it just told me it couldn't see the HD. I don't know what the current situation is, but years ago I installed FreeBSD, Linux Solaris on the same disk. It took probably a dozen install attempts to figure out. Ultimately I had to alter the fdisk partition type ID, install the next OS, and then change it back. There was also a particular order of install required because one of the installers was actively hostile to the others. I don't recall which though. IIRC (it was 10+ years ago) the main issue was Linux swap used the same fdisk partition ID as Solaris. After that I switched to using removable drive caddies. My current recommendation for laptops is to install to USB drives, but the 4k sector problem is making that difficult. But for a desktop system, the caddies are the way to go. this is basically what I am doing at the moment ... and until OI can see my 2TB and partitions ... so at the moment is OI on a good old 250g :) Cheers, ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Installation on HD = 2TB
On 02/ 1/13 12:12 AM, Edward Ned Harvey (openindiana) wrote: From: Mirko Fluher [mailto:m...@pax.apana.org.au] it simply wouldn't install ... it cannot see the partition .. yet on that HD I run linux Ubuntu Centos and have plenty of spare room. Are you trying to dual/triple boot the system? I would assume such a thing is possible, but probably very tricky, and probably very risky for trashing the other systems. Hopefully you can avoid doing that. Why not run OI as a host os, and then run the centos/ubuntu as guest OSes? (For example, VirtualBox) I CANNOT install OI on my 2TB Sata3 HD ... the liveDVD simply cannot see the HD ... :) All I can do at the moment is use OI on a smaller .. old 250G HD Cheers, ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Installation on HD = 2TB
Yes. I was still waking up. --- On Thu, 1/31/13, Jim Klimov jimkli...@cos.ru wrote: From: Jim Klimov jimkli...@cos.ru Subject: Re: [OpenIndiana-discuss] Installation on HD = 2TB To: openindiana-discuss@openindiana.org Date: Thursday, January 31, 2013, 6:34 AM On 2013-01-31 13:27, Reginald Beardsley wrote: You can't boot OI from disks over 2 TB as they require an EFI label. I believe this is not technically precise. If you label a 3Tb disk with MBR, I think you can boot - but forfeit the extra terabyte of data. In some future case this might be acceptable - i.e. when a dirt-cheap replacement disk which is larger than your old one comes and is to be just plugged into a degraded pool. So you lose 1/3... well... it is cheap (i.e. in a year-two from now). //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Installation on HD = 2TB
On 2013-01-31 14:12, Edward Ned Harvey (openindiana) wrote: From: Mirko Fluher [mailto:m...@pax.apana.org.au] it simply wouldn't install ... it cannot see the partition .. yet on that HD I run linux Ubuntu Centos and have plenty of spare room. Are you trying to dual/triple boot the system? I would assume such a thing is possible, but probably very tricky, and probably very risky for trashing the other systems. Hopefully you can avoid doing that. Why not run OI as a host os, and then run the centos/ubuntu as guest OSes? (For example, VirtualBox) This is possible (to multi-boot) - I have done that with few hiccups on a laptop with OI, Fedora, and for a while Win7 - all involving their own bootloaders. However, as for reasoning - I'd state poor hardware driver support in OI (i.e. the said laptop could not natively use USB3, WiFi, and powersave-sleeping; glitchy sound - both mic and play; multimedia playback)... At times when these were needed, there was little choice but to boot into another OS and use VirtualBox to boot OI as needed from the raw partition as a VM. And even that was unwieldy, with OI's pickiness about rpool storage device changes. //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Installation on HD = 2TB
On 31/01/2013 14:29, Mirko Fluher wrote: On 02/ 1/13 12:12 AM, Edward Ned Harvey (openindiana) wrote: From: Mirko Fluher [mailto:m...@pax.apana.org.au] it simply wouldn't install ... it cannot see the partition .. yet on that HD I run linux Ubuntu Centos and have plenty of spare room. Are you trying to dual/triple boot the system? I would assume such a thing is possible, but probably very tricky, and probably very risky for trashing the other systems. Hopefully you can avoid doing that. Why not run OI as a host os, and then run the centos/ubuntu as guest OSes? (For example, VirtualBox) I CANNOT install OI on my 2TB Sata3 HD ... the liveDVD simply cannot see the HD ... :) Be precise, the message was that the disk is too large for the live system, which is the real mystery, since that is a 2 TB disk, which should be handled even by a 32 bit system. -- Dr.Udo GrabowskiInst.f.Meteorology a.Climate Research IMK-ASF-SAT www.imk-asf.kit.edu/english/sat.php KIT - Karlsruhe Institute of Technologyhttp://www.kit.edu Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026 ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Installation on HD = 2TB
To at least summarize your problem, without all the distracting irrelevant details and tangents of the OP and this thread in general... Even if I don't have an answer for you ... When you boot the OI installer DVD, with a 2TB drive attached, OI simply cannot see the disk. When you boot the same system, with a 250G disk attached, OI installs just fine. So at least this confirms OI can use the SATA controller (or whatever). It suggests that the problem is the system can't handle drive of 2TB size... However, you can install (what did you say, centos and ubuntu?) some other OS onto the 2TB drive, just fine. So what gives? Is it a driver problem, a hardware compatibility problem, or what? And can anything be done about it? My only suggestion is to check the drive mode. I would guess you want AHCI, and I would guess it already is in AHCI mode, so I'm guessing this suggestion is no help. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Installation on HD = 2TB
(My advice, BTW, would be to try putting the 2T drive into one of the SATA 2 ports, and seeing what transpires.) - Rich On Thu, Jan 31, 2013 at 11:54 PM, Rich rerc...@acm.jhu.edu wrote: Most BIOSes really don't like trying to boot to things beyond a certain threshold into the drive [who even bothers implementing full LBA support, anyway...] Make a traditional MBR partition table and take a 100GB primary partition for root (or 64 GB or 32 or something smaller) - make it using gparted having cleared the EFI bits if necessary. I believe OI can be convinced to boot from said partition and not whole-disk, though I've not tried it. Once you're in the OS, you should be able to address the rest of the drive, though not as one contiguous storage blob [I'd bet a dollar if you tried concatenating the zpool, nothing sane would happen]. It's also possible that your problem is that the 2T drive is doing SATA 3 and something is buggy in how OI is handling the SATA 3 (whereas the 250GB drive is likely SATA 1/2). - Rich On Thu, Jan 31, 2013 at 8:22 PM, Edward Ned Harvey (openindiana) openindi...@nedharvey.com wrote: To at least summarize your problem, without all the distracting irrelevant details and tangents of the OP and this thread in general... Even if I don't have an answer for you ... When you boot the OI installer DVD, with a 2TB drive attached, OI simply cannot see the disk. When you boot the same system, with a 250G disk attached, OI installs just fine. So at least this confirms OI can use the SATA controller (or whatever). It suggests that the problem is the system can't handle drive of 2TB size... However, you can install (what did you say, centos and ubuntu?) some other OS onto the 2TB drive, just fine. So what gives? Is it a driver problem, a hardware compatibility problem, or what? And can anything be done about it? My only suggestion is to check the drive mode. I would guess you want AHCI, and I would guess it already is in AHCI mode, so I'm guessing this suggestion is no help. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
