Installation of Solaris 10 fails at booting kernal

Booting kernal/unix...
SunOS Release 5.10 Version Generic 32-bit
Copyright 1983-2005 Sun Mircosystems, Inc. All rights reserved.
Use is subject to license terms.
Nothing happens for a minute or so, then the following appears.
WARNING: /pci@0,0/pci-ide@7,1/ide@1 (ata1): timeout: abort request, target=0 lun=0
WARNING: /pci@0,0/pci-ide@7,1/ide@1 (ata1): timeout: abort request, target=0 lun=0
WARNING: /pci@0,0/pci-ide@7,1/ide@1 (ata1): timeout: abort request, target=0 lun=0
WARNING: /pci@0,0/pci-ide@7,1/ide@1 (ata1): timeout: abort request, target=0 lun=0
This happens on each of the 4 boot options. I'm booting from a DVD
My PC is a Pentium 3 800 with 256Mb Ram.
Any idea what the cause is?
thanks

The Solaris IDE/ATAPI kernel module has problems accessing
your ATAPI CD/DVD device.
Solaris 10 x86 currently has DMA disabled for ATAPI CD/DVD
devices. Maybe it works better if you enable DMA on the CD/DVD?
Try to change the "atapi-cd-dma-enabled" property to "1", on the
last DCA "select boot device" screen, in the edit properties submenu.
You probably have to press the "ESC" key to interrupt the cdrom
autoboot, to enter the DCA.

Similar Messages

Solaris 10u6 fails to boot after installation on HP Proliant DL380 G4

Hello,
I have used Solaris 10u5 without issues on the HP DL380 G4. However, when I tried to install update 6 (new installation), it fails to reboot. I starts to boot, then aborts and reboots the system. I added the arguments -av to help get more information. Here's what I was able to capture:
Enter default directory for modules [platform/i86pc/kernel /kernel /usr/kernel]:
module /platform/i86pc/kernel/amd64/unix: text at [0xfffffffffb800000, 0xfffffffffb8d5f0f] data at 0xfffffffffbc00000
module misc/amd64/krtld: text at [0xfffffffffb8d5f10, 0xfffffffffb90a89f] data at 0xfffffffffbc74ce0
module /kernel/amd64/genunix: text at [0xfffffffffb90a8a0, 0xfffffffffbb04f4f] data at 0xfffffffffbc7ee00
Name of system file [etc/system]:
SunOS Release 5.10 Version Generic_137138-09 64-bit
Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
features: 14dffdf<cpuid,mwait,cx16,sse3,asysc,htt,sse2,sse,sep,pat,cx8,pae,mca,mmx,cmov,pge,mtrr,msr,tsc,lgpg>
mem = 6225476K (0x17bf91000)
root nexus = i86pc
pseudo0 at root
pseudo0 is /pseudo
scsi_vhci0 at root
scsi_vhci0 is /scsi_vhci
isa0 at root
psuedo-device ppm0
ppm0 is /pseudo/ppm@0
npe0 at root: space 0 offset 0
npe0 is /pci@0,0
pcie_pci0 is /pci@0,0/pci8086,3595@2
PCIE-device: pci8086,32a@0,2, pcie_pci3
pcie_pcie3 is /pci@0,0/pci8086,3595@2/pci8086,32a@0,2
NOTICE:
* This device is not bootable! *
* It is either offlined or detached or faulted. *
* Please try to boot from a different device. *
NOTICE:
spa_import_rootpool: error 22
panic[cpu0]/thread=fffffffffbc26ba0: cannot mount root path /pci@0,0/pci8086,3595@2/pci8086,32a@0/pcie11,4091@3/sd@0,0:a /pci@0,0/pci8086
,3595@2/pci8086,32a@0,2/pcie11,4091@3/sd@1,0:a
fffffffffbc49320 genunix:rootconf+114 ()
fffffffffbc49350 genunix:vfs_mountroot+61 ()
I have tried this on two identical machines with the same results. Some other details:
- Booting into failsafe mode works; the system finds and mounts the zfs volumes
- I did a network installation. I rebuilt the miniroot to include the CPQary3 package
- I tried installing with a zpool with two disks as well as only one disk; the result was the same
- I also tried installing without using a ZFS root disk; it also fails
I have googled for this problem but have not found anything like it. I would greatly appreciate any help!
Thanks,
Michael

I finally figured it out. For some reason, the installer does not install the driver package (CPQary3) or include it in the boot archive. The driver is in the fail-safe miniroot, however. So, I booted into fail-safe mode and installed the driver, and now everything works!
I ran into two problems with the installer on this hardware. I'll post details and work-arounds for both in a separate message.

Installation of Solaris 10 fails on Desktop

Hi All,
I just downloaded the DVD iso image for Solaris 10 for the intel desktop and tried installing.
On my first attempt it was complaining about insufficient size to load module, but I later realised that the installation was corrupt so I re-downloaded and
verified chksum.
This time, the installation went through and went to the last stage where it rebooted, then I removed the DVD and it tried to boot from the Harddisk and comes up with the
boot screen having 2 options - Solaris 10 ........ & Solaris failsafe. I let the default option go through...
On that it fails with the following message:
boot: cannot find /misc/amd64/krtld
boot: error loading interpreter (misc/amd64/krtld)
Elf64 read error.
panic: no entry point in kernel/amd64/unix
Press any key to reboot
I'm not sure what went wrong, I just did the full installs + OEM and removed only the PostgreSQL as I didn't want that application.
Following are my system specs -
Intel Q6600
Gigabyte GA-X38-DQ6 - intel X38 board
4GB (2x2GB) + 2GB(1x2GB) = 6GB of Corsair RAM
Gigabyte nVidia 8800GTX Video card
Asus DVD drive
160GB harddrive
During the install I setup the HDD as
/ -40GB
swap - 4GB
/opt - 80GB
/export/home - 20GB
Would appreciate any help...

Solved this issue....
I reinstalled and changed the following - not sure which fixed the issue -
The install which I did was Localised to Australia and had also applied Australian posix, I changed to English posix in new install.
I have a 160GB drive, on the disk screen Solaris install shows total disk size 156117M and assigned is 156118 which is 1M more than available.
Not sure how this happened, but it's the default screen which comes up on install, I change the values and then defined the drive structure before install.
Works now.

Simple Portal Installation on Solaris 9 fails

Simple installation with no existing Directory Server fails on Solaris 9 with Java problems. The LDAP Server is running and seems to be configured correctly.
Any hints??
Setup
/var/sadm/install/logs/pssetup.4359/tmp/response/jdk
BASEDIR=/opt
IDSAME_BASEDIR=/opt
JDK_PATH=/usr/java_1.3.1_04
/var/sadm/install/logs/pssetup.4359/tmp/response/ds
ADMINPASSWD=********
BASEDIR=/opt
DIRMGRDN=cn=Directory Manager
DIRMGRPASSWD=********
DOMAIN=rz.uni.de
DS_ADMIN=admin
DS_ADMINPORT=8900
DS_HOST=couch.rz.uni.de
DS_HOSTNAME=couch
DS_PORT=389
EXISTING_DIT_SCHEMA=n
LDAPDIR=/usr/ldap
NEW_GROUP=bin
NEW_OWNER=root
ROOT_SUFFIX=o=isp
SERVER_HOST=couch.rz.uni.de
SERVER_PORT=80
SUBDOMAIN=
SUPERADMIN=amadmin
In the setup.log there are the following messages after the part in which all Services and Schema definitions are stored in LDAP (they are there, definitely).
adding new entry cn=iPlanetAMWebAgentServicePolicy,o=rz.uni.de,o=isp
Create DIT succeed
removing ldif files ..
Loading service schema XML files ...
Got LDAPServiceException code=-1
          at java.lang.Throwable.fillInStackTrace(Native Method)
          at java.lang.Throwable.fillInStackTrace(Compiled Code)
          at java.lang.Throwable.<init>(Compiled Code)
          at java.lang.Exception.<init>(Compiled Code)
          at com.iplanet.services.ldap.LDAPServiceException.<init>(LDAPServiceException.java:178)
          at com.iplanet.services.ldap.DSConfigMgr.getConnection(DSConfigMgr.java:229)
          at com.iplanet.services.ldap.DSConfigMgr.getNewFailoverConnection(DSConfigMgr.java:198)
          at com.iplanet.services.ldap.DSConfigMgr.getNewConnection(DSConfigMgr.java:138)
          at com.iplanet.services.ldap.DSConfigMgr.getNewProxyConnection(DSConfigMgr.java:76)
          at com.iplanet.services.ldap.DSConfigMgr.getNewProxyConnection(DSConfigMgr.java:86)
          at com.iplanet.ums.DataLayer.initLdapPool(DataLayer.java:949)
          at com.iplanet.ums.DataLayer.<init>(DataLayer.java:108)
          at com.iplanet.ums.DataLayer.getInstance(DataLayer.java:132)
          at com.iplanet.sm.SMSEntry.<clinit>(SMSEntry.java:77)
          at com.iplanet.sm.ServiceManager.<clinit>(Compiled Code)
          at com.iplanet.am.admin.cli.Main.registerServiceSchema(Main.java:565)
          at com.iplanet.am.admin.cli.Main.runCommand(Compiled Code)
          at com.iplanet.am.admin.cli.Main.main(Main.java:480)
Error 10: Cannot process requests:
Error 11: Cannot load service schema:
Message:Configuration Manager error: {0}

Also Guten Tag,
and thank you for the hint! I am sorry, I forgot to post the solution we found to the problem. It was a mistake during the installation process, in which a passphrase with various words, instead of a password was entered. Therefore the DSAME component could not bind succesfully to the Directory Server (err=49). It is now running without problems.
Martin

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.

Arch fails to boot after installation (BIOS mode)

I finished my Arch installation, following the Beginner's Guide, and once I unmounted the partitions and rebooted, GRUB failed to boot into Arch. I'm not exactly sure what the problem is though. Basically what happens is I power on the machine, the Dell splash screen comes up, GRUB loads, I choose
Arch Linux, with Linux core repo kernel
the kernel and ramdisk attempt to load, then some message about "recovering journal" appears, and then I return back to the Dell splash screen. The same thing happens even if I choose the second option
Arch Linux, with Linux core repo kernel (Fallback initramfs)
However, when I choose to boot Win XP everything boots just fine. My apologies for the quality of the videos and pictures.
Here's a video of what happens:
http://youtu.be/uC96kX6iTjI
I suspect this has to do with this error I got when I generated the "grub.cfg". Although I'm not entirely sure because my understanding is that this error would affect booting Win XP which in fact boots perfectly fine.
Error (and no I'm not using any lvm volumes)
http://imgur.com/qqxpoGG
I believe these are the portions of the "grub.cfg" that load Arch and Win XP. I got these by pressing "e" while on their menu entry in the GRUB bootloader.
Arch (I had to scroll down to see the rest, hence two pictures)
http://imgur.com/79dBw2C
http://imgur.com/qusEfL0
Win XP
http://imgur.com/oLnLlT0
Any idea how I can fix this? Any help is greatly appreciated and please be patient, I know, I'm a noob.
* I'm not sure if this is of any significance but I had a problem very similar to this when trying to get the Arch install to boot via usb (this computer doesn't have CD/DVD drive). I solved it by following this excerpt from the Beginner's Guide.
Troubleshooting boot problems
If you are using an Intel video chipset and the screen goes blank during the boot process, the problem is likely an issue with Kernel Mode Setting. A possible workaround may be achieved by rebooting and pressing
e
over the entry that you are trying to boot (i686 or x86_64). At the end of the string type
nomodeset
and press
Enter
Here's a video of what it looked like:
http://youtu.be/vXRcbU0zdto
The computer specs:
OS: Windows XP Professional 32 bit Version 2002 Service Pack 3
CPU: Intel Pentium 4 @ 3.00 GHz
RAM: 2 GB DDR2
HDD: 80 GB

Hi,
why did you not try adding nomodeset with the regular boot? During the net-install no video drivers will be installed;
you have to install them after reboot after installing xorg. The (video)problem you had with booting from usb is still
present.

11gR2 installation on Solaris failed with prereuisite 124861-15

The 11gR2 installation on Solaris 10 sparc failed with prereuisite 124861-15.
When I tried to install the patch 124861-20, it failed with the following(see below):
I have Sun Studio 12-2 installed on the system.
It was complaining that some packages (SPROmrcom, SPROlangx, SPROlang,SPROsunms ) are not installed.
Where can I get these packages? Should not it be included in the Sun Studio 12-2 installation?
Thanks.
Zhigang
# patchadd 124861-20
Validating patches...
Loading patches installed on the system...
Cannot find package name, arch or version in pkginfo file /var/sadm/pkg/IR/pkginfo.
Done!
Loading patches requested to install.
Done!
The following requested patches have packages not installed on the system
Package SPROmrcom from directory SPROmrcom in patch 124861-20 is not installed on the system. Changes for package SPROmrcom will not be applied to the system.
Package SPROlangx from directory SPROlangx in patch 124861-20 is not installed on the system. Changes for package SPROlangx will not be applied to the system.
Package SPROlang from directory SPROlang in patch 124861-20 is not installed on the system. Changes for package SPROlang will not be applied to the system.
Package SPROsunms from directory SPROsunms in patch 124861-20 is not installed on the system. Changes for package SPROsunms will not be applied to the system.
Checking patches that you specified for installation.
Done!
The following requested patches will not be installed because
the packages they patch are not installed on this system.
0 No Packages from patch 124861-20 are installed on the system.

Hi,
The 11gR2 installation on Solaris 10 sparc failed with prereuisite 124861-15.
When I tried to install the patch 124861-20, it failed with the following(see below):
I have Sun Studio 12-2 installed on the system.
It was complaining that some packages (SPROmrcom, SPROlangx, SPROlang,SPROsunms ) are not installed.
Where can I get these packages? Should not it be included in the Sun Studio 12-2 installation?
Thanks.
Zhigang
# patchadd 124861-20
Validating patches...
Loading patches installed on the system...
Cannot find package name, arch or version in pkginfo file /var/sadm/pkg/IR/pkginfo.
Done!
Loading patches requested to install.
Done!
The following requested patches have packages not installed on the system
Package SPROmrcom from directory SPROmrcom in patch 124861-20 is not installed on the system. Changes for package SPROmrcom will not be applied to the system.
Package SPROlangx from directory SPROlangx in patch 124861-20 is not installed on the system. Changes for package SPROlangx will not be applied to the system.
Package SPROlang from directory SPROlang in patch 124861-20 is not installed on the system. Changes for package SPROlang will not be applied to the system.
Package SPROsunms from directory SPROsunms in patch 124861-20 is not installed on the system. Changes for package SPROsunms will not be applied to the system.
Checking patches that you specified for installation.
Done!
The following requested patches will not be installed because
the packages they patch are not installed on this system.
0 No Packages from patch 124861-20 are installed on the system.
Refer my post *11gR2 Installation Error with patch 124861-15 as pre Req*
http://appsdbaworkshop.blogspot.com/2010/11/11gr2-installation-error-with-patch.html
thanks,
X A H E E R

So lately I decided I was tired of Tiger, and decided I would upgrade to Leopard. Well I made the mistake of erasing the hard drive before I made sure it would work. Well now like the installer was before it failed. And now when I boot it just won't work

So lately I decided I was tired of Tiger, and decided I would upgrade to Leopard. Well I made the mistake of erasing the hard drive before I made sure it would work. Well now like the installer was before it failed. And now when I boot I get the normal finder/question mark flashing folder. I also found a power Mac g4 that needs a new operating system. It's running 9.2. It's going to my grandma as a gift. I really need help.

I think you'll need to find a Retail 10.5 Disc.
Leopard requirements/10.5.x...
    * Mac computer with an Intel, PowerPC G5, or PowerPC G4 (867MHz or faster) processor
minimum system requirements
    * 512MB of memory (I say 1.5GB for PPC at least, 2-3GB minimum for IntelMacs)
    * DVD drive for installation
    * 9GB of available disk space (I say 30GB at least)
Classic/OS9 Apps no longer supported.
Trouble is Apple no longer sells it, check eBay & such for the Retail version, not the Gray Discs...
http://www.ebay.com/sch/i.html?_nkw=mac+os+x+leopard+retail+10.5
There are workarounds if the 867MHz CPU is the only hangup...
http://sourceforge.net/projects/leopardassist/
http://lowendmac.com/osx/leopard/unsupported.html
List of Applications Not Compatible with Leopard...
http://guides.macrumors.com/List:Applications_Not_Compatible_with_Leopard

UEFI installation fails to boot

Using the latest (2012.12.01) image, I can boot the CD in UEFI mode, `modprobe efivars` and `efibootmgr` work fine and I finished the installation.
However, upon trying to boot it, after a few seconds of init output, the screen turns black and nothing happens.
Motherboard is ASUS M5A97 Evo.

With nomodeset in the kernel parameters, I can boot and get to a command line, but when I try to start X, I get an error message stating that it can't set the mode, so there's less screens than it detected and therefore fails to start.
Without nomodeset, instead of the screen working, as soon as it gets to the part of booting up where it would change the resolution, the screen just violently flashes black and white.

[SOLVED] Luks with /arch/setup installation , fails at boot

Hi all,
So I tried to install arch on virtualbox with encrypted partitions (root /, /home/ and swap), but it fails at boot.
/dev/sda1 is /boot
/dev/sda2 is swap
/dev/sda3 is /
/dev/sda4 is /home
The root partition seems to be loading fine because it asks for my password, then the boot sequence goes on, until the /home/ (apparently) :
:: Bringing up loopback interface
:: Unlocking encrypted volumes: chome..Usage: cryptsetup [-?vyrq] (...all the options...can't copy paste with virtualbox)
/sbin/cryptsetup: Unknown action
failed [FAIL]
/dev/mapper/croot: clean, 27576/457856 files, 166316/1830898 blocks
fsck.ext4: No such file or directory while trying to open /dev/mapper/chome
Possibly non-existent device?
/dev/sda1: clean,29/24096 files, 20790/96356 blocks
[FAIL]
It seems that it tries to open /dev/mapper/chome but it's not mounted yet
In my /etc/crypttab, I added the lines :
chome /dev/sda4 none luks
cswap /dev/sda2 none luks
/etc/fstab (I didn't change anything, /arch/setup configured it that way) :
/dev/mapper/chome /home ext4 defaults 0 1
/dev/mapper/croot / ext4 defaults 0 1
/dev/mapper/cswap swap swap defaults 0 0
/dev/sda1 /boot ext2 defaults 0 1
And grub :
title Arch Linux
root (hd0,0)
kernel /vmlinuz-linux root=/dev/mapper/croot cryptdevice=/dev/sda3:croot ro
initrd /initramfs-linux.img
What I wanted to do was to have swap,root and home encrypted partitions mounted at boot, but maybe it is not possible?
I tried a lot of configurations for /etc/fstab and /etc/crypttab according to what I could find on the net but nothing worked. I read the whole tutorial https://wiki.archlinux.org/index.php/Sy … _with_LUKS but there is no config for fstab or crypttab or grub when installing with /arch/setup
Thanks for any help !
Last edited by John0000 (2012-04-12 12:50:18)

Indeed you have a point, putting password in plaintext isn't very safe.
There is a good alternative though: https://wiki.archlinux.org/index.php/Sy … _a_Keyfile
the reason why you don't have a passphrase for root in a file somewhere is that you provide this passphrase during boot-time.
Somewhere during boot you get the option to unlock you root device by typing in a passphrase... right?
ro means that the volume is mounted read only http://linux.die.net/man/8/mount

New Windows server 2003 Hyper-V guest fails to boot

Hello,
I'm currently doing some virtualization experiments on my new server hardware. The host hardware is:
IBM x3650 M4
x2 Xeon E5-2609
32GB RAM
x2 480 GB SSDs
Server OS: Windows server 2012
I'd like to test some legacy app virtualization. I've configured a VM and have installed Windows server 2003. The install is done via DVD. The issue at hand is that after the initial installation, the server fails to boot. The VM goes into a reboot loop
and so far the only error logging I'm able to find is in the hosts event log.
Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
Source: Microsoft-Windows-Hyper-V-Worker
Date: 7/8/2014 2:14:48 PM
Event ID: 18560
Task Category: None
Level: Critical
Keywords:
User: NT VIRTUAL MACHINE\A0D20FA4-B27B-4B58-85C1-87D74B0ADD2D
Computer: CCSTS1.cnet2k.cornerstonecredit.net
Description:
'LegacyTS' was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault. If the problem persists, contact Product Support. (Virtual machine ID A0D20FA4-B27B-4B58-85C1-87D74B0ADD2D)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-Worker" Guid="{51DDFA29-D5C8-4803-BE4B-2ECB715570FE}" />
<EventID>18560</EventID>
<Version>0</Version>
<Level>1</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-07-08T21:14:48.544007000Z" />
<EventRecordID>159</EventRecordID>
<Correlation />
<Execution ProcessID="1512" ThreadID="3536" />
<Channel>Microsoft-Windows-Hyper-V-Worker-Admin</Channel>
<Computer>CCSTS1.cnet2k.cornerstonecredit.net</Computer>
<Security UserID="S-1-5-83-1-2698121124-1264104059-3615998341-769460811" />
</System>
<UserData>
<VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<VmName>LegacyTS</VmName>
<VmId>A0D20FA4-B27B-4B58-85C1-87D74B0ADD2D</VmId>
<Rax>0x0</Rax>
<Rbx>0x0</Rbx>
<Rcx>0x0</Rcx>
<Rdx>0x0</Rdx>
<Rsp>0x804de00c</Rsp>
<Rbp>0x0</Rbp>
<Rsi>0x0</Rsi>
<Rdi>0x0</Rdi>
<R8>0x0</R8>
<R9>0x0</R9>
<R10>0x0</R10>
<R11>0x0</R11>
<R12>0x0</R12>
<R13>0x0</R13>
<R14>0x0</R14>
<R15>0x0</R15>
<Rip>0x80547c7c</Rip>
<Rflags>0x10046</Rflags>
<FpControlStatus>7F030000000000000000000000000000</FpControlStatus>
<XmmControlStatus>0000000000000000801F0000FFFF0000</XmmControlStatus>
<Cr0>0x8001003d</Cr0>
<Cr2>0x804ddffc</Cr2>
<Cr3>0xa02000</Cr3>
<Cr4>0x20</Cr4>
<Cr8>0xf</Cr8>
<Xfem>0x1</Xfem>
<Dr0>0x0</Dr0>
<Dr1>0x0</Dr1>
<Dr2>0x0</Dr2>
<Dr3>0x0</Dr3>
<Dr6>0xffff0ff0</Dr6>
<Dr7>0x400</Dr7>
<Es>0000000000000000FFFFFFFF2300F3C0</Es>
<Cs>0000000000000000FFFFFFFF08009BC0</Cs>
<Ss>0000000000000000FFFFFFFF100093C0</Ss>
<Ds>0000000000000000FFFFFFFF2300F3C0</Ds>
<Fs>00F0DFFF00000000FF1F0000300093C0</Fs>
<Gs>0000000000000000FFFFFFFF00000000</Gs>
<Ldtr>00000000000000000000000000000000</Ldtr>
<Tr>90685580000000006800000050008B00</Tr>
<Idtr>000000000000FF0700F4038000000000</Idtr>
<Gdtr>000000000000FF0300F0038000000000</Gdtr>
<Tsc>0x148e4294</Tsc>
<ApicBase>0xfee00900</ApicBase>
<SysenterCs>0x0</SysenterCs>
<SysenterEip>0x0</SysenterEip>
<SysenterEsp>0x0</SysenterEsp>
</VmlEventLog>
</UserData>
</Event>
My VM config
<?xml version="1.0" encoding="UTF-16" standalone="yes"?>
<configuration>
<_24984ed0-bdad-4b90-82b2-5d59f874e91e_>
<ChannelInstanceGuid type="string">{E4E9CD0E-4BBF-4C1B-B655-715781690655}</ChannelInstanceGuid>
</_24984ed0-bdad-4b90-82b2-5d59f874e91e_>
<_7d80d3db-61ee-4879-8879-5609f1100ad0_>
<address type="string">5353,00000000,00</address>
<version type="integer">1</version>
</_7d80d3db-61ee-4879-8879-5609f1100ad0_>
<_83f8638b-8dca-4152-9eda-2ca8b33039b4_>
<controller0>
<drive0>
<pathname type="string">E:\Hyper-V\VHD\LegacyTS.vhdx</pathname>
<pool_id type="string"></pool_id>
<type type="string">VHD</type>
</drive0>
<drive1>
<pathname type="string"></pathname>
<type type="string">NONE</type>
</drive1>
</controller0>
<controller1>
<drive0>
<pathname type="string">SCSI\CDROM&VEN_IBM_SATA&PROD_DEVICE_81Y3681\4&1864BF9E&0&010000</pathname>
<pool_id type="string"></pool_id>
<type type="string">ISO</type>
</drive0>
<drive1>
<pathname type="string"></pathname>
<type type="string">NONE</type>
</drive1>
</controller1>
<version type="integer">5</version>
</_83f8638b-8dca-4152-9eda-2ca8b33039b4_>
<_8e3a359f-559a-4b6a-98a9-1690a6100ed7_>
<port0>
<connection type="string"></connection>
</port0>
<port1>
<connection type="string"></connection>
</port1>
<version type="integer">2</version>
</_8e3a359f-559a-4b6a-98a9-1690a6100ed7_>
<_8f0d2762-0b00-4e04-af4f-19010527cb93_>
<controller0>
<drive0>
<pathname type="string"></pathname>
<type type="string">VFD</type>
</drive0>
</controller0>
<version type="integer">1</version>
</_8f0d2762-0b00-4e04-af4f-19010527cb93_>
<_a80e9c62-750a-4a6b-9548-d46677e806be_>
<ChannelInstanceGuid type="string">{23c9c636-93de-4aec-9bef-220766177a24}</ChannelInstanceGuid>
<Connection>
<AltPortName type="string">Dynamic Ethernet Switch Port</AltPortName>
<AltSwitchName type="string">Intel(R) I350 Gigabit Network Connection - Virtual Switch</AltSwitchName>
<AuthorizationScope type="string"></AuthorizationScope>
<ChimneyOffloadWeight type="integer">0</ChimneyOffloadWeight>
<Feature_C885BFD1-ABB7-418F-8163-9F379C9F7166>
<DisplayName type="string"></DisplayName>
<Flags type="integer">0</Flags>
<Setting_97274751-A1EC-4DC2-941D-B7F9A1AED814>
<Data type="bytes">AAIAAGQAAAAAAAAAAQAAAAAAAAA=
</Data>
<Version type="integer">256</Version>
</Setting_97274751-A1EC-4DC2-941D-B7F9A1AED814>
<Settings>
<Id type="string">97274751-A1EC-4DC2-941D-B7F9A1AED814</Id>
</Settings>
</Feature_C885BFD1-ABB7-418F-8163-9F379C9F7166>
<Features>
<Id type="string">C885BFD1-ABB7-418F-8163-9F379C9F7166</Id>
</Features>
<HostResources>
<HostResource type="string">8758EB1A-9687-41FC-9319-AE867D46BA5C</HostResource>
</HostResources>
<PoolId type="string"></PoolId>
<PreventIPSpoofing type="bool">False</PreventIPSpoofing>
<TestReplicaPoolId type="string"></TestReplicaPoolId>
<TestReplicaSwitchName type="string"></TestReplicaSwitchName>
</Connection>
<FriendlyName type="string">Network Adapter</FriendlyName>
<IsConnected type="bool">True</IsConnected>
<MacAddress type="string">00-15-5D-01-18-02</MacAddress>
<MacAddressIsStatic type="bool">False</MacAddressIsStatic>
<PortName type="string">E7F02418-A1EB-4FF9-84F8-BF461B2D00C6</PortName>
<SwitchName type="string">8758EB1A-9687-41FC-9319-AE867D46BA5C</SwitchName>
<VpciInstanceGuid type="string">{E9444985-111B-404A-82FE-48608A397676}</VpciInstanceGuid>
</_a80e9c62-750a-4a6b-9548-d46677e806be_>
<_ac6b8dc1-3257-4a70-b1b2-a9c9215659ad_>
<base_board>
<serial_number type="string">9595-3600-2199-6834-7686-3927-30</serial_number>
</base_board>
<bios_guid type="string">{B54BE7B5-05A4-4C4A-A2BD-D63272C7CCCD}</bios_guid>
<bios_serial_number type="string">9595-3600-2199-6834-7686-3927-30</bios_serial_number>
<boot>
<device0 type="string">Optical</device0>
<device1 type="string">HardDrive</device1>
<device2 type="string">Network</device2>
<device3 type="string">Floppy</device3>
</boot>
<chassis>
<asset_tag type="string">8437-8592-0329-9603-9215-1886-12</asset_tag>
<serial_number type="string">9595-3600-2199-6834-7686-3927-30</serial_number>
</chassis>
<num_lock type="bool">False</num_lock>
<version type="integer">2</version>
</_ac6b8dc1-3257-4a70-b1b2-a9c9215659ad_>
<_db8b9818-b4bb-4725-b99d-b4612716b6b4_>
<version type="integer">0</version>
</_db8b9818-b4bb-4725-b99d-b4612716b6b4_>
<global_settings>
<devices>
<allow_reduced_fc_redundancy type="bool">False</allow_reduced_fc_redundancy>
<generation_id type="string">883d11122d9b7b2c521be0c045ef3760</generation_id>
<storage_allow_full_scsi_command_set type="bool">False</storage_allow_full_scsi_command_set>
</devices>
<disk_merge_pending type="bool">False</disk_merge_pending>
<metrics>
<devicetype>
<deviceinstance>
<guid type="string">B637F346-6A0E-4DEC-AF52-BD70CB80A21D</guid>
<metric>
<enabled type="bool">False</enabled>
<lastcomputedtime type="integer">0</lastcomputedtime>
<peaktime type="integer">0</peaktime>
<poolid type="string"></poolid>
<resourcetypeid type="string">B637F347-6A0E-4DEC-AF52-BD70CB80A21D</resourcetypeid>
<starttime type="integer">0</starttime>
<typecode type="string">3F6F1051-C8FC-47EF-9821-C07240848748;0</typecode>
<value type="integer">0</value>
</metric>
</deviceinstance>
<guid type="string">B637F346-6A0E-4DEC-AF52-BD70CB80A21D</guid>
</devicetype>
<devicetype>
<deviceinstance>
<guid type="string">4764334D-E001-4176-82EE-5594EC9B530E</guid>
<metric>
<enabled type="bool">False</enabled>
<lastcomputedtime type="integer">0</lastcomputedtime>
<peaktime type="integer">0</peaktime>
<poolid type="string"></poolid>
<resourcetypeid type="string">4764334E-E001-4176-82EE-5594EC9B530E</resourcetypeid>
<starttime type="integer">0</starttime>
<typecode type="string">394DCE66-458F-4895-AE56-41D7C9602A49</typecode>
<value type="integer">0</value>
</metric>
<metric>
<enabled type="bool">False</enabled>
<lastcomputedtime type="integer">0</lastcomputedtime>
<peaktime type="integer">0</peaktime>
<poolid type="string"></poolid>
<resourcetypeid type="string">4764334E-E001-4176-82EE-5594EC9B530E</resourcetypeid>
<starttime type="integer">0</starttime>
<typecode type="string">FF85EA46-9933-4436-BE5D-C96827399966</typecode>
<value type="integer">0</value>
</metric>
<metric>
<enabled type="bool">False</enabled>
<lastcomputedtime type="integer">0</lastcomputedtime>
<peaktime type="integer">0</peaktime>
<poolid type="string"></poolid>
<resourcetypeid type="string">4764334E-E001-4176-82EE-5594EC9B530E</resourcetypeid>
<starttime type="integer">0</starttime>
<typecode type="string">04BDF59E-580D-4441-8828-FFFE44472D2D</typecode>
<value type="integer">0</value>
</metric>
</deviceinstance>
<guid type="string">4764334D-E001-4176-82EE-5594EC9B530E</guid>
</devicetype>
<devicetype>
<deviceinstance>
<guid type="string">83F8638B-8DCA-4152-9EDA-2CA8B33039B4</guid>
<metric>
<enabled type="bool">False</enabled>
<lastcomputedtime type="integer">0</lastcomputedtime>
<peaktime type="integer">0</peaktime>
<poolid type="string"></poolid>
<resourcetypeid type="string">70BB60D2-A9D3-46AA-B654-3DE53004B4F8</resourcetypeid>
<starttime type="integer">0</starttime>
<typecode type="string">AD29978B-AAB6-44AE-81CD-0609BF929F18;0\0\L</typecode>
<value type="integer">0</value>
</metric>
</deviceinstance>
<guid type="string">83F8638B-8DCA-4152-9EDA-2CA8B33039B4</guid>
</devicetype>
</metrics>
<owner>
<sid type="string">S-1-5-21-1940488291-1951097212-1584025624-1392</sid>
</owner>
<power>
<host_shutdown>
<action type="integer">1</action>
</host_shutdown>
<host_startup>
<action type="integer">1</action>
</host_startup>
</power>
<snapshots>
<list>
<size type="integer">0</size>
</list>
</snapshots>
<unexpected_termination>
<action type="integer">1</action>
</unexpected_termination>
<vhd_path_acled type="bool">True</vhd_path_acled>
</global_settings>
<manifest>
<size type="integer">11</size>
<vdev001>
<device type="string">58f75a6d-d949-4320-99e1-a2a2576d581c</device>
<flags type="integer">1</flags>
<instance type="string">58F75A6D-D949-4320-99E1-A2A2576D581C</instance>
<name type="string">Microsoft Synthetic Mouse</name>
</vdev001>
<vdev002>
<device type="string">197f74e3-b84b-46de-8ae6-82f1cd181cdc</device>
<flags type="integer">1</flags>
<instance type="string">197F74E3-B84B-46DE-8AE6-82F1CD181CDC</instance>
<name type="string">Microsoft Synthetic Keyboard</name>
</vdev002>
<vdev003>
<device type="string">f3cf6965-e8d3-44a9-9b7d-a04245ea7525</device>
<flags type="integer">1</flags>
<instance type="string">F3CF6965-E8D3-44A9-9B7D-A04245EA7525</instance>
<name type="string">Microsoft Synthetic Video</name>
</vdev003>
<vdev004>
<device type="string">84eaae65-2f2e-45f5-9bb5-0e857dc8eb47</device>
<flags type="integer">1</flags>
<instance type="string">84EAAE65-2F2E-45F5-9BB5-0E857DC8EB47</instance>
<name type="string">Microsoft Heartbeat Component</name>
</vdev004>
<vdev005>
<device type="string">2a34b1c2-fd73-4043-8a5b-dd2159bc743f</device>
<flags type="integer">1</flags>
<instance type="string">2A34B1C2-FD73-4043-8A5B-DD2159BC743F</instance>
<name type="string">Microsoft Key-Value Pair Exchange Component</name>
</vdev005>
<vdev006>
<device type="string">9f8233ac-be49-4c79-8ee3-e7e1985b2077</device>
<flags type="integer">1</flags>
<instance type="string">9F8233AC-BE49-4C79-8EE3-E7E1985B2077</instance>
<name type="string">Microsoft Shutdown Component</name>
</vdev006>
<vdev007>
<device type="string">2497f4de-e9fa-4204-80e4-4b75c46419c0</device>
<flags type="integer">1</flags>
<instance type="string">2497F4DE-E9FA-4204-80E4-4B75C46419C0</instance>
<name type="string">Microsoft Time Synchronization Component</name>
</vdev007>
<vdev008>
<device type="string">5ced1297-4598-4915-a5fc-ad21bb4d02a4</device>
<flags type="integer">1</flags>
<instance type="string">5CED1297-4598-4915-A5FC-AD21BB4D02A4</instance>
<name type="string">Microsoft VSS Component</name>
</vdev008>
<vdev009>
<device type="string">6c5addb9-a11a-4e8e-84cb-e6208201db63</device>
<flags type="integer">1</flags>
<instance type="string">6C5ADDB9-A11A-4E8E-84CB-E6208201DB63</instance>
<name type="string">Microsoft RDV Component</name>
</vdev009>
<vdev010>
<device type="string">2fc216b0-d2e2-4967-9b6d-b8a5c9ca2778</device>
<flags type="integer">1</flags>
<instance type="string">A80E9C62-750A-4A6B-9548-D46677E806BE</instance>
<name type="string">Synthetic Ethernet Port</name>
</vdev010>
<vdev011>
<device type="string">d422512d-2bf2-4752-809d-7b82b5fcb1b4</device>
<flags type="integer">1</flags>
<instance type="string">24984ED0-BDAD-4B90-82B2-5D59F874E91E</instance>
<name type="string">Synthetic SCSI Controller</name>
</vdev011>
<version type="integer">260</version>
</manifest>
<properties>
<global_id type="string">B37E54CD-FFBB-44DA-8B7C-322B922EAD72</global_id>
<highly_available type="bool">False</highly_available>
<last_powered_off_time type="integer">130493284127496105</last_powered_off_time>
<last_powered_on_time type="integer">130493284065876653</last_powered_on_time>
<last_state_change_time type="integer">130493284127496105</last_state_change_time>
<name type="string">LegacyTS</name>
<notes type="string"></notes>
<type_id type="string">Virtual Machines</type_id>
<version type="integer">1024</version>
</properties>
<settings>
<global>
<logical_id type="string">B37E54CD-FFBB-44DA-8B7C-322B922EAD72</logical_id>
</global>
<memory>
<bank>
<dynamic_memory_enabled type="bool">True</dynamic_memory_enabled>
<limit type="integer">1048576</limit>
<priority type="integer">5000</priority>
<reservation type="integer">512</reservation>
<size type="integer">4096</size>
<target_memory_buffer type="integer">20</target_memory_buffer>
</bank>
<vnuma>
<max_size_per_node type="integer">14770</max_size_per_node>
</vnuma>
</memory>
<processors>
<count type="integer">1</count>
<features>
<limit type="bool">False</limit>
</features>
<limit type="integer">100000</limit>
<limit_cpuid type="bool">False</limit_cpuid>
<reservation type="integer">0</reservation>
<vnuma>
<count_per_node>
<max type="integer">4</max>
</count_per_node>
<node_per_socket>
<max type="integer">1</max>
</node_per_socket>
</vnuma>
<weight type="integer">100</weight>
</processors>
<stopped_at_host_shutdown type="bool">False</stopped_at_host_shutdown>
<vnuma>
<enabled type="bool">False</enabled>
</vnuma>
</settings>
</configuration>
If its relevant, the host is not yet activated license wise. I downloaded the demo version so I could test my idea before making a purchase to go ahead with full implementation.
As it stands right now I'm not sure how to troubleshoot this. Many searches on google have not turned up any helpful info. Does anyone have any ideas?
Thanks,
D

Hi ,
First , please refer to the supported guest OS of windows 2012 hyper-v :
http://technet.microsoft.com/library/hh831531.aspx
2003/R2 should be with sp2 and max 2 virtual processors .
"'LegacyTS' was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault."
If the issue is not due to the above items , you can try to check the "CPU compatibility " in that VM settings for troubleshooting:
Hope it helps
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

[SOLVED] Arch Linux Duke (2007) Fails to Boot

Folks, I have a unique and challenging problem that has exhausted my Arch Linux skills, and so I am now turning to you.
I have a vintage Pentium Pro 200 system (that’s 200 MHz folks! – 200 MHz 686 architecture – the original 686!), two CPUs, running a dual boot between Windows NT 4.0 and Arch Linux Duke (2007). It has 512 MB of RAM and a 120 GB hard drive, partitioned up between Windows NT and Linux. I built this system new in 2007, hence the dated version of Arch. It has run like a charm all these years, granted not getting that much use. After about a year of no use at all, I fired the system up last week to help with a little research for a blog post I was writing on networking Windows NT 4.0 and Mac OS 8.6. Windows NT 4.0 fired right up with no issue, and after I was done testing what needed to be tested I tried to boot over to Arch.
After a year of disuse, Arch unexpectedly and stubbornly refused to boot. The boot process started up just fine, but towards the end, it declared that it could not mount the root file system on the root device and took a kernel panic and stopped. My Arch skills have gotten a bit rusty in the last few years, but I dusted them off and went to work. My guess was a file system or superblock error. Arch wouldn’t boot, but I dragged out my trusty RIPLinux 2.9 Rescue Live CD and fired it up. It came right up and ran, and I was able to mount the Arch partition and view all the files… everything seemed to be there; it just wouldn’t boot. Windows NT 4.0 AND RIPLinux both boot and run on the machine, so the hardware is fine as well.
A little information on the disk layout. Windows NT 4.0 is in the first partition on the hard drive. The extended partition has a second Windows NT 4.0 partition (sort of a /home partition for Windows NT 4.0), followed by the main Arch partition (the one I am trying to boot), followed by a swap partition and then the largest partition, which I use to share data between Arch and Windows NT 4.0 (I have loaded an ext2/3 driver into Windows NT 4.0 and it happily accesses the Linux partitions on the box).
RIPLinux’s e2fsck did find some issues with the Arch partition and I had it repair them all. I checked again afterwards that all the files were still there, and they were. With the partition now known to be clean, and the superblock repaired from one of the backups, all should have been well. However, Arch still wouldn’t (and still won’t) boot.
RIPLinux has a kind of a chain loader function, so I had it attempt to start up Arch for me. However, this was flummoxed by the fact that Arch addresses all my hard drive partitions as /dev/sdax and RIPLinux addresses them as /dev/hdax. Hence, without a common language, it was hard to get the one to start the other. Still, using this function, I have been able to get a crippled version of Arch running on the machine again. No modules had been loaded, and so it couldn’t do almost anything, but there it was (and is), Arch Linux Duke, at the CLI level. From there, I can see all the files, I can move freely in and out of my user account and the root account, but I can’t make the thing actually boot properly.
If you have read this far, you are a trooper. Summarizing what I know, the hardware is good, the file system is clean, the superblock is good, I can mount it cleanly from a live CD and I can chain load a crippled version of Arch. Here is the boot process blow-by-blow. When I try to do a normal boot, the Windows NT 4.0 loader passes control to the Lilo boot sector I have placed on hda1 (sda1 in Duke’s parlance). Lilo takes over, present a menu and when I select Duke, takes off. Arch Linux Duke starts to boot. It gets a good long way along, all the way along to:
:: Loading udev events [Pass]
:: Mount root Read-only
:: Checking file systems
This is where it stops.
The next thing I see is:
/dev/sda6
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else) then the superblock is corrupt and you might try running e2fsck with an alternate superblock:
E2fsck –b 8193 <device>
I then get a sort of character based splash screen that says
**********FILE SYSTEM CHECK FAILED ****************************
* Please repair manually and reboot. Note that the root file system
* is currently mounted read-only. To remount it read-write, type:
* mount –n –o remount,rw /. When you exit the maintenance
* shell, the system will reboot automatically
Give root password for maintenance
At this point, I give the root password and enter the maintenance shell as root. I typed in “mount” and the first entry I got back is
/dev/sda6 on / type ext3 (rw)
This is exactly the root partition that the start up complains about. It is clearly there. I can see it, I can walk around it… it is clearly there. Why won’t it boot? Despite the message, the superblock is fine – it passes every test e2fsck can throw at it.
At this point, I did a “e2fsck /dev/hda6 (which is how RIPLinux would have passed it into Arch” and it says it is “clean”. I suspect that the Superblock message is because Arch sees root as sda6, while RIP passed it in as hda6...
Deciding to see what Arch would be seeing as it tried to set things up in the boot sequence, I tried the following next:
# mknod “/dev/root2” b 3 6
(“3” because RIPLinux refers to my hard drive as IDE, while Arch refers to it by major number “8”, which is SCSI. By the way, it IS an IDE drive – not sure why Arch insists on using the sdx nomenclature instead of hdx)
Then I entered “mount /dev/root2 /mnt/hda6” and “ls /mnt/hda6”
All was well. I can make the node, I can mount it, and I can see the contents. All is clearly well, but something is clearly wrong enough that Arch can’t boot.
I am totally out of ideas. I have tried every trick I know and am out of tricks. I would welcome any insights as to what I could try to get this venerable Arch installation back on its legs.
By the way, the key section of the /etc/lilo.conf file (lest anyone want to know) is:
image = /boot/vmlinuz26
root = /dev/sda6
label = ArchLinux-Duke
initrd = /boot/kernel26.img
read-only
I am stumped. Thanks in advance for any and all pointers you may be able to offer.
Last edited by mac57 (2014-06-02 17:42:21)

Folks, thanks for all your helpful comments, and I wanted to report back to you that I finally overcame the issue, and ArchLinux-Duke (2007) is once again executing flawlessly on my old Pentium Pro 200 system. I won't bother reporting here all the blind allies I went down as I tried to figure out what was wrong, but in the end, literally moments before I was about to give up and overwrite my Arch installation with a new Linux variant (antiX seemed well suited for such old and low power hardware), my attention was drawn to a note I had made in my files back in 2007 about a problem with similar symptoms. In that case, I had just deleted ZenWalk Linux from the hard drive (both Arch and Zen had been on the drive), and merged several partitions to make use of the newly free space. This had changed Arch's view of the drive lettering, and what had been its /dev/sddx root device was now /dev/sdcx. Arch failed to boot, throwing off the same errors I was seeing now. I wish I had recalled that note a month or so ago! It would have saved me a lot of work and a lot of frustration.
At any rate, as a last step, and testing the idea that maybe the drive lettering had changed for some reason, I repeatedly manually booted Arch, specifying root=/dev/sda6, then /dev/sdb6, then /dev/sdd6, and finally, /dev/sdc6. Eureka! Arch now considered itself to be on /dev/sdc6 whereas previously it had been on /dev/sda6. This got me part way there, but the boot failed at the filesystem check stage and threw me into root. I disabled the file system check in /etc/rc.sysinit and got farther. Then I cleaned up /etc/fstab to agree with the new sdc naming, and I was back on the air fully.
So, what had happened was that Arch had changed its view of the drive it was on from sda6 to sdc6. While I could not understand why this "sudden" change had occurred, at least I had a solution, and had Arch back up and running.
Trolling through the rest of my notes, I found the answer. In 2012, the Tekram SCSI card in the machine failed, and I ultimately replaced it with an Adaptec card. The Tekram card did not have a BIOS segment on it. The Adaptec card did. My guess is that this caused the two internal SCSI devices I have built into the system (Iomega ZIP and Jaz respectively) to be enumerated first, claiming the "sda" and "sdb". device names. That left "sdc" for the root device, and that is where Arch went next. This is my guess anyway.
I should have caught this issue back in 2012, at the time, but from my notes, I can see that I tested the new card thoroughly using the Windows NT 4.0 side of the machine, but never thought to bring up Arch as well. Hence, this problem lay dormant for two years, before I attempted to fire up Arch last month and blundered right into it.
It has not all been bad. I have learned more about the ext2 and ext3 file systems and superblocks in the intervening time than I will ever need to use. I have learned how to manually boot Linux on a machine whose BIOS is so old that it cannot address the disk cylinder that the kernel is on and I have completely refreshed the many general Linux skills that used to just flow from my finger tips. It has been a frustrating experience, but ultimately a successful and useful one.
Just wanted to let everyone know that this is now [SOLVED]. I would mark the post as such, but I don't see any obvious way to do that. Thanks again everyone.

MacBook Pro failing to boot up despite disk utility repair and PRAM

Problem: MBP frozen on boot up screen with Apple logo and turning gear (which freezes after a while aswell)
Solutions attempted: disk repair via custom recovery- disk utility, PRAM
Device: MacBook Pro 15" (early 2010) running 10.9
Additional info-
Never had any issue with the device and this seems to have happened all of a sudden. Installed an SSD a few months ago, and just realised the ssd did not have a recovery partition. However I connected my older hardrive via USB to access recovery which seemed to work fine.
NOTE: for the past few weeks, every now and then I was unable to power the device off and whenever this occurred, there seemed to be a few bugs (ie unable to empty thrash-error 50 and enable to increase/decrease volume/screen brightness). However, holding the power button and restarting it seemed to have fixed it.
Had the same issue but this time around MBP failed to boot up.
Any possible suggestions?

Ranban wrote:
Are you suggesting reinstalling the os?
No.
Furthermore, is there a way to keep the data intact using this method? Or retrieve it at the least?
Repairing a disk should have no affect on the data, nor would an OSX installation. However if the data has value, there always should be a backup, preferably two.
In your original post you said "attempted: disk repair via custom recovery- disk utility". The term 'custom recovery' to me is alien and thus confusing.
What I am suggesting is a repair of the HDD using the original installation disk, not an OSX installation.
You insert the disk holding down the C key at startup. Proceed with the process until you see on the top of the display a menu bar. Select UTILITIES and from the drop down menu select Disk Utility. Then select Disk Utility>First Aid and then run Verify and repair. Exit from the installation process.
That way I know that the attempted repair was properly executed. You may have in essence done that, but there is an element of doubt in my mind.
Ciao.

Installation error Solaris 10-u6-ga1

I must be missing something really obvious on the installation of Solaris 10 U6. I've come up against the error message upon manually partitioning, and using UFS. After the install the error is:
Solaris 10 10 software installation partially failed
Solaris 10 packages partially installed
SUNWlur
Then at reboot it loops and loops
If I install using ZFS no problem. Unfortunately I have to use UFS for this install.
I pulled down the sol-10-u6-x86-ga1 dvd and installed on an Vmware to see what I'd get. If I manually setup the drive, it fails to with the same error.
Here is my drive layout both sparc server and vmware(x86)
/ = 10 Gb
swap = 10 Gb
/etc = 10 Gb
/usr = 10 Gb
/var = 10 Gb
/export=remaining drive space.
I'm I missing something obvious?
thanks
bill

There should be more information in the install log about why the one package failed. If you search for the package name in the log you should be able find it. Then that might help determine whether the package can be installed on its own, possibly fixing your reboot issue.
-- Alan

How to Add a Physical Interface After Installation in Solaris 10

How to Add a Physical Interface After Installation in Solaris 10
Hi Java Specialist,
I am trying to setup a network interface with the following steps on a new fresh Solaris 10 installation using the instruction titled How to Add a Physical Interface After Installation in Solaris 10 3/05 ONLY from http://docs.oracle.com/cd/E19253-01/816-4554/esxhb/index.html:
1. # ifconfig lo0 plumb up
2. # ifconfig lo0 10.56.8.101 netmask 255.255.240.0. This was the working Windows DHCP environment prior to installing Solaris
10 on top of it.
3. # Added saturn to /etc/hostname.lo0.
4. # Added 10.56.8.101 to /etc/inet/hosts
5. # Added 10.56.0.0 255.255.240.0 to /etc/inet/netmasks
6.# reboot
However, the following errors kept recurring:
svcs –xv …. unable to qualify my own domain name,
failed with exit status 69.
Any idea on what other steps have I missed? I was hoping to only do step 3 – 6 for the change to apply permanently.
Many thanks,
Jack

Hi Java Specialist,... in a Solaris forum?
1. # ifconfig lo0 plumb upThe loopback connection (your lo0)is NOT a physical interface. There are no hardware components for it. Nor can I think of any reason why it should ever be anything other than the default 127.0.0.1
Use your favorite Internet search site (such as Google, Bing, Yahoo) to learn more about it.
2. # ifconfig lo0 10.56.8.101 netmask 255.255.240.0. This was the working Windows DHCP environment ...I have no idea how a nonexistent software construct gets a DHCP address in a MS Operating System, unless you are confusing this with the "Microsoft Loopback Adapter" which is an utterly different concept. Again, go see what Google tells you.
<br>
<br>
<br>
... completely unrelated to configuring an IP...
unable to qualify my own domain nameAgain, search the Internet or even search these forums with that string of words.
Go back through your two most recent posts and read the responses again.
They seem to both be on the same topic as this new one -- configuring an IP on something.
How to initialize new IP address on secondary interface permanently
How to change IP address permanently on Solaris 10
When you've done all that, then come back and tell us what you are actually trying to do.

Installation of Solaris 10 fails at booting kernal

Similar Messages

Maybe you are looking for