topic Re: Bad Blocks in Operating System - HP-UX

Bad Blocks

Nagamani_1 — Wed, 24 Oct 2001 10:53:21 GMT

When i login to HP 9000 K-class server i get the message.
Please wait...checking for disk quotas
free(4001ba58) bad block. (memtop = 40027000 membot = 4001b480)
free(4001ba68) bad block. (memtop = 40027000 membot = 4001b480)
Is it due to bad blocks ..? How do i set this right.?

Also initial hardware tests shows( when the system was rebooted after applying patch)
Test C263
Warn 7702 memory

Is this a hardware failure..?

regds
Nag

Re: Bad Blocks

James R. Ferguson — Wed, 24 Oct 2001 11:09:54 GMT

Hi:

"Test C263" is a memory write test. "Warn 7702" indicates that memory was *not* tested, but initialized only.

I'd turn back *on* the memory test routines and reboot. You may have some memory problems.

In my experience, turning off the memory diagnostics to save boot time doesn't gain much. The processor test routines take the bulk of the time.

Also, if you have STM installed, you can look at memory errors by doing the following:

# echo "selclass qualifier memory;info;wait;infolog"|cstm > /tmp/meminfo

Regards!

...JRF...

Re: Bad Blocks

Sridhar Bhaskarla — Wed, 24 Oct 2001 12:43:46 GMT

Turning of memory check during the boot doesn't buy us much time on K servers. So, turn off the fastboot and let the system test the memory while booting up. Then you can use stm to verify if there are any errors and let HP know if so.

-Sri

Re: Bad Blocks

Roger Baptiste — Wed, 24 Oct 2001 13:17:33 GMT

Both the problems may be interrelated and due to
memory-bit errors.
Run STM and check the
stm logs for memory errors.
This can be done by:
Run STM
Click on Device/select/Class
Select Memory/OK
Select Tools/Information/Informationlog
-> Look for memory error
counts in the LOG file

You can also reboot
the system, go into diagnostics mode and run memory tests. Also remember
to turn on Memory tests during
the boot process.

With this details you
would need to get an HP engineer to identify the faulty memory card.

-raj