09-22-2010
I got the information you asked:
Now, the OS is SCO OpenServer 5.0.7
About the hardware, i still don't have the information about the controller, all i know is that the broken HD is a Toshiba MK2018GAS and the new HD is a WD1200B EVE
I have an old image from the Toshiba. Now that Toshiba HD is broken, i restored the
image file to the new HD (Western Digital) and i get the errors bellow:
warning:hd:noroot disk controler was found
hd:a boot-time loadable driver may be required
h i init
panic:srmount fan-error19 mounting rootdev(1/42)
error 19 opening dumpdev(1/41)
dump not completed
safe to power off
The cpu is a PIII and i did't find any problems related to that.
As a newbie to SCO i can't bypass this problem and map the OS to new disc
Forgive me for my bad English.
Any help would be really grateful.
Panos
---------- Post updated at 08:41 PM ---------- Previous update was at 08:21 PM ----------
The new drive uses the same disk controller driver as the old one, however...
There are two issues that you will have to deal with. The first is the CMOS settings for how SATA drives are to be treated. You must use legacy mode, so that the disk appears to be the primary master.
Secondly, the disk geometry is different for the new drive. Use the biosgeom(cyl,heads,sectors) boot string to tell the kernel that the drive has a different number of cylinders heads and sectors. Use the native mode numbers, not LBA or LARGE.
After you have booted, use the "dparam" command to permanently change these values.
You said that the cpu is a P3. Are you using a non standard SATA controller?
As i understand and correct me if i a wrong, when you say CMOS settings do you
refer through BIOS settings? Legacy mode has to be configured through the BIOS?
10 More Discussions You Might Find Interesting
1. AIX
My root disk is failed and how to replace the root disk in AIX.
Can u give a detailed explanation in step wise.
Pls give the answer taking different scenarios.
Regards
Praveen (1 Reply)
Discussion started by: chinnu_mulakala
1 Replies
2. UNIX for Dummies Questions & Answers
Actually have a few different issues, wondering if I could get input on (tried reading/searching for an answer, with no luck)
1. Have a v240 running sol9 that needs a bad disk replaced. So, here are the steps I took:
a. detached from mirroring
b. cleared mirroring (metaclear)
c.... (4 Replies)
Discussion started by: mr.moralito
4 Replies
3. Filesystems, Disks and Memory
Good morning,
I have a problem replacing a disk with raid-5 volumes.
An hardware error was occurred from a disk c9t3 so all slices were in maintenace. Every slice is part of a raid-5 volume. Any replica is present.
Following Volume manager manual for replacing a disk, I have:
- phisically... (0 Replies)
Discussion started by: bonovox
0 Replies
4. Solaris
solaris os run on X86.
bootdisk have been mirrored.but there is one disk miss,I want to replace the fail disk,but after I replace the disk,the system can't boot!
pls help! (2 Replies)
Discussion started by: netxjman
2 Replies
5. Solaris
Dear all
Please can any one explain me how to replace failed disk in Solaris 10.
Please tell me the step by step procedure. (9 Replies)
Discussion started by: suneelieg
9 Replies
6. Solaris
-bash-3.00# zpool detach zonepool c1t1d0
cannot detach c1t1d0: only applicable to mirror and replacing vdevs
-bash-3.00# zpool remove zonepool c1t1d0
cannot remove c1t1d0: only inactive hot spares, cache, top-level, or log devices can be removed
-bash-3.00# zpool offline zonepool c1t1d0... (3 Replies)
Discussion started by: LittleLebowski
3 Replies
7. Ubuntu
Hi,
I have an Ubuntu system which I have an faulted mirror.
I trying to replace the disk, but I'm stuck on that it boots and only showing GRUB
GRUB
## ## End Default Options ##
title Ubuntu 8.04.4 LTS, kernel 2.6.24-26-server
root (hd0,0)
kernel ... (0 Replies)
Discussion started by: jld
0 Replies
8. HP-UX
Scenario1:
VG00 lvm,not mirrored,2 disk of 36GB vg size
VG00 size is under 30G.
Is possible to remove a disk of 36GB and replace "on fly"
with a disk of 300GB on VG00?
Thanks (6 Replies)
Discussion started by: Linusolaradm1
6 Replies
9. Solaris
issue,
I had a zpool which was full
pool_temp1 199G 197G 1.56G 99% ONLINE -
pool_temp2 199G 196G 3.09G 98% ONLINE -
as you can see, full
so I replaced with a larger disk.
zpool replace pool_temp1 c3t600144F0FF8BA036000058CC1DB80008d0s0... (2 Replies)
Discussion started by: rrodgers
2 Replies
10. Solaris
Hello,
I see hard and transport errors on all disks under treso pool and looks like some data corruption too. I want to take backup before, I reboot and replace disk. As of now, there are no slots free on server, so one option is, to break mirror, remove second disk (I need two disks, because... (5 Replies)
Discussion started by: solaris_1977
5 Replies
LEARN ABOUT CENTOS
mpartition
mpartition(1) General Commands Manual mpartition(1)
Name
mpartition - partition an MSDOS hard disk
Note of warning
This manpage has been automatically generated from mtools's texinfo documentation, and may not be entirely accurate or complete. See the
end of this man page for details.
Description
The mpartition command is used to create MS-DOS file systems as partitions. This is intended to be used on non-Linux systems, i.e. systems
where fdisk and easy access to SCSI devices are not available. This command only works on drives whose partition variable is set.
mpartition -p drive
mpartition -r drive
mpartition -I [-B bootSector] drive
mpartition -a drive
mpartition -d drive
mpartition -c [-s sectors] [-h heads]
[-t cylinders] [-v [-T type] [-b
begin] [-l length] [-f]
Mpartition supports the following operations:
p Prints a command line to recreate the partition for the drive. Nothing is printed if the partition for the drive is not defined, or
an inconsistency has been detected. If verbose (-v) is also set, prints the current partition table.
r Removes the partition described by drive.
I Initializes the partition table, and removes all partitions.
c Creates the partition described by drive.
a "Activates" the partition, i.e. makes it bootable. Only one partition can be bootable at a time.
d "Deactivates" the partition, i.e. makes it unbootable.
If no operation is given, the current settings are printed.
For partition creations, the following options are available:
s sectors
The number of sectors per track of the partition (which is also the number of sectors per track for the whole drive).
h heads
The number of heads of the partition (which is also the number of heads for the whole drive). By default, the geometry information
(number of sectors and heads) is figured out from neighboring partition table entries, or guessed from the size.
t cylinders
The number of cylinders of the partition (not the number of cylinders of the whole drive.
b begin
The starting offset of the partition, expressed in sectors. If begin is not given, mpartition lets the partition begin at the start
of the disk (partition number 1), or immediately after the end of the previous partition.
l length
The size (length) of the partition, expressed in sectors. If end is not given, mpartition figures out the size from the number of
sectors, heads and cylinders. If these are not given either, it gives the partition the biggest possible size, considering disk
size and start of the next partition.
The following option is available for all operation which modify the partition table:
f Usually, before writing back any changes to the partition, mpartition performs certain consistency checks, such as checking for
overlaps and proper alignment of the partitions. If any of these checks fails, the partition table is not changes. The -f allows
you to override these safeguards.
The following options are available for all operations:
v Together with -p prints the partition table as it is now (no change operation), or as it is after it is modified.
vv If the verbosity flag is given twice, mpartition will print out a hexdump of the partition table when reading it from and writing it
to the device.
The following option is available for partition table initialization:
B bootSector
Reads the template master boot record from file bootSector.
See Also
Mtools' texinfo doc
Viewing the texi doc
This manpage has been automatically generated from mtools's texinfo documentation. However, this process is only approximative, and some
items, such as crossreferences, footnotes and indices are lost in this translation process. Indeed, these items have no appropriate repre-
sentation in the manpage format. Moreover, not all information has been translated into the manpage version. Thus I strongly advise you
to use the original texinfo doc. See the end of this manpage for instructions how to view the texinfo doc.
* To generate a printable copy from the texinfo doc, run the following commands:
./configure; make dvi; dvips mtools.dvi
* To generate a html copy, run:
./configure; make html
A premade html can be found at `http://www.gnu.org/software/mtools/manual/mtools.html'
* To generate an info copy (browsable using emacs' info mode), run:
./configure; make info
The texinfo doc looks most pretty when printed or as html. Indeed, in the info version certain examples are difficult to read due to the
quoting conventions used in info.
mtools-4.0.18 09Jan13 mpartition(1)