08-10-2012
If the backup is an image file of the original disk, then it may require the target to have the same disk geometry, or at least have the same number or sectors per track.
Can you explain the process of doing the restore (eg, I boot from, (hard disk 0, a dvd, a diskette) then run the following commands?
This User Gave Thanks to jgt For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi All,
Please check the below ftp related job, which is deleting the files from remote host. Problem is it is not capturing the ftp failure error, and the exit status is still '0' eventhough the deletable files are not present in remote location OR ftp credential are incorrect.
... (5 Replies)
Discussion started by: ganapati
5 Replies
2. Solaris
Hi Guys,
Anybody come across this error when formating a harddisk. "Reserved Failed"
Supected hardisk failure, is my assumption correct.
Thanks (5 Replies)
Discussion started by: bigmoon
5 Replies
3. HP-UX
Hi,
I have installed automake in one of HP-UX boxes using swinstall command. But when i issue automake it gives the following error message.
Can't locate loadable object for module IO in @INC (@INC contains: /usr/local/share/automake-1.10 /usr/local/lib/perl5/5.8.8/PA-RISC2.0... (1 Reply)
Discussion started by: chrisanto_2000
1 Replies
4. UNIX for Advanced & Expert Users
# netstat -a > /test/a
getnameinfo failed
getnameinfo failed
getnameinfo failed
getnameinfo failed
getnameinfo failed
command is working fine (as i get output in file /test/a)
# dig -x 10.xxx.xxx.xxx
; <<>> DiG 9.3.3rc2 <<>> -x 10.203.xxx.xxx
;; global... (0 Replies)
Discussion started by: crackthehit007
0 Replies
5. Solaris
Hi,
i got the following error when i tried to access the cygwin x server from a windows XP PC.
"xdmcp fatal error session failed session 23 failed for display"
Alternatively, when i tried to access the same Cygwin X Server from another windows XP PC which is on a different LAN... (3 Replies)
Discussion started by: HarishKumarM
3 Replies
6. Solaris
Hi
Could any one explain the meaning & purpose of below mention parameters in layman term. Suppose if we set below paramet what will happen.
error-reset-recovery=boot
error-reset-recovery=sync (3 Replies)
Discussion started by: sb200
3 Replies
7. Solaris
I have two servers with a fresh install of Solaris 11, and having problems when doing rpcinfo between them. There is no firewall involved, so everything should theoretically be getting through. Does anyone have any ideas? I did a lot of Google searches, and haven't found a working solution yet.
... (2 Replies)
Discussion started by: christr
2 Replies
8. Solaris
Hi
I tried to boot as single-user mode on my sunfire t1000 to change my root password since the guy has left the company without give us the root password.
anyhow since this machine not have attached with cd/dvd/usb so the only think that to do it through Jumpstart
now i tried to... (8 Replies)
Discussion started by: jmishal
8 Replies
9. UNIX for Advanced & Expert Users
I have created a windows server 2008 r2 Active Directory Server where I will create users. These users will be AD owners of data created on SUSE-OES server.
I am facing issue while while creating my suse-oes server account to ade server.
When I try to join my linux box to this windows AD... (0 Replies)
Discussion started by: rupeshkp728
0 Replies
10. HP-UX
I have a B.11.31 U ia64 system where I swremove the disk driver "SerialSCSI-00 B.11.31.1303 PCI-X/PCI-E SerialSCSI" (by mistake). afterwards the system won;t boot because of the missing disk drivers. I'm trying to recover my kernel by using the image HP-ux_11_31_disc_1.iso
Run an Expert... (1 Reply)
Discussion started by: black_fender
1 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)