Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I think I have a big problem. I went to loggin to my Win 2k server, and I saw a message stating that my Samba Shares on my File server were not loading. WTF??? So I KVM over to that box, and find that I have the following message:
AmiRaid: HyperDisk driver version 01.01.07
AmiRaid: HyperDisk Firmware Version 2.4.0.919168
AmiRaid: ERROR: no controler found, driver exiting.
/lib/amiraid.o: init_module: Device or resource busy
autodetecting RAID arrays
autorun...
...autorun DONE
kmod: failed to exec /sbin/modprobe -s -k block-major-101, errno=2
VFS: Cannot open root device 65:01
Kernel Panic: VFS: unable to mount root fs on 65:01
Can someone tell me what is up? I kinda think my RAID controler has went out. What does this mean for my array if it has? Any help would be very much appreciated.
No controller found would be refrring to the ata controller of the drive itself as the kernel saw the Ami controller. I've had similar problems when using multiple ata controllers in one box (well only since the Promise Ultra/100 Tx2 - Ultra/66 cards are very well-behaved).
Check cabling, drive tempertatures and do a 'cat /proc/iterrupts' and lspci -vb' to see how your hardware showed up on boot.
RAID0? I hope there was nothing important on that rig.
By the way, getting the new motherboard is what fixed the issue. My other motherboard was fried by too much dust accumulating on AGP slot. You could see the burn marks..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.