I’m getting this error on install: “The storage subsystem is locked by another application. Quit this application and continue”
Don’t know the application… just trying to install.
Network install.
Setup:
Intel DP45SG
Intel Q9450
Mushkin DD3 2G
WD 320G
Corsair 750W power
Any clues? Also, I’ve tried Debian, and it hangs on partitioning. I’ve unplugged all of the drive (all Sata) once I got to this screen hoping for a different error. Same error. Currently doing memtest.
Error Happens around probing phase at first. If you hit cancel enough, it’ll happen a lot more until it just fails (the intall).
Memtest came up Perfect. 22 passes over night and perfect.
Tried installing again in text mode and unplugged the mouse. (usb keyboard) and got Installed Failed. No reason. Just Failed.
Please, I beg, just give me some guidance. I’d hate to have to use windows out of pure inpatience.
-Tad
> Please, I beg, just give me some guidance. I’d hate to have to use
> windows out of pure inpatience.
why are you doing a network install…welll, never mind that…my
real idea/question is:
what has got your “storage subsystem” locked?
what is a “storage subsystem” anyway?
that is, is that “lock” error coming from the motherboard? the BIOS?
the kernel you are using to boot up with? the CPU? hard drive
controller? what?
i do wonder what you are booting with to do your network install? and
where in the install process you get that “storage subsystem” error…
guess what, google can find only ONE instance of “The storage
subsystem is locked by another application.” in the entire universe…
and it is in YOUR posting…apparently this has never happened to
anyone before, ever!!
which raises a few red flags in my mind:
is that board on the hardware compatibility list? what about the
chip set? http://en.opensuse.org/HCL/
that western digital drive–some are known to have problems with
all flavors of Linux–is it on the compatibility list?..
oh, is it an external USB drive? have you read other post in these
fora on external drives… is/was it your plan to install Linux on the
external and (maybe) have some other OS on the internal?
what did you mean when you said Debian hung on partitioning? did
you get an error
in your first posting you said: “I’ve unplugged all of the drive
(all Sata) once I got to this screen hoping for a different error.”
are you sure yours are hot-pluggable? *
back to your “I’d hate to have to use windows out of pure
inpatience.”: is this a brand new motherboard that has never had
Windows[tm] loaded on it? if so, how do you know it is a SUSE/Linux
problem? you might try loading M$ just to prove the board/mem/HD
actually work (if not, this would NOT be the first MB which never
worked after being put together)
sorry, i don’t know what to do next…
–
see caveat: http://tinyurl.com/6aagco
DenverD (Linux Counter 282315) via NNTP, Thunderbird 2.0.0.14, KDE
3.5.7, SUSE Linux 10.3, 2.6.22.18-0.2-default #1 SMP i686 athlon
*
“that is, is that “lock” error coming from the motherboard? the BIOS?
the kernel you are using to boot up with? the CPU? hard drive
controller? what?”
The “lock” error is given to be during the hardware probing stage at first. What is given me the error is a majority of my problem.
My board is a new board by Intel. Since the HCL was so limited, I did not find it.
However, I am wondering if my south bridge is causing the issue. Intel ICH10R. In the BIOS is has three configurations for it, IDE, RAID and AHCI. I’ve gotten the same problem on all three. It also appears that it is no loading drivers for my sata. It sees the drives, but appears to not write to the drive.
- what did you mean when you said Debian hung on partitioning? did
you get an error
No error. Just hung. Which leads me to believe the ICH10R controller is having driver issues.
your right. AHCI was NOT enabled.
new everything. Not blaming OpenSuse, blaming Linux. As of right now it severely looks like Driver issues with the new models. Have any boot commands to try? no ACPI or nomsi?
Completely Clueless right now.
ps.
guess what, google can find only ONE instance of “The storage
subsystem is locked by another application.” in the entire universe…
and it is in YOUR posting…apparently this has never happened to
anyone before, ever!!
Happened to someone else on 8-30-08ish. He posted on this forum, and no one answered him. Poor guy.
It’s been years since I’ve done a network install and there is more than one way to do it; what specifically are you using to boot the machine?
The boot kernels are not necessarily the same on all the various installation media. This can be important because if the kernel does not have compiled in the particular driver you need - as can happen installing to SATA drives (and happens in XP and Vista, as well) - the kernel must be instructed to load it from the modules library. It’s also possible that the kernel may need to be given a particular parameter to handle a machine’s unique hardware. Try adding this in the box below on the boot menu:
pci=nomsi
You may be successful using the DVD, which you can break out of to specify modules to load. Or the Live-CD, which for obvious reasons has more modules compiled into the kernel mainline. Linux veterans often keep a copy of the Knoppix Live-CD/DVD because he compiles nearly everything into the kernel precisely to ensure the best possible hardware recognition; once booted, commands can be used to identify the disk controller (the disks themselves are irrelevant) and kernel modules that are working with it. Are any of these alternatives an option for you?
BTW, I’m pretty sure the correct bios setting is AHCI; there is a kernel module of the same name.
I did some googling about and your P45 chipset should work; it houses an ICH10 controller. I saw that there are 2 versions of ICH10, 1 is ICH10R which supports RAID and, apparently, in some cases not AHCI. That is, needs to be configured in the bios as RAID even though not used as such. You may need to try several combinations, but of course again, you need to have a kernel that can load the modules. I also saw that with Intel’s AHCI implementation, the kernel argument above is sometimes required to workaround the PCI address not being available.
> 4) your right. AHCI was NOT enabled.
maybe something got fried when trying to hotplug when that was not an option
(because AHCI wasn’t working)…
–
see caveat: http://tinyurl.com/6aagco
DenverD (Linux Counter 282315) via NNTP, Thunderbird 2.0.0.14, KDE 3.5.7, SUSE
Linux 10.3, 2.6.22.18-0.2-default #1 SMP i686 athlon
Apparantly, the disc I was using was back from Beta and did NOT have the drivers for the ICH10R.
I got the DVD version and everything was Dandy.
My video card (8800GS) had some problems with drivers. The Repository wouldn’t Let me do the GL drivers, so I tried Legacy drivers. Put me in a way older kernel and didn’t work. Tried another thing, older kernel and startx wouldn’t work. And I think the three kernels were conflict after awhile so I just reinstalled, this time it let me use the GL drivers and I was good to go.
Wine was no problem. I even installed WoW and only had to configure it for OpenGL.
Over all once I got the right materials, everything seemed to work great! Gonna play around with some of the extra features.
Thanks for everyone’s help!
Tad
P.S.
maybe something got fried when trying to hotplug when that was not an option
(because AHCI wasn’t working)…
SATA is designed to not short anything out. The Motherboard just simply does not recognize ports when it starts up. Same concept with IDE. The cable will not short anything out. but the Molex will. The Sata power is designed to not short.
Have module, kernel boots . . . 
So, just for future ref, it was AHCI you needed afterall?
So, just for future ref, it was AHCI you needed afterall?
Raid. Even with a singular Drive.
Sorry, I wasn’t clear. I suspected since you have the ‘R’ the bios setting was RAID. My question was re the kernel module; is it still AHCI or ?
Can you refresh my memory? What is the command to glance at that? Plus I’m at work and don’t have access to my box.
lsmod will give you all loaded modules. It’s likely the module was automatically added to your initrd; those modules are in the file /etc/sysconfig/kernel on the INITRD_MODULES line (which is called by the mkinitrd script).