01-08-2014
It looks like the boot disk is faulty.
So trying to clone it is a good idea.
If that is successful, replace the disk by the clone disk.
Furthermore, (if not successful,) an expensive SCSI disk has a possibility to "repair" a sector (remap to a spare sector). The contents of a "repair"ed sector is unknown, that can mean a little data loss/corruption. (That's why everyone says: re-install the OS, then restore from last data backup.)
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I am not getting login prompt when connecting to the red hat linux 7.2 server from windows machine and i am unable to login to server, after giving username at login prompt cusor blinks, no respnse. I can able to login to server thro ssh.
Pl can i know how to solve this problem.
Very badly... (4 Replies)
Discussion started by: bache_gowda
4 Replies
2. UNIX for Dummies Questions & Answers
Hi...
Can anyone help! I am in dire need to change the "login:" prompt to "username:" any ideas?
Thanks in advance :) (6 Replies)
Discussion started by: juilan
6 Replies
3. UNIX for Dummies Questions & Answers
Hello
When I login as root - my prompt is # I want to change this and I understand the setting (PS1=) needs to go into a file called .profile, but I don't know where this file is for the root user. The root users home folder is / when I type env.
Should I be creating a home folder for the... (4 Replies)
Discussion started by: deedaz
4 Replies
4. Linux
Hi, We currently have a problem on a centos server when i try to ssh to it there is a significant delay in getting a login prompt. What would be the steps in troubleshooting this issue? I have try to narrow down a possible network issue but cannot see anything obviously wrong in the routing table,... (4 Replies)
Discussion started by: borderblaster
4 Replies
5. Solaris
Hi All,
I have created a new user. Using the below command I have created the user successfully.
useradd -c "Test user" -d /tmp/test -g Testgroup -s /bin/ksh -u 601 Test
I don't want to set the password using “passwd” command after creating a user.
I want to prompt for the new... (2 Replies)
Discussion started by: kalpeer
2 Replies
6. Ubuntu
Hi Team,
I am using DRBL environment on Ubuntu. When my machine starts some times it's not starting lxdm & nslcd service. Because of that i didn't get graphic mode & also not able to authenticate user as nslcd is also stops. I have to login as root and restart these two services, then i am able... (0 Replies)
Discussion started by: paragnehete
0 Replies
7. Shell Programming and Scripting
Hi,
How i can pass the login details to the URL which is password protected with the htaccess using command line or script (perl,or shell,or php).
Any help or hint appreciated.
Thanks,
SJ (4 Replies)
Discussion started by: SilvesterJ
4 Replies
8. Shell Programming and Scripting
Hey guys, trying to create a script that will run in the background until a user logs in and then present them with different options to proceed further.
It is on an Ubuntu 10.04 Amazon ec2 system.
The system runs 24/7 as it is and just needs to feed the prompt to whoever logs in.
Is this... (3 Replies)
Discussion started by: 3therk1ll
3 Replies
9. HP-UX
Hi, I'm a normal user in hp-ux box. today i'm unable to get prompt after i successfully logged in into the hp-ux box. what could be the problem? what should should i check? (4 Replies)
Discussion started by: sam_bd
4 Replies
10. HP-UX
When I login as root or any user it prompts for the Login again. never prompts for password.login: root
Login incorrect
login:
Does not matter what user login I try I get the same response (3 Replies)
Discussion started by: KMRWHUNTER
3 Replies
BAD144(8) System Manager's Manual BAD144(8)
NAME
bad144 - read/write DEC standard 144 bad sector information
SYNOPSIS
bad144 disktype disk [ sno [ bad ... ] ]
DESCRIPTION
Bad144 can be used to inspect the information stored on a disk that is used by the disk drivers to implement bad sector forwarding. The
format of the information is specified by DEC standard 144, as follows.
The bad sector information is located in the first 5 even numbered sectors of the last track of the disk pack. There are five identical
copies of the information, described by the dkbad structure. Only the first of these copies is used.
Replacement sectors are allocated starting with the first sector before the bad sector information and working backwards towards the begin-
ning of the disk. A maximum of 126 bad sectors can be supported. The position of the bad sector in the bad sector table determines which
replacement sector it corresponds to.
The bad sector information and replacement sectors are conventionally only accessible through the ``h'' file system partition of the disk.
If that partition is used for a file system, the user is responsible for making sure that it does not overlap the bad sector information or
any replacement sectors.
The bad sector structure is as follows:
struct dkbad {
long bt_csn; /* cartridge serial number */
u_short bt_mbz; /* unused; should be 0 */
u_short bt_flag; /* -1 => alignment cartridge */
struct bt_bad {
u_short bt_cyl; /* cylinder number of bad sector */
u_short bt_trksec; /* track and sector number */
} bt_bad[MAXBAD];
};
Unused slots in the bt_bad array are filled with all bits set, a putatively illegal value. MAXBAD (in <sys/dkbad.h>) may be tuned locally
to reduce the space required to hold the bad-sector file in memory. It may not be greater than 126, which uses the whole disk sector. Bad
sectors past MAXBAD may be included by the formatter, but replacement sectors will not be used until MAXBAD is increased.
Bad144 is invoked by giving a device type (e.g. rk07, rm03, rm05, etc.), and a device name (e.g. hk0, hp1, etc.). It reads the first sec-
tor of the last track of the corresponding disk and prints out the bad sector information. It may also be invoked giving a serial number
for the pack and a list of bad sectors, and will then write the supplied information onto the same location. Note, however, that bad144
does not arrange for the specified sectors to be marked bad in this case. This option should only be used to restore known bad sector
information which was destroyed.
New bad sectors can be added by running the standard DEC formatter in section ``bad.''
SEE ALSO
badsect(8)
BUGS
Not all drivers support bad-sector forwarding on the PDP-11.
It should be possible to both format disks on-line under UNIX and to change the bad sector information, marking new bad sectors, without
running a standalone program.
The bootstrap drivers used to boot the system do not understand bad sectors or handle ECC errors. This means that none of these errors can
occur when reading the file /unix to boot. Sector 0 of the disk drive and the file /boot in the root file system of that drive must also
not have any of these errors in it.
The drivers that write a system core image on disk after a crash do not handle errors; thus the crash dump area must be free of errors and
bad sectors.
3rd Berkeley Distribution BAD144(8)