04-02-2008
Things are still running as of today so I'm still puzzled about the extend of the damage. As root, I did a "cp -a" command and copied the entire 1.7+ TB out to another attached raid5 set.
Because this is a hardware raid set, can I assume that the OS just see this set as one single disk drive? In the past, when I had server with a corrupted system drive, I could just physically unplug the data drive and attach it to another running server, then mount this data drive on /mnt and all the data would be there. I'm wondering if I can treat this raid set the same way.
Many thanks for your kind responses.
10 More Discussions You Might Find Interesting
1. Solaris
I have two disks on a sun blade 100. I just installed a solaris8 on the first disk. The installation was successful. But the problem is now I lost all data / partition on my second hard disk.
The possible reason could be:
1. I used default web start install. During the installation I didn't... (2 Replies)
Discussion started by: motor98
2 Replies
2. Filesystems, Disks and Memory
hi,
I have a SCO unix server which has a 36gb hard drive, but the IT company who supplied it assigned 1gb to /dev/root, 15mb to /dev/boot and 33gb to /dev/u.
The /dev/root partition is now full, is there a way I can use the 33gb assigned to /dev/u without loosing any data, preferably... (2 Replies)
Discussion started by: Martyn
2 Replies
3. UNIX for Dummies Questions & Answers
Hello everyone -
Please forgive me if I violate the forum's etiquette as this is my very first post. I'm posting this on both the dummies and the advance section with the hope for any responses.
I stumbled on this forum while frantically looking for an answer to a dumb, ignorant thing I did... (2 Replies)
Discussion started by: kevindoman
2 Replies
4. UNIX for Dummies Questions & Answers
I have a FAT32 data disk attached to my Mac. It has 1 partition that is marked as bootable and the Mac tries to boot from it even though it has no OS on it. The man page for fdisk tells how to turn on the boot flag for a partition, but not how to remove it. Is there a way? Thanks! (0 Replies)
Discussion started by: jkorchok
0 Replies
5. Filesystems, Disks and Memory
Hello,
I have a RHEL system with two 500GB hard drives in RAID 1 (I think hardware, but not 100% certain - any way to tell?).
It looks like it was just set up in default configuration with a small boot partition and one huge partition for the rest, which composes a LVM volume.
I want... (1 Reply)
Discussion started by: builder88
1 Replies
6. Shell Programming and Scripting
Hi,
How can I run fdisk partition in a script without interactive input?
In manual procedure, I run fdisk device, select n, select p, presess enter for default start number (1), press enter to default end number, then select w for writing to the partition table. The command looks like... (3 Replies)
Discussion started by: hce
3 Replies
7. Red Hat
Hello,
I have been going through our environment and I see we have a few servers with LVM's setup and the file system type is still set to "83" within fdisk. If I change this to "8e", will it hurt the data or cause any loss? I need to know for sure before I make the change. (1 Reply)
Discussion started by: s ladd
1 Replies
8. Solaris
So, we removed a LUN from the SAN and the system is refusing to remove the references to it in the /dev folder. I've done the following:
devfsadm -Cv
powermt -q
luxadm -e offline <drive path>
luxadm probe
All those commands failed to remove the path. The drive stills shows up as <drive... (13 Replies)
Discussion started by: DustinT
13 Replies
9. UNIX for Advanced & Expert Users
Hello,
I have rebooted the RHEL VM but after rebooting the vm it not showing all the partition mounted on OS level, if i'll execute the fdisk -l command, then i'm able to see the same disk. below is the fdisk output :
# fdisk -l
Disk /dev/sda: 107.6 GB, 107639996416 bytes
255 heads, 63... (1 Reply)
Discussion started by: purushottamaher
1 Replies
10. Red Hat
Hi,
Please suggest steps to change grub from /dev/sda to /dev/sdb, (1 Reply)
Discussion started by: manoj.solaris
1 Replies
HD(4) Linux Programmer's Manual HD(4)
NAME
hd - MFM/IDE hard disk devices
DESCRIPTION
The hd* devices are block devices to access MFM/IDE hard disk drives in raw mode. The master drive on the primary IDE controller (major
device number 3) is hda; the slave drive is hdb. The master drive of the second controller (major device number 22) is hdc and the slave
hdd.
General IDE block device names have the form hdX, or hdXP, where X is a letter denoting the physical drive, and P is a number denoting the
partition on that physical drive. The first form, hdX, is used to address the whole drive. Partition numbers are assigned in the order
the partitions are discovered, and only nonempty, nonextended partitions get a number. However, partition numbers 1-4 are given to the
four partitions described in the MBR (the "primary" partitions), regardless of whether they are unused or extended. Thus, the first logi-
cal partition will be hdX5. Both DOS-type partitioning and BSD-disklabel partitioning are supported. You can have at most 63 partitions
on an IDE disk.
For example, /dev/hda refers to all of the first IDE drive in the system; and /dev/hdb3 refers to the third DOS "primary" partition on the
second one.
They are typically created by:
mknod -m 660 /dev/hda b 3 0
mknod -m 660 /dev/hda1 b 3 1
mknod -m 660 /dev/hda2 b 3 2
...
mknod -m 660 /dev/hda8 b 3 8
mknod -m 660 /dev/hdb b 3 64
mknod -m 660 /dev/hdb1 b 3 65
mknod -m 660 /dev/hdb2 b 3 66
...
mknod -m 660 /dev/hdb8 b 3 72
chown root:disk /dev/hd*
FILES
/dev/hd*
SEE ALSO
chown(1), mknod(1), sd(4), mount(8)
COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 1992-12-17 HD(4)