I'm just curious more than anything. With me having a hard drive in the bay does the system ignore the eject command for that drive as long as it remains there?
I.E. If I upgrade the OSD drivers (reported to have working eject now) will the system "eject" the hard drive in the bay or will it just disregard the button?
-
As far as I know the OSD is purely software "shortcuts", which is why it doesn't even work outside of Windows. Now, taking into account Windows won't detect any Optical Drives I think it'll just look for the command and ignore it once it doesn't find it.
Worst case scenario you might get a bluescreen of some sort, but we'll never know unless you give it a shot -
Well actually the drive houses one drive in a raid 0 pair. Worse case scenario is that it corrupts the array but yea I suspect it will just ignore it then. I started copying about 300GB to an external drive and just realized just how much of a boost Raid 0 really did give.
Internal array -- ~10% activity
External eSATA drive - ~100% activity
-
No, pressing the eject command will not do anything to the hard drives. The OSD eject command is mapped to eject the discs from the optical drive. It is not mapped to a specific SATA port. I've got my RAID 0 setup just like yours and I've pressed the OSD eject button multiple times. Nothing happens if there isn't an ODD drive connected to the system. No errors, no BSODs.
OSD drivers with hard drive in optical drive bay
Discussion in 'Alienware 17 and M17x' started by shinji257, Feb 12, 2013.