Red Hat

Hi

The output of the command is:

Code:

 fdisk -l /dev/sda

Disk /dev/sda: 32.2 GB, 32212254720 bytes
64 heads, 32 sectors/track, 30720 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Disk /dev/sda doesn't contain a valid partition table

this is a standalone server, but we want to attach a NetApp storage using iSCSI, so no FC adapters on it.
The NetApp will only be used to store backups, because this server does not have any backup functionality attached to it.

Hi,

The device you list "/dev/cciss" is actually a HP Smart Array device, the drivers for this were removed some time ago.

I'd have a look here to start your hunt for information.

Also, normally /dev/sda would be the first disk on a standalone server, so how is the server booted at the moment?

Regards

Gull04

the sys admin of that server, have configured 450G LUN and in there it was installed the operating system. That LUN of 450G is part of internal disks of the server.

Since you had the LUN added, have you re-scanned for devices (or rebooted). This link talks about CentOS7, but it should be pretty much the same. Perhaps the command kudzu might be an option too for RHEL5.

I find I always need to re-scan to get new/enlarged LUNs reflected in the OS.

I suspect that the LUN is not yet showing up, hence the confusion of the two disks you do have. I think that they are both local, one a simple disk, one a RAID device.



Robin

Hi Robin!

thanks for your inputs, I did a test with the help of the NetApp admin, which was to remove the LUN he presented onto the server, and present a bigger LUN, and to show or see the LUN on the server, I did run the following commands:

Code:

/etc/init.d/iscsi restart
iscsiadm -m session --rescan
fdisk -l | egrep '^Disk' | egrep -v 'dm-' | grep -v identifier

in this order, and the new bigger LUN show up.

Very good. Does it show the data/filesystems you are expecting?

If you are certain that they are not is use elsewhere, can you mount them?

If you are not sure, think carefully. Trying to mount them may just refuse, but it may possible say "Are you sure?" and then force it or just try and fails with a suggestion to fsck it. All of these could be very bad for your data. When sharing a LUN/filesystem(s) between servers, there is usually a need for good HA software. There are all sorts of problems, such as the free block list which will be held in memory, so if one side uses some free blocks, the other side doesn't know about it and could just use the same blocks causing data loss.



Kind regards,
Robin

that´s the problem:
If its new LUN, like the one the NetApp admin provided me for testing purposes, yes can go through the process of creating partition, etc, etc up to creating a file system and mount it. BUT if its LUN that has already data and use to be presented on another server, how do I mounted on the new server?