06-18-2015
As I said, "ATA transport failed" and "I/O error" mean that your disk is broken.
You can as well verify with format -> select the disk -> analyze -> read
And then see the Error count in iostat -E for "dad1" (the kernel driver name for the "c0t0d0" disk, you can do iostat -nE to see the other name).
BTW the geometry matches a 20 GB disk; it is normal that the last sectors.of a disk or partition are unused.
Get a new disk! Restore your data or start an installation from scratch.
This User Gave Thanks to MadeInGermany For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
when installing a piece of third part software I get the error "Bad magic number" at one point when it tries to use libraries from the bea tuxedo server. Am I correct that this means that the software is expecting 32bit while I'm on 64bit? Is there a way around it or can it only be solved... (5 Replies)
Discussion started by: rein
5 Replies
2. Solaris
I tried rebooting my Sun server just a few minutes ago and I got the following at boot:
--
Sun Fire 280R (UltraSPARC-III+) , No Keyboard
Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.5, 1024 MB memory installed, Serial #xxxxxxxxx
Ethernet address... (6 Replies)
Discussion started by: deckard
6 Replies
3. Filesystems, Disks and Memory
Dear All,
i have a SCSI hard disk drive i'm installing on it solaris 5 and the workstation is sun sparc, i made an image of this H.D using Norton Ghost 6, so i took off the SCSI H.D from the sun workstation and put it on a Compaq server then i booted the server from the Norton Ghost floppy disk... (0 Replies)
Discussion started by: wesweshahaha
0 Replies
4. UNIX for Advanced & Expert Users
Hello All,
(RHEL4)
Few weeks ago I had posted a message in this forum about the problem I had when I replaced my two scsi disks and tried rebuild raid1 array.
I somehow managed to up the system with working raid1 array.
But the main problem persisted..
i.e when I reboot the system, mounting... (0 Replies)
Discussion started by: ravinandan
0 Replies
5. Solaris
Hello All,
I m very new to this forum.
i m having SUN NETRA X1 server with 40 GB HDD (Seagate) & 128 MB RAM.
i m trying this server for SUN 10 Practise.
As i m installing SUN 9 /10 with CD ,its giving me error after OK propmt
***************************
#boot cdrom
or
#boot cdrom... (16 Replies)
Discussion started by: amrut_k
16 Replies
6. Solaris
Hello,
I'm brand new to Sun/Solaris.
I have a Sun Blade 150, with SunOS 5.8.
I wanted to make a backup to prevent future data loss, so I put the disk in a normal PC with Windows XP to try to make a backup with Norton Ghost, the disk was detected, but not the file volume, so I place the disk... (6 Replies)
Discussion started by: Resadija
6 Replies
7. Solaris
I'll keep it fairly straight forward. I work with a Solaris server and magically today it decided to take a dump on me. At first it give a long list of files that couldn't be acessed before terminating the boot process and returning to the 'ok' prompt. Booting in single-user mode allowed me to run... (4 Replies)
Discussion started by: Aon
4 Replies
8. Solaris
I have created 1 LUN.
1)LUN 00BB 200GB /dev/rdsk/c1t3d44
/dev/rdsk/c2t28d44
/dev/rdsk/c3t19d44
/dev/rdsk/c4t12d44
2) Already added the new entry into sd.conf and rebooted.
3) Already done these:
powercf –q
power config
4) power display dev=all
I can see the new Symmetrix device.... (1 Reply)
Discussion started by: sirius20d
1 Replies
9. Solaris
Is there a way to recover label?
I could install (sparc) Solaris again, but it would take a lot of time. (5 Replies)
Discussion started by: orange47
5 Replies
10. Solaris
So we have a new to us v240 server with no OS installed. It has an outdated version of OB and ALOM so before we install the OS we want to update both. We have a DVD with the latest OB patch burned on it.
We do the boot cdrom command but receive the Bad Magic Number Error. Does an OS need to... (2 Replies)
Discussion started by: dunkpancakes
2 Replies
LEARN ABOUT NETBSD
diskpart
DISKPART(8) BSD System Manager's Manual DISKPART(8)
NAME
diskpart -- calculate default disk partition sizes
SYNOPSIS
diskpart [-d] [-p] [-s size] disk-type
DESCRIPTION
diskpart is used to calculate the disk partition sizes based on the default rules used at Berkeley.
Available options and operands:
-d An entry suitable for inclusion in the disk description file /etc/disktab is generated; for example, disktab(5).
-p Tables suitable for inclusion in a device driver are produced.
-s size The size of the disk may be limited to size with the -s option.
On disks that use bad144(8) type of bad-sector forwarding, space is normally left in the last partition on the disk for a bad sector forward-
ing table, although this space is not reflected in the tables produced. The space reserved is one track for the replicated copies of the ta-
ble and sufficient tracks to hold a pool of 126 sectors to which bad sectors are mapped. For more information, see bad144(8). The -s option
is intended for other controllers which reserve some space at the end of the disk for bad-sector replacements or other control areas, even if
not a multiple of cylinders.
The disk partition sizes are based on the total amount of space on the disk as given in the table below (all values are supplied in units of
sectors). The 'c' partition is, by convention, used to access the entire physical disk. The device driver tables include the space reserved
for the bad sector forwarding table in the 'c' partition; those used in the disktab and default formats exclude reserved tracks. In normal
operation, either the 'g' partition is used, or the 'd', 'e', and 'f' partitions are used. The 'g' and 'f' partitions are variable-sized,
occupying whatever space remains after allocation of the fixed sized partitions. If the disk is smaller than 20 Megabytes, then diskpart
aborts with the message ``disk too small, calculate by hand''.
Partition 20-60 MB 61-205 MB 206-355 MB 356+ MB
a 15884 15884 15884 15884
b 10032 33440 33440 66880
d 15884 15884 15884 15884
e unused 55936 55936 307200
h unused unused 291346 291346
If an unknown disk type is specified, diskpart will prompt for the required disk geometry information.
SEE ALSO
disktab(5), bad144(8)
HISTORY
The diskpart command appeared in 4.2BSD.
BUGS
Most default partition sizes are based on historical artifacts (like the RP06), and may result in unsatisfactory layouts.
When using the -d flag, alternative disk names are not included in the output.
BSD
June 6, 1993 BSD