Boot Lun size for W2012 installation

Is there a rule how big a boot lun must be for a W2012 server installation; server memory size, e.g. 64GB / 128GB / 256 GB / 512 GB
I have seen, that for a 512 GB size, a boot lun of 60GB is by far not enough.

Wont argue, taking time with customer I dont have to try and help you. Typically when the "Unable to install" message is up there its because the MS Installation CD is not currently mapped in the Virtual Media due to the Drivers CD being mapped. Map the drivers CD, install drivers for Storage->Cisco since we're using the VIC cards and booting from SAN. Once the fnic driver is installed I can see the LUN but it says cannot install to it. At this time I typically add a few more drivers to save time, like network for cisco, storage for LSI as well as chip set but you dont have to. With the error showing you go to virtual media, uncheck the map driver.iso file, check the box to map the MS installation cd/dvd again. Returning to the server installation the error still shows. At this time I now click refresh below the list of drives and once that refresh has completed the error is gone but a new one shows stating the LUN is too small and needs to be increased to 150GB. This size is because of page file required due to our memory amount, this will change based upon your memory for the blade, per microsofts documented amounts. However we still wanted 40GB for the bootable LUN so we clicked "Next" despite the error and it continues and starts the installation. This is our experiance, and at this customer site I have now done 22 servers this week, some 2008 and some are 2012 and all of them reacted the same, which is consistent with my past installs.

Similar Messages

Maximum LUN size for Windows 2012 server

Dear All
What is the Maximum size of the LUN that can be provided to windows 2012 server. Earlier it was 2 TB for windows 2008 server has the policy changed or it is still
the same.
Regards
Zubair

Hi,
Would you please let me know if your OS version is Windows Server 2012 or Windows Server 2012 Essentials? If it’s Windows Server 2012, you’d better ask the question in the File Services and
Storage forum. We will get a better assistance there.
File Services and Storage
http://social.technet.microsoft.com/Forums/en-US/winserverfiles/threads
Best Regards,
Andy Qi
Andy Qi
TechNet Community Support

Maximun LUN size for non-MAC SAN

Hi.
I am trying to configure a PPC Mac Xserve to utilize storage space on a non-mac SAN (Compellent). I successfully setup the original volume on the SAN as a 2TB volume, zoned it through the Qlogic switch and mounted it on the Xserve.
Now I need to increase the size of that volume to 3TB. I unmounted the volume on the Xserve, deleted and recreated it on the SAN, and then tried remounting it on the Xserve. The Xserve detects the new volume, but only sees 2TB of space. No matter what I do, I cannot get it to see anything more than 2TB.
I thought the 10.4.10 FS (HFS+ Journaled) could see well over 2TB? Is there a LUN limitation? The only reference to this that I saw, was a limitation with older versions of the XSAN software.
Thank you.
Tim

Hi Tim,
I am looking in to this also Take a look at this
http://discussions.apple.com/thread.jspa?messageID=5517350&#5517350
I haven't had a chance to test this. I'd be interested to hear if it is successful for you.

Boot camp asking for windows installer update

I cannot load the osx dvd because it prompts me to update my windows installer. You can click no or update. No closes the whole thing and update gives me an error. Anyone able to help?

Hi afrobat,
you probably need something like this (download from net).
For winXP 32bit ="WindowsXP-KB942288-v3-x86.exe"
for win7 32+64bit ="Windows6.0-KB942288-v2-x86.msu"
"Windows6.0-KB942288-v2-x64.msu"
These are windows applications so install with-in winOS.
They are "Windows Installer 4.5"

Lun Size best practice for UC apps and VMWare?

Hi,
We have UCS manager v2.1 with FI 6248 direct FC attached to NetApp with plenty of storage.
Per following doc, Lun size for UC apps should be 500GB - 1.5TB and 4 to 8 VMs per Lun.
http://docwiki.cisco.com/wiki/UC_Virtualization_Storage_System_Design_Requirements#Best_Practices_for_Storage_Array_LUNs_for_Unified_Communications_Applications
We have four B200M3 blades and 3 to 4 UC apps (CUCM, Unity, UCCX) will be hosted on each blade. May add more VM the blades in the future.
I am thinking four 1 TB Luns and one for each blades. (actually 8 Luns in toal, 4 boot luns for ESXi and 4 for UC apps).
What is the best practice (or common deployment) to create Lun size and design?
Thanks,
Harry

UC apps need low IO，nothing special，Reference vmware LUN design is ok.

[Solved] Boot process hangs for installed Arch and installation usb

Hi. I've been using Arch Linux for around 6 months now and I'm in love with it. It is now my primary OS. However, I might have done something or performed some update, and I can no longer boot into Arch. The boot process hangs right before it should show the login screen (I'm using Gnome 3.6 with GDM). I see the following messages on the screen:
Loading Linux core repo kernel ...
Loading initial ramdisk ...
/dev/sda3: recovering journal
/dev/sda3: clean, 330610/1749664 files, 5585671/6996827 blocks
And then it hangs right there. I have to hard-reboot after this.
I then tried to boot using the Arch Linux Installation USB (archlinux-2012.12.01-dual.img), which also hangs at a particular point, before it should show me the prompt. I took a picture of the screen where it hangs: Screen Capture. This is an issue with just my laptop, because the USB boots just fine on another laptop I tried.
I also have Windows 7 and Ubuntu 12.10 installed on my system, and I'm able to boot into both of them.
I have 2 hard drives: /dev/sda is a 120GB SSD, and /dev/sdb is a 500GB hard disk. My partitions are as follows:
sda1 - Windows 7 100MB System Reserved Partition (boot flag enabled)
sda2 - Windows 7 OS
sda3 - ArchLinux (boot flag enabled)
sdb1 - Ubuntu 12.10 (boot flag enabled)
sdb2 - Just data
I ran bootinfoscript and below is the output:
Boot Info Script 0.61 [1 April 2012]
============================= Boot Info Summary: ===============================
=> Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
in partition 99 for .
=> Grub2 (v1.99) is installed in the MBR of /dev/sdb and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
in partition 99 for .
sda1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Boot/BCD
sda2: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows 7
Boot files: /Windows/System32/winload.exe
sda3: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Mounting failed: mount: /dev/sda3 already mounted or sda3 busy
sdb1: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 12.10
Boot files: /boot/grub/grub.cfg /etc/fstab
sdb2: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
============================ Drive/Partition Info: =============================
Drive: sda _____________________________________________________________________
Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 * 2,048 206,847 204,800 7 NTFS / exFAT / HPFS
/dev/sda2 206,848 178,466,084 178,259,237 7 NTFS / exFAT / HPFS
/dev/sda3 * 178,466,085 234,440,703 55,974,619 83 Linux
Drive: sdb _____________________________________________________________________
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sdb1 * 63 20,948,759 20,948,697 83 Linux
/dev/sdb2 20,964,824 976,771,071 955,806,248 7 NTFS / exFAT / HPFS
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/mmcblk0p1 6665-3162 vfat
/dev/sda1 CA6A20CC6A20B75B ntfs System Reserved
/dev/sda2 1EE242D5E242B137 ntfs
/dev/sda3 65db0c59-9f04-46f1-975d-8a4c28132137 ext4
/dev/sdb1 bb9818db-ce7c-43a4-8ad5-8d3702001aed ext4
/dev/sdb2 3C2E3A4E2E3A0206 ntfs
================================ Mount points: =================================
Device Mount_Point Type Options
/dev/mmcblk0p1 /media/dhaval/6665-3162 vfat (rw,nosuid,nodev,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush,uhelper=udisks2)
/dev/sdb1 / ext4 (rw,errors=remount-ro)
=========================== sdb1/boot/grub/grub.cfg: ===========================
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
set default="0"
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function recordfail {
set recordfail=1
if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
if background_color 13,37,73; then
clear
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
if [ "${1}" = "keep" ]; then
set vt_handoff=vt.handoff=7
else
set vt_handoff=
fi
if [ "${recordfail}" != 1 ]; then
if [ -e ${prefix}/gfxblacklist.txt ]; then
if hwmatch ${prefix}/gfxblacklist.txt 3; then
if [ ${match} = 0 ]; then
set linux_gfx_mode=keep
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=keep
fi
else
set linux_gfx_mode=text
fi
export linux_gfx_mode
if [ "${linux_gfx_mode}" != "text" ]; then load_video; fi
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
recordfail
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
linux /boot/vmlinuz-3.5.0-21-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro quiet splash acpi_osi=Linux acpi_backlight=vendor $vt_handoff
initrd /boot/initrd.img-3.5.0-21-generic
submenu 'Advanced options for Ubuntu' $menuentry_id_option 'gnulinux-advanced-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
menuentry 'Ubuntu, with Linux 3.5.0-21-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.5.0-21-generic-advanced-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
recordfail
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
echo 'Loading Linux 3.5.0-21-generic ...'
linux /boot/vmlinuz-3.5.0-21-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro quiet splash acpi_osi=Linux acpi_backlight=vendor $vt_handoff
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.5.0-21-generic
menuentry 'Ubuntu, with Linux 3.5.0-21-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.5.0-21-generic-recovery-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
echo 'Loading Linux 3.5.0-21-generic ...'
linux /boot/vmlinuz-3.5.0-21-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.5.0-21-generic
menuentry 'Ubuntu, with Linux 3.2.0-29-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.2.0-29-generic-advanced-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
recordfail
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
echo 'Loading Linux 3.2.0-29-generic ...'
linux /boot/vmlinuz-3.2.0-29-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro quiet splash acpi_osi=Linux acpi_backlight=vendor $vt_handoff
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-29-generic
menuentry 'Ubuntu, with Linux 3.2.0-29-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.2.0-29-generic-recovery-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
echo 'Loading Linux 3.2.0-29-generic ...'
linux /boot/vmlinuz-3.2.0-29-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-29-generic
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
linux16 /boot/memtest86+.bin
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 7 (loader) (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-CA6A20CC6A20B75B' {
insmod part_msdos
insmod ntfs
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 CA6A20CC6A20B75B
else
search --no-floppy --fs-uuid --set=root CA6A20CC6A20B75B
fi
chainloader +1
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
=============================== sdb1/etc/fstab: ================================
# /etc/fstab: static file system information.
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sdb1 during installation
UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed / ext4 errors=remount-ro 0 1
=================== sdb1: Location of files loaded by Grub: ====================
GiB - GB File Fragment(s)
4.564525127 = 4.901121536 boot/grub/grub.cfg 1
5.130507946 = 5.508840960 boot/initrd.img-3.2.0-29-generic 2
5.851592541 = 6.283099648 boot/initrd.img-3.5.0-21-generic 2
6.317649364 = 6.783524352 boot/vmlinuz-3.2.0-29-generic 1
4.965751171 = 5.331934720 boot/vmlinuz-3.5.0-21-generic 2
5.851592541 = 6.283099648 initrd.img 2
5.851592541 = 6.283099648 initrd.img.old 2
4.965751171 = 5.331934720 vmlinuz 2
4.965751171 = 5.331934720 vmlinuz.old 2
I tried adding nomodeset and acpi=off to the boot parameters, but the boot process still hangs. Please let me know if I should provide any other information.
Last edited by dhavalparmar (2012-12-30 11:45:25)

Ok.. So my Arch Linux randomly decided to work. I'm sure I didn't do anything between my last "not working" state and my current "working" state. Below are a few things I tried:
I thought of trying an earlier build of ArchLinux, and downloaded archlinux-2012.11.01-dual.iso and made a bootable USB out of it. It still hung.
I was getting error messages during Arch boot that the last access time for the disks was at a future date. I found out that Ubuntu was using localtime instead of UTC and screwing up my hardware clock. I fixed it, and thought maybe the time issues were causing the boot problem. But fixing time didn't solve my problem.
I chrooted into Arch from my Ubuntu install, ran 'sudo pacman -Syyu' and updated my Arch install.
I thought maybe GDM isn't starting up. I re-enabled the service using 'systemctl enable gdm.service'.
I removed OpenNTPd and installed NTPd. Enabled the daemon using 'systemctl enable ntpd'
None of the above solved the problem, and rebooting to Arch still hung the system. So I stopped fiddling with it yesterday. Today, as usual, I just tried logging into Arch.. And it just worked out of the blue. The solution to me is as mysterious as the problem.
I told this to my friend who introduced me to Arch, and this is what he said:
Damn it computers, you were supposed to be deterministic!

1) How to Boot from SAN for T4-1 Server with Solaris 11.1 OS on the disk? 2) How to SMI Label/Format a disk while OS Installation in Solaris 11.1?

FYI....boot from SAN is required for physical server (T4-1) (not OVM).
1) How to Boot from SAN for T4-1 Server with Solaris 11.1 OS on the disk?
The SAN disks allocated are visible in ok prompt. below is the output.
(0) ok show—disks
a) /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0, 2/hub@2/hub@3/storage@2/disk
b) /pci@400/pci@2/pci@0/pci€a/SUNW, ezalxs@0, l/fp@0, 0/disk
e) /pci@400/pci@2/pci@0/pci@a/SUNW, ealxs@0/fp@0, 0/disk
d) /pci@400/pci@2/pci@0/pci@8/SUNW, emlxs@0, l/fp@0, 0/disk
e) /pci@400/pci@2/pci@0/pci@8/SUNW,enlxs@0/fp@0,0/disk
f) /pci@400/pci@2/pci@0/pci@4/scsi@0/disk
g) /pci@400/pci@1/pci@0/pci@4/scsi@0/disk
h) /iscsi—hba/disk
q) NO SELECTION
valid choice: a. . .h, q to quit c
/pci@400/pci@2/pci@0/pci@a/SUNW, ealxs@0/fp@0, 0/disk has been selected.
Type “Y ( Control—Y ) to insert it in the command line.
e.g. ok nvalias mydev “Y
for creating devalias mydev for /pci@400/pci@2/pci@0/pci@a/SUNW,emlxs@0/fp@0,0/disk
(0) ok set—sfs—boot
set—sfs—boot ?
We tried selecting a disk and applying sfs-boot at ok prompt.
Can you please help me providing detailed pre-requesites/steps/procedure to implement this and to start boot from SAN.
2) How to SMI Label/Format a disk while OS Installation in Solaris 11.1?
As we know that ZFS is the default filesystem in Solaris 11.
We have seen in the Oracle documentation that for rpool below are recommended:
- A disk that is intended for a ZFS root pool must be created with an SMI label, not an EFI label.
- Create root pools with slices by using the s* identifier.
- ZFS applies an EFI label when you create a storage pool with whole disks.
- In general, you should create a disk slice with the bulk of disk space in slice 0.
I have seen the solution that using format -e, we change the labelling but all the data will be lost, whats the way to apply a SMI Label/Format on a rpool disks while OS Installation itself.
Please provide me the steps to SMI Label a disk while installaing Solaris 11.1 OS.

Oracle recommends below things on rpool: (thats reason wanted to apply SMI Label)
I have seen in the Oracle documentation that for rpool below are recommended:
- A disk that is intended for a ZFS root pool must be created with an SMI label, not an EFI label.
- Create root pools with slices by using the s* identifier.
- ZFS applies an EFI label when you create a storage pool with whole disks.
- In general, you should create a disk slice with the bulk of disk space in slice 0.

Recommended Boot Camp Partition Size for Windows XP

All,
What size is recommended for a Windows XP Boot Camp Partition? 100Gb? 50Gb?
Main use is to run a few programs that are not available for Mac. Most everything else will be transferred over.
Thanks
PAX
JD

Kalebd wrote:
All,
What size is recommended for a Windows XP Boot Camp Partition? 100Gb? 50Gb?
Main use is to run a few programs that are not available for Mac. Most everything else will be transferred over.
Depending on the programs you want to install, you can get by with very little. I have virtual XP systems that live within 8GB virtual disks. If you've got the drive space, go for ~30GB. I've found that to be a nice size for running Windows 7 within, and thus you likely won't have to mess with re-partitioning should you update the OS in the future.

Best size for SSD boot drive?

Hi,
I am looking to replace my optical drive from my iMac 27" with an SSD to be used as a boot drive and to hold my applications for faster loading etc..
I was wandering what would be the best size for a boot drive so that I dont overspend as SSD's are expenive.
Thanks for any help in advance.

The best size is the size you need to store OS X and your apps without getting the SSD full. For example, if OS X and your apps take less than 100 GB, you should consider a 128 GB SSD, and if they take 150 GB, go for a 256 GB SSD.
You can buy the SSD at OWC to guarantee the compatibility > http://eshop.macsales.com/shop/SSD/OWC/

HT4818 What is the best Partition size for a windows 7 Home Premium. I'm trying to install Windows using Boot camp

What is the best Partition size for a windows 7 Home Premium. I'm trying to install Windows using Boot camp

Go into your system preferences and click the startup disk icon then select your Mac HD.

[Solved]Right size for /boot

Which is, in your opinion, the right size for a /boot partition? Some guides suggest 50-100Mb, other 10Gb!
Who's right?
Last edited by frazar0 (2011-07-17 17:03:10)

Mine is 32MB; half used, half empty:
$ du -sh /boot/*
285K /boot/grub
8.6M /boot/kernel26-fallback.img
1.8M /boot/kernel26.img
163K /boot/memtest86+
1.3M /boot/System.map26
2.2M /boot/vmlinuz26
Last edited by lolilolicon (2011-07-17 15:10:00)

Have a mac book pro that crashed. ran disk utility to repair. comp booted and ran for short time. then crashed. ran repair again. disk utility said it could not repair files and i needed to format hard drive and start again. now nothing works

have a mac book pro that crashed. ran disk utility to repair. comp booted and ran for short time. then crashed. ran repair again. disk utility said it could not repair disk and needed to format and start again.
comp said it could not unmount disk and now when comp trys to boot all i get is a question mark on the screen. help

Erase and Install
1. Boot from your Snow Leopard Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed.
4. Quit DU after formatting completes and return to the installer. Install Snow Leopard.
5. After restart into Snow Leopard download and install Mac OS X 10.6.8 Update Combo v1.1.

The boot configuration data for your Pc is missing or contains errors: error code 0x000014c

Hello,
See if any body may help here... I get this blue screen:
RECOVERY
Your PC needs to be repaired:
The Boot Configuration Data for your PC is missing or contains errors.
file:\\EFI\Microsoft\Boot\BCD
Error code: 0xc000014c
You'll need to use the recovery tools on your installation media. If you don't have any installation media (like a a disc or USB device), contact your system administrator or PC manufacturer.
Press Esc for UEFI Firmware Settings
First I was able to get into the option 11 and run the whole factory reset, i was so happy because I tought it will be easy.. but then after I did the factory reset.. I keep getting this blue screen. if I press ESC I get into this next screen:
F1 System Information
F2 System Diagnostics
F9 Boot Device Options
F10 BIOS Setup
F11 System Recovery
ENTER - Continue Startup.
this is what happen when I click any of this options:
F1 I get into the System Information with no problems, then I click <ESC> to continue and get back to the last screen... then I press F2 and super, I am able to run Memory Test and Hard Drive Check 100% with no problems in any of those, after I am done with my teste I press exit and I am back to the F1,F2, ETC menu... now I want to try F9, F10 or F11. bummer.. in this 3 options I get back to the blue screen described at the beggining of this post. (I already connect a USB with an boot loader, which works perfectly)
so I can't do anything, nothing at all!! crazzines.
So what I did to check why I can't get into the BIOS or at least to boot from my USB... I removed the botton cover of my laptop and removed the hard drive and that's how then I was or I am able to Log into the BIOS, - I did the changes to boot first from the USB and then from the HD and this is how I was able to boot from the USB - BUT If I connect back the Hard drive, I am not able to get into the BIOS or boot from the USB - so basically I am stuck in this blue screen and I can't boot from a USB if I have the HD connected.. I can't use any option.. no BIOS, nothing.. only if again, i disconnect the HD.
This is an:
HP ENVY TS Sleekbook 4
PRODUCT NUMBER D1A99UA#ABA
SYSTEM BOARD ID: 1894
Bios F.25
**** I though that by updating the BIOS I may be able to get help, nothing. What I did is, I removed the HD and then and boot from the USB and with a DOS command propmt I excecuted the Bios Update from F.21 to f.25... but again, when I installed the hard drive back, BUMMER, nothing I can't do nothing but this silly blue screen.
Any idea of what should I do?
Thanks in advance.
This question was solved.
View Solution.

If you can't access BIOS with the hard disk connected, you certainly won't be able to boot to the usb recovery flashdrive. That is indicative of a failed hard disk.
Install a new hard disk and then boot to the recovery flashdrive.
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

Temporary wim-files for multicast transmissions still needed for WDS installation in Server 2012 R2?

Acording to
https://technet.microsoft.com/en-us/library/dn281955.aspx one of the new features for WDS in Server 2012 R2 for multicast is:
Improved multicast deployment by eliminating the need for making a local copy of the install.wim file. You can apply the install.wim file while it is being downloaded without significant impact to the application process.
However, this doesn't seem to be activated by default and I still get the following error when installing one or more machines using multicast:
"Windows Setup cannot locate a valid hard drive to store temporary installation files." However, once I remove Multicast from this install image, it installs without any problems at all.
I have also noticed that while multicasting, the installation will use the "Copying Windows files" phase, while downloading and copying the install.wim (or whatever name it is) locally on the hard drive first, so this will require lots of space.
So the question is, how do you enable this new feature that should be a part of WDS in Server 2012 R2???

Full version:
Following steps could help enable the feature:
1. Mount the boot image using dism.
e.g.
>dism /mount-wim /wimfile:c:\remoteinstall\boot\x64\images\boot.wim /index:2 /mountdir:c:\mount
2. Create a metadata file if no existing one. The metadata file should be in mountdir from the first step under mountdir\sources. And the file name should be: WdsClientMetadata.txt
3. Add entry to the metadata file: WDS.Client.Multicast.WIM.Streaming.Enabled=true
4. Save changes and unmount the boot image
e.g.
>dism /unmounts-wim /mountdir:c:\mount /commit
Sorry for the late reply, but I had to test this thoroughly since I didn't get it working right away. I tried both the regedit you first mentioned, and later also creating a textfile in the "/index:2 boot.wim", both without any success. I noticed
that creating the sources\WdsClientMetadata.txt with the data "WDS.Client.Multicast.WIM.Streaming.Enabled=true" gives me an error upon booting into WDS as follows (EUFI/IPv6-boot):
Same happens if I boot using IPv4 (an non-UEFI boot), except that there would be a plain IPv4-address instead in the error msg. Just for troubleshooting I tried writing WDS.Client.Multicast.WIM.Streaming.Enabled=false in the file instead, and WDS would throw
me the exact same error message. Once I delete the file sources\WdsClientMetadata.txt from the WDS/Boot image, the client boots ok, both for IPv4/IPv6. Disabling the firewall on the WDS didn't help, so something in the configuration is still missing? I'm getting
to a dead end here, and I suppose you're all out of advice on this one?
Thank you Shaon Shan for your great effort so far.

Unable to boot from OSX 10.6 installation DVD to run Disk Repair

Hello all,
I have something that is puzzling me. My MacBook Pro hasn't been giving me the best experience lately - the system just seems... slow.
So I ran a disk permissions fix and it found some errors which I repaired. Then, I thought it might be wise to run a disk check on the System Disk as well.
So I attempted to boot from the Mac OSX installation DVD - I tried both a "hold the "C" key" method as well as the "Set start-up disk preferences to boot from DVD" method. I even tried two different OSX installation DVD's in case one wasn't working.
Then, I reset PRAM and I reset SMC (or at least followed the procedure as outlined by Apple - it doesn't really seem to give a strong indication of whether the process occurred or not)
I just cannot get the system to boot from DVD. (I even tried TechTools Pro 5).
I even let it "sit" for more than 4 hours in case it was just taking it's time.
Can anyone think of what the deal might be? I'm REALLY wanting to run a System Disk check now!

Ta-Da! Worked!
You learn something new every day here! I had no idea that I couldn't boot from a standard OSX boot disk and had to use the in-box one.
It does raise the question of which version of Disk Check I will be using - as there has been several upgraded to my OS since I bought this MacBook Pro (it has 10.6.3)
THANKS! I really appreciate the help - now I can check the disk.

Boot Lun size for W2012 installation

Similar Messages

Maybe you are looking for