UNMOUNTABLE_BOOT_VOLUME HP nc6400

HP notebooks that use Microsoft Windows XP without XP Service Pack 2 installed may start with the following error:
STOP 0x000000ED (0xaaaaaaaa,0xbbbbbbbb,0xcccccccc,0xdddddddd) UNMOUNTABLE_BOOT_VOLUME

This error is related to the way Windows XP interacts with the hard drive during an unexpected shutdown. Sometimes the contents of the cache are not written to the drive properly causing the error to appear when the notebook restarts.

This document provides instructions to repair your notebook PC and prevent this error from reoccurring. Once you have repaired your notebook PC, be sure to follow the steps to prevent the error from occurring again.

View the knowledge base article from Microsoft, Stop 0x000000ED Error Message When Volume on IDE Drive with Caching Enabled Is Mounted (in English) and the Microsoft Help and Support article, Unmountable Boot Volume (in English).

Repairing the notebook PC when the error occurs
The following repair options require the HP Operating System disc that was included with the HP Notebook PC. If you have misplaced or lost your disc please view HP Notebook PCs - Obtaining a Recovery CD or DVD set to order a new disc. For customers in Europe, Middle East, and Africa please refer to the HP support document Europe, Middle East, and Africa - Statement on the Availability of the Recovery Software on CD . For other countries/regions, contact your local HP support center for information about obtaining recovery CDs.


Option 1:

Use CHKDSK from the Recovery Console
Start the computer with the HP Operating System disc in the CD or DVD drive.

Press any key when prompted to boot from the CD or DVD.

A blue screen will appear and several files will load. This process takes about 30 seconds to complete. You should not have to select anything from the keyboard.

At the blue setup menu, press R to Repair a Windows XP installation.

At the C: prompt, type chkdsk /r . This repair process may take 30 - 60 minutes depending on the size of the hard drive and repairs needed.

After the chkdsk completes, type Exit at the C: prompt.

Windows will restart. Eject the CD or DVD and it should continue normally.

Já aderi ao ping.fm.. http://ping.fm

uma ferramenta excelente para fazer updates simultaneos a diversos perfis "sociais" e aos blogs..

erros ARcServe E5110 The database is no longer available." "E4101 Unable to login to db engine" "E3530 Failed to login to database EC=-2005

This has been based on CA support KB - Reference is TEC 426805
Title: "E5110 The database is no longer available." "E4101 Unable to login to db engine" "E3530 Failed to login to database EC=-2005"
Description:
The errors listed above may appear if there is a problem with the ARCserve standard database (VLDB) which can in turn place the ARCserve Database Engine in a shutdown state.
Solution:
Resolving the Problem
If the database engine will not stay in a running state this could be an indication of a problem with the contents within the database. As a first step perform the following:
Run CSTOP.BAT from the ARCserve install directory.
Remove the following files from X:\Program Files\CA\BrightStor ARCserve Backup\Database:
rdm.chi, rdm.chk and rAAAA*.chg
Remove the *.tmp files from the X:\Program Files\CA\BrightStor ARCserve Backup\temp directory.
Edit VELOCIS.INI in X:\Program Files\CA\BrightStor ARCserve Backup\Database modifying the following entries to the values listed:
Archiving =0
AsyncRead =0
AsyncWrite=0
Run CSTART.BAT from the ARCserve install directory.
If this does not help than this may be an indication that detail table data in the database have inconsistencies. An initialization of this table can be done to zero out the detail specific data while retaining specific information relating to jobs, tapes, media pools, etc. in tact. It should be noted that this operation will remove all detail record information for given backups, and specific restore data will need to be merged back into the database for restore by Tree, Session, and Query operations.
Close all ARCserve applications.
Start > Programs > ARCserve > ARCserve Server Admin.
Select the Database Engine tab.
Select Operation > Initialize Database...
Select "The database to be initialized" and then highlight astpsdat.
Click the initialize button.
If the initialization of the ASTPSDAT database does not resolve the problem please contact CA Technical Support.

reset sessao Terminal Server por CMD

Fortunately there is an easy solution. Windows 2000+ (includes Windows XP and 2003) have two command-line tools called qwinsta and rwinsta that can query and reset a remote session.
For example, let's say that I can't gain access to a server using Terminal Services because both sessions are used up. I can use another server to check the status of the first one. As long as the logged in user has administrative rights on the non-accessible machine I would run this:

qwinsta /server:12.12.12.12

Where 12.12.12.12 is the IP address or name of the non-accessible machine.
This will display something like this:
> qwinsta /server:12.12.12.12
SESSIONNAME USERNAME ID STATE TYPE DEVICE console 0 Conn wdcon rdp-tcp 65536 Listen rdpwd rdp-tcp#470 Bob 1 Active rdpwd rdp-tcp#471 Jane 3 Active rdpwd

Now I know that Bob and Jane are the two that are logged in. Since Jane left the office 20 minutes ago I know that she forgot to log off. I don't know where Bob is but I only need one session so I'll ignore him for now.
To disconnect Jane's session I would type this:

rwinsta /server:12.12.12.12 3

Notice the 3 which is the session ID I found from using qwinsta above.
Yet another option with W2K3 is a new feature that lets you connect to the desktop directly and gain a 3rd session.
If you're like me, you probably noticed that rwinsta and qwinsta seems like strange names. This came from the Citrix Metaframe days which Terminal Services has descended from. It stands for:
qwinsta = Query WINdows STAtionrwinsta = Reset WINdows STAtion
One final comment. Microsoft has replaced these two tools with Query but since qwinsta and rwinsta is fully compatible with W2K WinXP and W2K3 I choose to use it instead.

invalid boot.ini e system\hal.dll error

Antes de fazer o que vou descrever agora é necessario verificar se sabemos a conta de administrator e sua password.

Caso nao saibamos a password poderemos entrar via MINI PE CD e fazer password renew ou null password á conta de administrator


depois seguimos os seguintes passos:

Para resolver este problema, inicie o computador a partir do CD do Windows XP, inicie a Consola de recuperação e utilize a ferramenta Bootcfg.exe para recriar o ficheiro Boot.ini. Para tal, siga estes passos:

Configure o computador para iniciar a partir da unidade de CD-ROM ou DVD-ROM. Para obter mais informações sobre como o fazer, consulte a documentação do computador ou contacte o respectivo fabricante.

Introduza o CD-ROM do Windows XP na unidade de CD-ROM ou de DVD-ROM e reinicie o computador.

Quando receber a mensagem "Prima qualquer tecla para arrancar a partir do CD", prima qualquer tecla para iniciar o computador a partir do CD-ROM do Windows XP.

Quando receber a mensagem "Bem-vindo ao programa de configuração", prima R para iniciar a Consola de recuperação:

Se tiver um computador com arranque duplo ou arranque múltiplo, seleccione a instalação que tem de utilizar a partir da Consola de recuperação.

Quando lhe for pedido, introduza a palavra-passe de administrador e prima ENTER.
Na linha de comandos, escreva bootcfg /list e prima ENTER. As entradas no ficheiro Boot.ini actual são apresentadas no ecrã.

Na linha de comandos, escreva bootcfg /rebuild e prima ENTER. Este comando detecta a existência de instalações do Windows XP, Microsoft Windows 2000 ou Microsoft Windows NT nos discos rígidos e apresenta os resultados. Siga as instruções apresentadas no ecrã para adicionar as instalações do Windows ao ficheiro Boot.ini. Por exemplo, siga estes passos para adicionar uma instalação do Windows XP ao ficheiro Boot.ini:

Quando receber uma mensagem semelhante à mensagem seguinte, prima S:

Número total de instalações do Windows identificadas: 1[1] C:\WindowsAdicionar a instalação à
lista de arranque? (Sim/Não/Todas)

Recebe uma mensagem semelhante à mensagem seguinte:

Introduza o identificador de carregamentoEste é o nome do sistema operativo. Quando receber esta mensagem, escreva o nome do sistema operativo utilizado e prima ENTER. Este será o Microsoft Windows XP Professional ou Microsoft Windows XP Home Edition.

Recebe uma mensagem semelhante à seguinte:
Introduza as opções de carregamento do SOQuando receber esta mensagem, escreva /fastdetect e prima ENTER. Nota: as instruções apresentadas no ecrã poderão divergir, dependendo da configuração do computador.

Escreva exit e prima ENTER para sair da Consola de recuperação. O computador é reiniciado e a lista de arranque actualizada será apresentada quando receber a mensagem "Seleccione o sistema operativo para iniciar".

SAS Disks e RAID

Os discos SAS que por vezes acompanham os servidores da HP, quando ligados em raid com um controlador Smart Array E200 necessitam que seja incluido na configuraçao :

HP Internal SAS/SATA Multi-Lane Cable Kit
Part code:
464830-B21

De outra forma os discos SAS nao conseguem ser vistos pela controladora RAId.

Este cabo é ligado numa extremidade na controladora Raid e noutra no backplane do servidor

load de Sata Drivers Windows XP

Para o NC6400 o driver de sata é ICH7M

PARA O 6910P o driver é o ICH8M.


mas nao funcionou no 6910p até fazer disable na bios de "SATA NATIVE MODE". o disco comporta-se entao como um disco IDE e permite ao WIN PE fazer a instalação.

Depois é fazer enable do SATA e correr os drivers para instalar dentro do windows XP.

http://forums11.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=1174004