This content has been marked as final. Show 13 replies
You are correct, this is not possible because the CCISS driver has changed between 3.0 and 3.1, and to your point, will not function. I dont know of any workaround for this, we are in the same position with a few 3.0.3 standalone machines that we can't upgrade.
We are in almost an identical situation, except using 300GB SAS drives. I found that "Bug" related to SAS drives not being supported, but don't know if this is something that is going to be fixed in the near future or what.... Either way, its a huge pain point for us as we are going to have to stand something up with SATA drives, or pay a considerable amount for a SAN.
I guess the workaround is just leave them on 3.0.3 - that is what I have chosen to do for my particular implementation. I will open an SR with Oracle to hopefully get some idea of when/if this issue will be addressed.
We got an even worse situation. We are gonna use a G8 server and internal disks. So its only supported on version 3.1.1 but since the driver changed in that version local storage isn't supported anymore :(
What do you plan on doing for resolution? I've got an open SR right now, and according to the technician that is working it, it doesn't appear that this "Bug" will be addressed at all.
Why dont you direct them to this thread, as were probably a small snapshot of people complaining, but the likelihood is there are alot more going to complain as they try to upgrade a WORKING 3.0.X setup on the same hardware to a now NON WORKING 3.1 setup.
I think that's pretty obvious that its a bug, maybe not a bug in the driver, but a bug that Oracle included a incompatible driver which broke previously functioning functionality.
I've already directed the tech working it to this thread :)
Here is what I got from the technician:
"Ok, I reviewed the thread and that person is using a HP Smart Array P410i controller and SAS disks.
The thing is these are SAS disks that are local to the system, and that's not supported on OVM 3.1.1. Also it seems there is no plan to support that."
This doesn't look good for us.
I got the same problem and received the exact same message from oracle support.
We need more people to open S/R's about this so they know its feature people would like to get back
I agree. For small implementations, local raid 5 really does make sense. A SAN really isn't an option for lots of companies because they are so expensive. Small implementations often don't need that high ability option.
It's been a couple months since the last update of the thread, but i think the problem is still unresolved and it seems Oracle is not planning on supporting local sas disks.
We're using IBM X3550M3 servers and already opened an SR and got the same response.
We need to install new environments and still can't decide which OVM version to use, what's interesting though, is that the problem is mentioned on both 3.0.3 and 3.1.1 documentation:
6.4.3. Local SAS Hard Disks Not Supported for Storage
7.5.10. SAS Disks Only Supported in Shared Configuration (SAS SAN)
But you mention that it works on 3.0.3, and it seems that other people got it working too. We updated the SR to ask about support on 3.0.3 but got no response yet.
A workaround is to export your local disks in dom0 by NFS and then access them through SAN generic file server.
I wouldn't recommend this for a production system though.
Have you tried this lately, Ive noticed on the last kernel upgrade they issues (200.1.9), my HP CCISS devices turned back to general /dev/sdX devices, which should work normally. I have not tried on my DL380, but I did witness this transition on my DL585's while apply the latest errata.