Sponsored Content
Full Discussion: Phone support
Operating Systems AIX Phone support Post 302215935 by ASSR on Thursday 17th of July 2008 01:59:02 PM
Old 07-17-2008
It 's sample problem from old server,hdisk2 fail already.
please check every entry,double check block number.

BLOCK NUMBER
51387528(from your posted error log)

if all block number same with this,it is mean a bad block problem only,you can ignore it.

otherwise you must replace this hdisk before it is gone.
 

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Phone dialer?

Dos someone know of a simple phone dialer I can use to paste in a phone number, and dial it? It's a lazy habit I got into using Dos, and Windows. Sonshyne5 (10 Replies)
Discussion started by: Sonshyne5
10 Replies

2. UNIX for Dummies Questions & Answers

Phone Dialer?

Is there a phone # dialer for Unix? I'm specifically looking for one in the OS X terminal, but I can run it through my FreeBSD computer too. --Andrew (0 Replies)
Discussion started by: andrewgray
0 Replies

3. Shell Programming and Scripting

Phone menu

Hello, Is there a way to read in user input inside a Here Document? The last line of the add(draft) file is supposed to redirect the user input to the phonebook file, but it is not doing that. I am not sure what I am doing wrong. So the redirected user input should be appended to the... (1 Reply)
Discussion started by: Dawg101
1 Replies

4. BSD

help mounting a phone!

hi, im completely new to bsd, but everything seems to work that bit better than under linux distros! im using pc-bsd, and need to get access to my sony ericsson k550i. i have a 2gig m2 card in it, and when the phone is switched off, it acts like a usb storage device apparently! it shows up in... (2 Replies)
Discussion started by: Fanny Zoddar
2 Replies

5. UNIX for Dummies Questions & Answers

Connecting a phone

I have an LG VX9800 (The V), am using Linux Mint, and just downloaded BitPim. The problem: BitPim doesn't detect my phone. Then again, the computer doesn't even do that. I read here (under Reference > USB > Linux USB Setup) about direct USB access, but Linux Mint apparently doesn't use hotplug. Or... (0 Replies)
Discussion started by: Zucriy Amsuna
0 Replies
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
All times are GMT -4. The time now is 06:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy