Hi Friends,
My solaris box V440 got stucked. I couldn't accessit from the remote console. Finally i restarted the box.
Can you tell me what are the ways we can find out the issues
and what are the logs we can check other than /var/log/messages.
Thanks
Jinu (1 Reply)
Hi,
My system is crashing with following error .. i tried to boot from the network and unencapsulated the root disk from SVM .. but still not able to boot the box , can any one point me to some direction .. i do not want to build the box new as of now just want to troubleshoot if possible..
... (3 Replies)
I installed solaris 10 in my amd based system with 512 mb ram. After installation it booted poping up the grub menu...after that...
It showed something like....rougly
syncing file systems.... ................ done (not all i/o completed)
dumping kernel compreesion ratio 2:1 succeded... (1 Reply)
Hello,
I've a very weird problem with one of the machines. When I try to boot off a working DVD that I used to install another system with it spits out the following message:
Sun Fire V440, No Keyboard
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.22.33, 8192 MB... (14 Replies)
Hi:
I bougth an used Sun Fire v440, and It have a firmware password. When I turn on the server, it ask for firmware password. (I don 't know what is the correct password). I can access to SC, but when I want to access to OBP, Firmware Password appears again. I remove the battery for two hours,... (1 Reply)
Hello Admins,
Howz it going?
Coming to our forum after long time.
Well, a solaris x86 system on my vmware workstation is facing a big trouble.
I did a file system check on root file system. And after reboot, I am getting an error for both normal mode and fail safe mode.
I have... (4 Replies)
Over the last month or so my CentOS server has been crashing for reasons I do not know. It has been running for over a year with regular yum updates without problems. The load on the server is perfectly normal with CPU usage at 5-6% and RAM usage at less than half of 32GB of RAM (multiple smaller... (3 Replies)
Got a T2000 which has got the 2.5" SAS drives. Want to be able, if I can, to connect to USB caddy and connect to a V440.
Anyone ever tried this? To be honest, having problems even finding a SAS-USB caddy. (0 Replies)
Hi,
I have a SUN Fire V440 server running Solaris 8. One of the 4 disks do not appear when issued the format command. The "ready to remove" LED is not on either.
Metastat command warns that this disk "Needs maintenace". Can I just shutdown and power off the machine and then insert an... (5 Replies)
Hi there,
I have a V440 Server based on Sun Microsystem with Solaris OS.
Is there any way to auto power on the system only with cabling the V440 with 220 v?
Thanks! (10 Replies)
Discussion started by: proof_enrique
10 Replies
LEARN ABOUT NETBSD
badsect
BADSECT(8) BSD System Manager's Manual BADSECT(8)NAME
badsect -- create files to contain bad sectors
SYNOPSIS
badsect bbdir sector ...
DESCRIPTION
badsect makes a file to contain a bad sector. Normally, bad sectors are made inaccessible by the standard formatter, which provides a for-
warding table for bad sectors to the driver; see bad144(8) for details. If a driver supports the bad blocking standard it is much preferable
to use that method to isolate bad blocks, since the bad block forwarding makes the pack appear perfect, and such packs can then be copied
with dd(1). The technique used by this program is also less general than bad block forwarding, as badsect can't make amends for bad blocks
in the i-list of file systems or in swap areas.
On some disks, adding a sector which is suddenly bad to the bad sector table currently requires the running of the standard DEC formatter.
Thus to deal with a newly bad block or on disks where the drivers do not support the bad-blocking standard badsect may be used to good
effect.
badsect is used on a quiet file system in the following way: First mount the file system, and change to its root directory. Make a directory
BAD there. Run badsect giving as argument the BAD directory followed by all the bad sectors you wish to add. The sector numbers must be
relative to the beginning of the file system, but this is not hard as the system reports relative sector numbers in its console error mes-
sages. Then change back to the root directory, unmount the file system and run fsck(8) on the file system. The bad sectors should show up
in two files or in the bad sector files and the free list. Have fsck(8) remove files containing the offending bad sectors, but do not have
it remove the BAD/nnnnn files. This will leave the bad sectors in only the BAD files.
badsect works by giving the specified sector numbers in a mknod(2) system call, creating an illegal file whose first block address is the
block containing bad sector and whose name is the bad sector number. When it is discovered by fsck(8) it will ask ``HOLD BAD BLOCK ?'' A
positive response will cause fsck(8) to convert the inode to a regular file containing the bad block.
DIAGNOSTICS
badsect refuses to attach a block that resides in a critical area or is out of range of the file system. A warning is issued if the block is
already in use.
SEE ALSO bad144(8), fsck(8)HISTORY
The badsect command appeared in 4.1BSD.
BUGS
If more than one of the sectors in a file system fragment are bad, you should specify only one of them to badsect, as the blocks in the bad
sector files actually cover all the sectors in a file system fragment.
BSD June 5, 1993 BSD