I had to reload a server for a client due to the primary drive being corrupt. Secondary drive is untouched and *should* have backups on it.
This is what I did to mount it without formatting it:
fdisk -l
mkdir /backup
mount /dev/sdb3 /backup
However, its ending up replicating (even in real-time) the primary drive, sda3 which is odd. How I know its replicating it is because Cpanel is currently being installed on the primary. Every few minutes I refresh the d -h output and both sizes on sda and sdb update to exact usage size. I even went into /backup and it looks like the primary which is odd.Code:Disk /dev/sda: 160.0 GB, 160000000000 bytes 255 heads, 63 sectors/track, 19452 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 13 104391 83 Linux /dev/sda2 14 144 1052257+ 82 Linux swap / Solaris /dev/sda3 145 19452 155091510 83 Linux Disk /dev/sdb: 80.0 GB, 80000000000 bytes 255 heads, 63 sectors/track, 9726 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdb1 * 1 13 104391 83 Linux /dev/sdb2 14 144 1052257+ 82 Linux swap / Solaris /dev/sdb3 145 9726 76967415 83 Linux
Why would this happen?
Code:mount /dev/sdb3 /backup [root@server092 home]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda3 72G 3.7G 64G 6% / /dev/sda1 99M 11M 83M 12% /boot tmpfs 252M 0 252M 0% /dev/shm /usr/tmpDSK 485M 13M 447M 3% /tmp /dev/sdb3 72G 3.7G 64G 6% /backup



LinkBack URL
About LinkBacks
Reply With Quote




