When I installed DSS V6, I used cfdisk to create a 2GB primary boot partition to install DSS, plus a second partition for the rest of the space. I was hoping to set up a volume group on the remaining space, but when i click on Unit Rescan, it does not show up at all. Is it because I created that second partition when I should have left it as unallocated space? If so, how do I get to cfdisk to remove the second partition? Now that DSS is installed, I cannot seem to boot with the install CD to get to cfdisk.
The logical disk and its physical disks show up correctly under Setup > H/W Raid.
I do not think it is a problem with the RAID controller (LSI) because I have a second logical disk (which I did not create a partition on) that shows up as available under Unit Manager.
I managed to boot from the DSS V6 install CD again (just had to hit F11 to get a boot menu) and ran cfdisk to remove the second partition that I had created originally. (I don't know if it is supposed to be there or not.) After rebooting, running Unit Rescan still did not show an available unit to create a volume on.
I think I am doing exactly what the manual says:
Only RAID controllers with multiple LUN support can be used. Please create a small 2GB logical unit for DSS V6. Running DSS V6 installer you will need to select this 2GB logical unit as the boot media. On the rest of RAID space please create second LUN for the user data. ...
Why would DSS Unit Rescan not find that second LUN?
OK, I got this working by rebuilding my RAID card's "Virtual Drive" setup. This time I set up a 2.2GB virtual drive dedicated for DSS and another virtual drive for the rest. Then I reinstalled VSS and it saw all of the available LUNs. This time I didn't use cfdisk because it was not needed in this scenario--I just let the VSS installer create its own partition.
I guess I was getting LUNs and partitions mixed up.
Partition not showing up in Unit Manager
Reply With Quote
