Hardware :: Scsi Device Is Not Available In Enclosure After Hot Plugging
Jan 15, 2010
One of my servers contains two scsi enclosures. After hot removing a disk and hot adding another the new disk gets assigned a device file but the enclosure (in sysfs) doesn't want to see it.
How can I force the enclosure to recognise the hot added disk.
Situation in sysfs:
The link device is dead after hot removing the device and keeps vanished after hot adding the new device. The hot added device gets assigned a device file and it is reachable. Even
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?
Since May 12,2009. Our system lifekeeper has the error log "lifekeeper error: DEVICE FAILURE on SCSI device '/dev/add'", but it ran normally. Until last week, it failover to the standby server. The disk still running, the error still come out.
Have tried to find an answer over at over LoCo (Sweden) with no result...Does anyone know how to stop Banshee from autostarts when I plug in a USB-drive, my iPhone or what-so-ever! Banshee even autostarts when I'm doing a "Connect to server" O_oHave even googled for it, with no result and it's bugging me off real hard that Banshee autostarts!Edit: If I remove Banshee, and still plugs a device in it now autostarts in qmm
Changing the brightness and keyboard brightness does not give a notification, though the brightness changes. In addition, ejecting a cd, plugging in a usb device, and seeking/playing music gives no notification (though Rhythmbox tells me what track I've skipped to/played). Again, the cd does eject, the usb device can be accessed, etc. I'm not sure if this last one is a problem, but every notification except for the volume one appears about 80 pixels down from the top panel. This 80 pixels below the panel is only ever occupied by the volume notification. Ubuntu 10.04, gnome-power-manager 2.30.0 ubuntu1, notify-osd 0.9.29-0ubuntu2. I'm using a Dell Studio 1555 notebook.
I am attaching a LTO-3 tape drivce into my RHEL5 linux machine. Every time i used to restart my machine to detect the tape drive is there any way to rescan the buses to detect the newly attached scsi devices. In solaris "devfsadm" and "iostat" is there. I need the same kind of thing in linux.
I created a new disk on our scsi san. I then ran the following command: echo "- - -" > /sys/class/scsi_host/host1/scan. did that command for each host. and in dmesg, it shows it found a device /dev/sdg. but when i do a fdisk -l. It never lists /dev/sdg. I just did this other day on another server and it worked fine like that. This is RH 4.8.
I am developing for a Linux based device for which the HOT PLUG option is deactivated. As part of optimizing the code, we also don't want to create device files for unused devices. We understand that both USB attached and fixec SCSI hard disks would create device files like /dev/sda,/dev/sda1 /dev/sdb, /dev/sdb1 etc. Is this understanding correct?
In the case of USB attached SCSI devices, would driver create this device file entry? How is it created? Can somebody please tell me how it is being created automatically. In case I attach a fixed SCSI hard disk before boot up(and create device file /dev/sda1), would USB SCSI device driver create device files starting from /dev/sdb, automatically.
i 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....
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.
Some 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 have a 3.5" SATA disk in an external enclosure which is connected to my USB port. How do I get F13 to recognize the disk? It does not show up in the Disk Utility (Applications > System Tools > Disk Utility).
F13 does recognize flash drives that I put into a USB port.
My Motherboard has 4 SATA ports on it, Is there a way short of buying an expensive RAID card to add more SATA drives and do a software raid still? What about getting an external 8-bay eSATA enclosure and putting drives in it? Will the OS see this and software raid? (linux)
I put together a NAS-like device using a 2-slot USB JBOD enclosure and an eBox-3300. I'm using Ubuntu Server 8.04 Hardy as an OS for the eBox. I have two WD EARS drives hat I intend to use in the USB enclosure, one 1TB large, the other 2TB. I managed to install Hardy on the 1TB drive and boot from it. The 2TB drive is preformatted XFS. If I add the 2TB drive in the enclosure, it does not show up in /dev in ubuntu. In the device's BIOS, both drives appear just fine with correct IDs, so I'm guessing the problem is with ubuntu.
P.S. dmesg report regarding usb:
Code:
[ 6.436689] usbcore: registered new interface driver usbfs [ 6.436872] usbcore: registered new interface driver hub [ 6.437094] usbcore: registered new device driver usb
I have 3X 5.25 SATA removable bays with hard drives in it. I am working on a new script to manually backup some very important data to those drives. Basically, to eliminate risks of burning the HDD's, or accidentally (either by me or my scripts) destroy data, I normally keep those drives offline, i.e. unpowered. The enclosures are Vantec EZ swap and require a key to turn them on/off. Once it is turned on, Slackware see them without a glitch. My script will basically display a message to warn that the backup is about to happen, then once the user click the OK button, mount the partition to a local folder and then backup the data. The partition will then be unmounted and a new message will be displayed to ask the user to "unplug" the HDD. Cron will take care of the schedule.
Basically, in pseudo code:
Code: 1-Verify if sdd is connected (powered)... If so, procee to #2, else display message box "The HDD is not connected" 2-Mount the partition sdd5 to the local folder 3-Backup 4-Unmount the partition from the local folder 5-Display a message box "The backup was completed with success. You can now disconnect the HDD"
how can I automate the detection of the hdd? I would like the script to poll or probe the HDD to see if it was properly turned on, and if so, proceed with the rest... I tried all kind of stuff but no luck... For example, fdisk -l will list the drive & its partitions if it is connected (powered) and wont if the drive is not connected. I cant use the output of fdisk to efficiently accomplish what I am trying to do...
I want the script to display the messages boxes (Please plug the HDD & You can now unplug the HDD) to a different display (i.e. my laptop). The reason is because the script will run on my server that has no monitor...
Why is it that FC6 installs just fine from a USB CDROM in an external enclosure but FC12 boots from the CD asks to install or upgrade an existing system but then stops at no devices found and wants the install path for the install image? It appears to see the CDROM, boots then looses its mind and forgets a CDROM was attached.
My Western Digital My Book World Edition II enclosure failed recently and as normal, WD support sucks. A friend told me he salvaged his by looking at the individual disks with Linux. How can I recover the disks, which seem to be fine.I can put them into an enclosure that supports JBOD and Raid 1 and it will see the drives when hooked up to a Windows XP system. It does not see anything on the drives but it knows they are there. I have a copy of some data recovery software Easus Data Recovery Wizard and it finds loads of data on the drives but recovery, according to the timer, will take weeks.How can I make Ubuntu see each drive and mount it?
I'd like to know if it's possible to automatically mount, and fire up rsync to sync a USB drive with a directory? Specifically, I'd like to copy as much data as the drive can hold and only delete the oldest files if space is needed. I would assume I'd do something like this with a script, but my problem, is where to start.
I once plugged in my mini video camera (6, good buy), and I accidentally clicked on 'Always use F-spot to open this kind of device'. The problem is, I can't set it back to nautilus. I've looked everywhere, including right clicking on the drive in 'Computer', but the default application in the 'properties' window is set to 'open folder'. When I right-click on the drive, I still see F-spot on the list. If I select 'Open with other application', I can't change it from F-spot.
I just installed Ubuntu 10.10 32 bit on my desktop and I've encountered a curious and somewhat frustrating issue. It appears that when I plug a flash drive, external hard drive or MP3 player into a USB port my computer turns off. Sometimes it happens instantly, other times it occurs a minute or two later when I'm transferring files. I'm not sure how to approach this issue. I've searched the forum and haven't found any mention of this. I am working on said desktop and all other hardware seems in good working order. If it helps, This is a 3 year old desktop with an AMD Athlon 64 X2 4600 cpu, a ABIT NF-M2S AM2 NVIDIA GeForce 6100 motherboard, an EVGA GeForce 7600GT video card and a SATA harddrive. I can post a log if someone wants, not sure which one to post though.
I am setting up another computer with Debian 6 stable and I have only 2 normal sata slot on the motherboard, the board has also 2 other Raid sata slot, I don't want to use Raid, can I just plug my 3rd drive into one of those. I read that I can use those slot as JBOD (just another bunch of drive). By running a Mandriva live cd before I install any OS, I don't see that 3rd drive. I don't see anything about JBOD in the bios.
If I plugin a USB drive (external hard drivee) into my running Fedora 13 64-bit system - it occassionally freezes up. This behavior is intermittentI could not trace it to any /var/log/messages yet.
My display on fedora 13 freezes, key board stops working, when I connect projector to my laptop. I see the display settings mentions "DVI monitor, resolution 1280X800 refresh rate 60.0". Do I need to set the resolution to some other number before plugging the projector on and do I need to change it back to the default resolution after unplugging projector
I had an old Windows disk I wanted to see if I could get some files off of. I was a Windows XP installation, but it got a virus of some sort and eventually died completely. I had always wanted to try to get my files off of it so I could wipe it and use it as another drive. Well, I plugged it up in my computer and thought that it would just recognize it as a regular data disk, but instead somehow it got automatically set as the boot drive. The computer went from the BIOS splash screen to blank and back a couple times before booting Windows. I then tried resetting the other drive as the boot drive and also unplugging the Windows disk with the same result: an MBR error screen.
I fixed the issue by reinstalling the MBR with the repair tools in the openSUSE disk but I am really curious if anyone knows why this happened. Is it a Windows issue or a motherboard issue or perhaps something else?. My old computer was about 7 years old but this new one is well, brand new. So I haven't had much experience with newer motherboards but I know they have come out with a lot of new features so for all I know they may have something that can detect a Windows install and rewrite the MBR or something. I also wouldn't put it past MS to influence($) MB makers to include such a feature.
The one problem I have now is that the boot options no longer display the kernel version, and the splash screen with the progress bar no longer shows, just the standard text.
