simply fdisk -l is the way to find out which are the new disk. If the disk are presented from SAN they wont have any partion table and hence doing fdisk /dev/<sd*> will make it clear. If you need to reboot the server from viewing the disks there is some issue with the storage system or the way it is being presented.
Really old post guys sorry.
I finaly have time to do this but I noticed when i mount sdc1 it is exactly the same as sdd1:
RCWLO-ODS10g:/NEWSAN/backup # df -k /NEWSAN
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdc1 1373587836 683999232 689588604 50% /NEWSAN
RCWLO-ODS10g:/NEWSAN/backup # df -k /SAN
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdd1 1373587836 683999232 689588604 50% /SAN
RCWLO-ODS10g:/NEWSAN/backup #
Does this mean sdc1 is the mirror of sdd1?
RCWLO-ODS10g:/NEWSAN/backup # fdisk -l
Disk /dev/sda: 72.9 GB, 72999763968 bytes
255 heads, 63 sectors/track, 8875 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 2624 20972857+ 83 Linux
/dev/sda3 2625 4583 15735667+ 83 Linux
/dev/sda4 4584 8875 34475490 82 Linux swap / Solaris
Disk /dev/sdb: 145.9 GB, 145999527936 bytes
255 heads, 63 sectors/track, 17750 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 1 4178 33559753+ 83 Linux
/dev/sdb2 4179 5484 10490445 83 Linux
/dev/sdb3 5485 17750 98526645 83 Linux
Disk /dev/sdc: 1406.6 GB, 1406601789440 bytes
255 heads, 63 sectors/track, 171009 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 1 171009 1373629761 83 Linux
Disk /dev/sdd: 1406.6 GB, 1406601789440 bytes
255 heads, 63 sectors/track, 171009 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdd1 1 171009 1373629761 83 Linux
Any assistance would be appreciated.
Thanks
Have you managed to ask the service technicians what the capacity of the disk was and where it came from? That would help a LOT. Right now all we're doing is guessing.
It may be a mirror. Do you have a /dev/md0, md1, etc? That's a software RAID device that combines multiple disks into one device. Try 'cat /proc/mdstat'
Yes it's 1 TB.
We just rebooted the server and fdisk -l still doesn't show any new disk. Its the same as before.
Maybe there's something wrong with how it's connected to the server? Not too sure.
If there is, Linux couldn't tell you. How's it supposed to tell you what's wrong with a disk it can't see? Someone needs to do some basic hardware troubleshooting on this system. We don't even know if the BIOS sees this drive. We don't even know what the drive is except it's "terabyte".
1 Like
All sorted out.
The Tech didn't have it set up properly. Big surprise. He said 'Hold on a sec... ok try it now' and fdisk -l showed the new disk.
I created the partition, mounted it and got all my Oracle data moved over.
Thanks for all who helped me with this.
1 Like