Server :: Removed Fibre Scsi Drive Shows Even After Reboot?
Apr 30, 2010
I am running fedora 8 on a Dell 2950 with a qlogic fibre channel card.is attached to a Dell/clarion AX100.I had a drive assigned to this server which had been working for approximately a year now.Recently during a power failure things turned ugly. Rebooting didn't fix things.I unassigned/reassigned the drive, rebooted, still no good.Funny thing when I unassigned the drive and reboot the system.still see /dev/sdb but no partitions and fdisk -l does not display /dev/sdb.I even did "echo 1 > /sys/block/sdb/device/delete"
and the device no longer showed in /dev, but after a reboot it is back.I pulled and reseated the fibre card, same
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....
I am setting up a new server and am in the midst of testing RAID. This is an Ubuntu 9.10 server. RAID1 (/dev/md1) is spread across 12 one-terabyte SCSI disks (/dev/sdi through /dev/sdt). It has four spares configured, each of which are also one-terabyte SCSI drives (/dev/sdu through /dev/sdx). I have been following the instructions on the Linux RAID Wiki ([URL]....
I have already tested the RAID successfully by using mdadm to set a drive faulty. Automatic failover to spare and reconstruction worked like a champ. I am now testing "Force fail by hardware". Specifically, I am following the advice, "Take the system down, unplug the disk, and boot it up again." Well, I did that, and the RAID fails to start. It outright refuses to start. It doesn't seem to notice that a drive is missing. Notably, all the drive letters shift up to fill in the space left by removing a drive. The test I did was to:
[code]....
Is removing a disk from the bus a reasonable test in the first place? Meaning, is this likely to happen in a production environment by other means than a human coming by and yanking out the drive? Meaning, is there a hardware failure that would replicate this event? Because, if so, then I don't know how to recover from it.
A single LUN is attached to my server with rhel5.3. The server has two Fibre channel adapters. I need to turn off one of the FC interface manuly. Which command should i use to turnoff(disable) the adapter. The settinga are the following:
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.
I try to use a usb pen drive. The usb pen drive show up under computer but not like a drive in geparted. When I look in the log file I find the drive Code: May 29 10:11:46 CQ60 kernel: [ 112.942602] scsi 6:0:0:0: Direct-Access USBest USB2FlashStorage 0.00 PQ: 0 ANSI: 2 I do not know what this mean but it looks like the drive show up like a scsi and not usb or? I need a clue to get it work like a normal usb device.
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?
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 need to read some data from a hdd that belongs to an old SCO Unix system. The SCSI card is PCI so I unplugged it from the old SCO unix box and stuck it in a new computer and booted using a Fedora 14 USB pen drive. The SCSI card was recognized and so was the hdd but it was not mounted. I then went into Applications, Disk Utility, and found the hdd. Under 'Edit Partition' the type was blank. I was tempted to set it to 'Extended' but was not sure whether that could damage the data on the disk. Does anyone know whether I would be able to read this Hdd by setting the type to 'Extended'?
I have just purchased (AT ENORMOUS EXPENSE) a used 306637-004 36 GB hard drive. It has come, by default, with no jumpers and my scsi controller recognizes it as SCSI device 0.Very inconvenient as it clashes with my existing IBM 9GB drive I am loth to play about with.Does any kind person out there know how to jumper this drive to be SCSI ID 1 or 2 (say).
I did an installation of SUSE 11.2 on a new SCSI hard drive. Keeping the old hard drive separate. I remembered there was some info on the old hard drive I wanted.
I added this to the system and mounted a partition. I then copied the data over. Then I umounted the partition rebooted the machine and removed the hard drive. However the machine will now not boot without this hard drive even though its not mounted. Not sure what the error message im given means I think it could be trying to fchk it.Do I need to do something more like remove /dev/sdd ?
just bought an adaptec 39160 PCI scsi controller and 34Gb drive and installed it on my computer.When i Booted it up a utility thing ran which said 'detecting array' and it found the drive and its size etc. it didn't go any further to allow my system to boot, so I rebooted and pressed CTRL + A to enter the adaptec scsi config. I changed something in there to make the disk non bootable (i Think) and rebooted the system.
It now hangs at :
'Detecting Array .....'
and does not show the drive details or the CTRL + A option to enter the utilities. So the only option I have had is to remove the adaptec controller ( and the system boots fine) the mother board is an Abit an8 ultra - probably about 4 years old and cpu is amd 64 I guess i have broken it and my remedy would be to reset the default options on the adaptec controller, but you can probably guess I have v. limited knowledge and have not used scsi before.
I have successfully setup a FOG server to image my Windows clients, so I have tftp, pxe and anything else related to booting to a pxe server setup and rocking. What I'm trying to do now, is use the CentOS net install files to setup CentOS on an old server with no USB boot option, and a broken scsi cdrom drive (it's a Dell PowerEdge 2400, with a single PIII 733 and 1.25GB ram).
Using the FOG Projects gparted wiki entry (adding gparted to the pxe boot menu) I was actually successfully able to pull the net install files over to the PE, and install CentOS 5.5 via local ftp server. At first it kept erroring out (I kept picking and choosing individual packages from the package groups), so I thought it may be an issue with the GUI install (the python script kept spitting back errors forcing a reboot). In any case, I finally got through the GUI install, but now I need / want to know how to force a text mode install.
[Code]....
the bolded "append" line is where I thought I could force the text mode install script, but that didn't work. The vmlinuz and initrd.img files were both pulled form the net install iso, NOT the livecd. Would that have made a difference? If not, what / where / how should I force the text mode install script?
Is there anything that could betray the time the USB memory drive was last removed ? I can't find it and the time would help me pinpoint what happened to it.fstab file last access time or something like that ?
I'm looking for a version of, or equialent to, Predator for Ubuntu 10.10. This program sets a USB drive as a key to the computer, locking it when removed. I've had no luck in finding an equivalent for Ubuntu, and the site does not have a version for Linux of any kind.
I have servers installed with RHEL 4 2.6.9-89.0.9 ELsmp. I tried using uuid and label in /etc/fstab to automount usb drives to mountpoints that I specify after reboot. Unfortunately, it just does not work in all my RHEL4 servers. After every reboot, /etc/fstab will be automatically modified and all configurations related to my USB drives will be changed. Irregardless of whether i use UUID or LABEL in my /etc/fstab.However, it works on RHEL5. But, upgrading is not an option in my environment. I have been googling around looking for alternatives but everything seems to point back to using UUID or LABEL in /etc/fstab. Anyone has tried something that works? Please help me, thank you.
I have 6 hard drives that have 9.10 and 10.04 on them. Not as a dual boot, but some hard drives have different versions on them. When I have plugged the drives in a couple of weeks later, the grub is gone and system will not boot. I get like a grub 1.5 error and that is all the options I have. Does anyone one know why this happens? Nothing on the drives but the O/S to get rid of windows. All drives worked perfect until they were removed and installed later.
Need help on how the scsi and multipathing works in Linux. From the docs i have read, i understand that by the use of multipathing we can assign multiple paths to a SAN partition. If there is a problem then one path will failover to other path.However, i am not clear on how linux recognizes the SAN partitions using the multipath drivers. For e.g. I have a HP Proliant server on which we have the following mounts:
Filesystem Size Used Avail Use% Mounted on /dev/cciss/c0d0p3 59G 11G 46G 20% / /dev/cciss/c0d0p1 494M 27M 443M 6% /boot
I have properly ejected a USB memory stick and removed it from the port, but it remains in my 'Places', on the side pane of Nautilus. The /media directory is empty.
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 currently have a massive problem with my main webserver: one of the SCSI drives where I keep my htdocs seems to have failed (sd 0:0:0:0: [sda] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK end_request: I/O error, dev sda, sector 7797601).
Since I have no backup (dumb!dumb!dumb!) of it, I tried to copy what I could on the fly, but that failed miserably. The next idea was to umount the volume and try remounting it R-O, but I have a bunch of apache2 processes that are apparently reading/writing on it and I can't seem to find any way of terminating them. I tried via init script, killall and kill -9 but they just don't respond. Until I can terminate those processes, I won't be able to unmount the drive and try saving what's left of the data.Oh and the cherry on top of the cake: the server is 1100 miles away so I can't even access it physically..Is there any way I didn't think of to get rid of those apache processes?
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 have an old Dell Dimension 4500 that, until recently, had 2 hard drives. One drive is running Xubuntu Koala and the other was running XP. I had set up Xubuntu to run LVM.
After needing XP again for a small project I tried reinstalling XP, got disk errors, took the drive out to just have Xubuntu, and now when I boot I get "Error loading operating system".
I have tried restoring GRUB from a Live CD with no help. Everyplace I look on the net talks about restoring GRUB after installing Windows on another drive. I'm trying to get GRUB working again after removing the XP drive.
I've been having trouble with CUPS.I uninstalled it and I wanted to re-install it. When I removed CUPS some other files were removed too. I don't have an option of installing the software or updating a system, in the Control Center.
