I've just put together a Centos 5.2 system using an old Future Domain SCSI card which would allow me to hook up an external DAT drive. On its BIOS screen it advertises itself as an AHA-2920 which should be handled by the aic7xxx module. However, the module doesn't even get loaded unless I force it in /etc/rc.modules and even then it doesn't pick up the card.
View 2 RepliesI installed OpenSuse 11.4 (x86_64) a couple of days ago.One of my Drives a PC-DVD RAM (Creative) is not working. This worked under 11.3.The SCSI drive is connected to a PCI/SCSI adapter (AHA-2904).The message I see at boot is: ata_id[443]HDIO_GET_IDENTITY FAILED /dev/sr1I also see the message ata_piix not found, and can not find an option in the kernel
to provide this.his causes the system to wait a long time and slows down boot dramatically
In /proc/scsi/scsi, we can see the scsi host no. (scsi identifier no.). for e.g. Host: scsi4 Channel: 00 Id: 01 Lun: 00 In above e.g., scsi identifier no. is 4. Whenever we modprobe a particular module associated with scsi devices, we can see new entry in/proc/scsi/scsi with a greater identifier no. When we do rmmod on that module, the entry from /proc/scsi/scsi wipes off but still the counter of scsi identifier no. doesn't decreases. is is there any way to reset or decrement this counter so that next time when I do modprobe on scsi related module, it will assign no.s starting with 0 ? I found that during registering a scsi device, scsi_register() method gets value from "next_host" (which is a static int initialized to 0) and then increments next_host counter. Also, during scsi_unregister(), it decrements next_host counter. rmmod internally calls scsi_unregister(). So, if it is true then why the scsi host id. doesn't decrement during rmmod?
View 2 Replies View Relatedi am writing block deriver for usb device in linux i want to read and write data to/from usb device i already registered usb device with my driver and opened the handle for the usb device now i need to send scsi command to usb device to make it work but i dont have knowledge about scsi commands and how and where to use them now i need to know which scsi command i need to pass to the usb device and how can i pass that command to usb device also i need some information like how to register host controller with my usb driver
if anyone knows about this or where can find the tutorials / documentation/ framework for the same.
we need to connect 80pin SCA Ultra320 SCSI hdd to 68pin on host adapter. The adapter we got is Assmann ABSCA-2. Hard drive is 'Fujitsu MAW3073NC'
we have two 68pin cables, one with and one without the terminator on end. which one to use?
it is essential the drive doesn't get damaged.
I've recently put Ubuntu 11.04 onto an unused server with the plan of converting it into just a standard desktop PC, however it was lacking some of the basic components. After a struggle I managed to get an old Nvidia graphics card to work nicely and I bought a ?2 USB sound card from ebay and I've had no luck whatsoever in even getting it recognised.When plugged into windows the information given about the device is 'Generic USB Audio'I've restarted after each time I've tried to fix the issue and I've been mucking around a bit with ALSA following instructions from every forum post I could find but with no success
View 2 Replies View RelatedI have just set up a server with Ubuntu Server edition 10.04. I installed it by plugging the harddrive into my main pc as the server doesn't have a cd drive. Now the drive is back in the server and the internet won't work. I have run lspci and lshw and neither show a lan or network card anywhere. ifconfig comes up with nothing related to eth0, and says the 'inet addr' is 127.0.0.1. My motherboard has an onboard Realtek 8101L LAN controller. Can't seem to find much with a google search
View 2 Replies View RelatedI'm running FC 12, on a Pentium III PC. This has a 440BX motherboard with an AWE64 Gold ISA card. It wasn't recognised at boot up, I've installed the GUI ALSA mixer, inisitally it shows no sound device.Searching around the forums stumbled across the command:modprobe snd-sbaweThis one line command worked fine (no errors), enabled the volume control, and ALSA mixer GUI gave loads of nice sliders. Pushing these up I found that basic sound was working fine (eg playing Flash video within Firefox). I don't need any other features of the AWE64 right now (might like MIDI port one day).
However, each time I reboot the system it forgets, and I have to run the comand again (and tweak up the volume in the mixer, particularly for PCM).I tried adding a file called awe64 in /etc/init.d, with the contents:
#!/bin/bash
#modprobe snd-abawe
(and chmod +x awe64) but this doesn't seem to get run, or has no effect.I tried adding a file to /etc/modprobe.d but this just gave errors - I think this is the right approach though.What should I do please?
I'm installing my first new Dell SCSI controller card (PERC 6) and storage array (MD1000) into my first RHEL server. I've done this plenty of times in a Windows world, but never in Linux. I know the BIOS will pick up the SCSI card and I can go into that during the boot screen to set up how i want the array (RAID5), but once Linux comes up, will it automatically find and mount the drives, or do I have to do something?
View 9 Replies View Relatedwhat is the model of virtual scsi card in vbox? where to find drivers for it?
View 1 Replies View RelatedDoes anyone have knowledge of where I can get drivers for above card?
View 1 Replies View Relatedi m facing same error in most of the HCL servers. the problem is that it throws error while booting and sometimes not throws error. the error is :-
Feb 13 13:17:25 fe13s kernel: Adapter 0: Bus A: The SCSI controller was reset due to SCSI BUS noise or an invalid signal. Check cables, termination, termpower, LVDS operation, etc.
Feb 13 13:17:30 fe13s kernel: Adapter 0: Bus B: The SCSI controller successfully recovered from a SCSI BUS issue. The issue may still be present on the BUS. Check cables, termination, termpower, LVDS operation, etc
Feb 13 13:29:15 fe13s kernel: Adapter 0: Bus B: The SCSI controller successfully recovered from a SCSI BUS issue. The issue may still be present on the BUS. Check cables, termination, termpower, LVDS operation, etc
code....
In my understanding, the way /proc/scsi/scsi gets populated, /proc/paritions also gets populated in the same fashion. i.e. the description for first entry of /proc/scsi/scsi can be seen in the first entry of /proc/partitions and same for rest.
So, With this assumption, in my project, I used to relate first entry of /proc/scsi/scsi with first entry of /proc/partitions to get its total size and same for all entries.
But, I observed some differences in following scenario, where
1) The first 4 entries in /proc/scsi/scsi are SAN luns attached to my system and for which the actual device names in /dev/ are sda,sdb,sdc and sdd.
2) The last 4 entries are the internal HDDs on same system. In /dev/, their respective device names are sde,sdf,sdg & sdh.
(Output attached at end of the thread)
But in /proc/partitions, the device order is different.
You can see their respective sizes in /proc/partition output as well.
So, my question is, in this particular scenario, I can't relate the first entry of /proc/scsi/scsi with first entry of /proc/partition. i.e. scsi0:00:00:00 is not /dev/sde, because it is actually /dev/sda.
It seems that my assumption is wrong in this scenario.
Is there any way or mechanism to figure out actual device name for an entry in /proc/scsi/scsi in /dev/ directory?
How can my application should relate /proc/scsi/scsi entries with their respective device names and sizes?
When I enter "cat /proc/scsi/scsi" I'm returned with "cat: /proc/scsi/scsi: No such file or directory". I've tried this on two different installs on two different machines.
View 6 Replies View RelatedWe ran out of space on our server hard drive, so I installed 2 x 1GB drives, set them up as a software RAID1 array, copied the contents of /home to it, mounted it as /home for testing. Everything OK, so I unmounted it,deleted the contents of the /home folders (don't worry, we're backed up), then remounted the array. Everything was fine until we rebooted.Now I can't access the array at all; during booting the error "mount: special device /dev/md1 does not exist" comes up twice, and manually trying toe same issue.The relevant line from fstab reads:/dev/md1 /home ext3 defaults 0 0.However, using webmin shows only md0, the RAID0 device on which the OSD was originally installed.There is no /dev/md1 device file.The mdadm.conf file reads as follows:
# mdadm.conf written out by anaconda
DEVICE partitions
MAILADDR root
ARRAY /dev/md0 level=raid0 num-devices=2 uuid=76fd4050:fb820568:c9bd3a59:ad3e70b0
Having a problem after a crash.Replaced system disk re-installed version 5.6.Now it does not recognise the RAID-disk connected to a SIL 3114 RAID-controller.Anyone have any ideas what to do.I can see both disks as sda and sdb, although the raid-controller reports them as a raid-set.Both disks are obviously reported with unknown partitions.Previously I used version 5.5, cant remeber any problems when I added the RAID.
View 7 Replies View RelatedSome of our workstations have LTO's attached and they seem to drop off every now and again, the only thing which picks them up again (besides a reboot) is the famous rescan-scsi-bus script from here
The thing is that I'd like non-root users to be able to run this script, which in turn needs root to /proc/scsi/scsi
I am running a server that needs both a wired and wireless connection with static IPs, with wireless as the default link. I'm using the SMCWUSB-G for wireless. I was running Debian for a while and had some routing tables set up as in [URL].... Everything worked until I recently switched to Ubuntu Server 9.10. After the switch a weird behavior showed up: if wlan0 is down, eth0 works fine. But if wlan0 is up, I can't reach any host with either interface (even nameservers or the gateway I am supposedly connected to). ifconfig indicates that nothing is wrong. It's really not clear what is causing this problem. It seems like something has to be wrong with both the wireless hardware/drivers and the routing tables in order for turning wireless on to interfere with "ping -Ieth0".
[code]...
I just installed centos 5 on a hp dl380 server and it has 2 72.8 scsi gig hard drives. The problem I am having is that only one hard drive is being recognized and it is not being recognized as a scsi. This is what I get from fdisk -l
Disk /dev/cciss/c0d0: 72.8 GB, 72833679360 bytes
255 heads, 63 sectors/track, 8854 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/cciss/c0d0p1 * 1 13 104391 83 Linux
/dev/cciss/c0d0p2 14 8854 71015332+ 8e Linux LVM
as you can see, the system doesn't even see the second hard drive. How do I get both hard drives to be seen and how do I get them to be recognized as scsi?
I've managed to install Centos 5.3 (with Gnome) from a temporary IDE-based CD drive. This has now been removed and, instead, I have added a SCSI-based Panasonic LF-D201 DVD-RAM drive onto channel-B of the Intel SRCU32 (LSI clone) SCSI RAID card.
it seems that Centos cannot see the DVD-RAM drive at all - not even as a simple CD drive.
I added two scsi disk, but it is not listed in /dev. But the controller information is available from lspci code...
View 4 Replies View RelatedCan an unattended Kickstart support both IDE (hda) and SCSI (sda)? The goal is to to create a new virtual machine from scratch. What I have works for Parallels in which a new VM defaults to emulate an IDE hard disk. It does not work for VMware Workstation which defaults to emulate a SCSI disk.
The relevant Kickstart section: bootloader --location=mbr --driveorder=hda --append="rhgb quiet"
clearpart --all --initlabel --linux --drives=hda
part /boot --fstype ext3 --size=100 --ondisk=hda
part pv.2 --size=0 --grow --ondisk=hda
volgroup VolGroup00 --pesize=32768 pv.2
logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow
logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=1024 --grow --maxsize=2048
Can the Kickstart file be made to not care what drive type is there, or conditionally handle either type?
I am looking for a way to partition 2 disks automatically with are both connected to 2 different scsi controllers.
I want one disk on one controller to be partitioned with boot and lvm and the other one with a different partition layout.
I there a way in kickstart to do this, like for instance specify the drive module?
Client has a server running 5.5 (I think) and it they moved locations. This server is used in other locations (state) via ssh tunnel as well so they can all access files.
When attempting to boot up I get screenshot 1 (superblock errors)[url]
They supposedly have a backup on a hot swap scsi and I want to know how/if I can restore it using that backup if I cant fix the superblock boot/error issue.
I took some other screenshots:
[url]
[url]
[url]
I have a linux router with 2 physical ISPs and a VPN tunnel that all my traffic passes through. I would like to setup a rule to redirect all traffic from one internal IP address (10.0.0.x) through the physical link only. My current script is as follows.
iptables -F
iptables -X
echo 1 > /proc/sys/net/ipv4/ip_forward
[code]....
My goal is to do something similar to the mangle on the tor traffic, but for an entire host.
I have installed CentOS 5.4 machine named test.example.com (192.168.1.1)File /etc/hosts contains:127.0.0.1 test.example.com test localhost.localdomain localhostI have read that the loopback addres should not be assigned to host name,only to localhost and the host name should be assigned to 192.168.1.1, like this:127.0.0.1 localhost.localdomain localhost192.168.1.1 test.example.com testIs there any reason why it should be one or another way?
View 6 Replies View RelatedWe just setup a HP DL380 with CentOS 5, and ran all of the latest updates.I am trying to attach a Compaq array (no model number) that is SCSI attached. I can see the array from the bios and created a raid group on it from there. However, from LVM and lvscan, I don't see it at all. I checked dmesg and there are no errors.Also, interestingly /proc/scsi/scsi is empty.
View 1 Replies View RelatedHas anyone successfully used an Adaptec 2100S in a RAID configuration? Specifically, RAID1?
Drivers exist for earlier version of Red Hat, but building an using a driver disk results in the error:
Driver disk is invalid for this release of CentOS
CentOS does not recognize the adapter out-of-the-box as a HW RAID controller, but does recognize the individual disks.
I attempted to use software RAID, but the installer craps-out after a while and the screen locks up.
My Ubuntu Box has 3 interfaces. eth0 (Internal 192.168.1.0/24)eth1 (External ISP DHCP)eth2 (External ISP Static IP)I need the outgoing traffic to internet for 1 of the internal pc (192.168.1.10) to only go only go through eth2
View 4 Replies View RelatedDoes CentOS 5 support HP EH854A LTO4 External SCSI tape drive?
View 3 Replies View Related