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.
View 3 RepliesIn 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?
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.
View 7 Replies View RelatedI installed from a live disc months ago. It worked fine for a while, don't remember what caused the change.
Now when I boot, I get this message:
Quote:
I have several hdds in this desktop box, one other has a OS on it, has the Hardy version. But i disconnected that (it all used to work with both drives connected and I was able to use that boot menu to change from one OS to the other). I can boot by getting to "boot menu" by pushing the "esc" key when the bios starts (just after the beep). It gives the option to start from, with a list of possible devices to choose from. I don't know where this menu is from, bios or other. I select hard drive, then select the correct hard drive and it starts right up. That is nonsense though. I really no longer need version 8.04 but keep it as a backup in case my preferred OS/hdd fails.
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
Doesn't change anything.
How can I force the link to be updated towards.
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.
View 2 Replies View RelatedHow can i do to mount a scsi device ? it is a lg android phone ...
My dmesg shows :
I have a HP Proliant DL380 G3 server with Ubuntu Server 9.10
I have a HP Storageworks Ultrium 215 tape device
For some reason the Ubuntu server does not find the tape device
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 RelatedI 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....
After connecting, dmesg shows:
Code:
After that, there are no /dev/sd* entries. the hard drive works as expected on my windows box. how can i mount this drive?
I just compiled my first own kernel (I'm using Arch Linux), following the tutorial on the german site. Now I tried to boot it, I ended up failing with this message: Code: Waiting 10 seconds for device /dev/sda1 ... Root device '/dev/sda1' doesn't exist, Attempting to create it. ERROR: Unable to determine major/minor number of root device '/dev/sda1' Here is the important part of my menu.lst:
[Code]....
I simply copy&pasted the Arch-entry, i.e. I also had the disk by uuid there. The failure message was the same, just the root device name was the different name Also, at first I did not have the initrd line in my menu.lst (as written in my tutorial that I may not need it). In this case I had this error message:
[Code]....
cciss :cmd ffff880074984e00 has check condition byte 2 = 0x3
Printk : 30 messages suppressed
Buffer I/O error on device cciss/c0d0p2 logical Block 2211585 to 2211594
2 weeks ago, my power supply blew, during close-down. My system is a SUSE Linux 10.1 and openSUSE 11.1 dual boot with WInXP (for those family things). After replacing the power supply my system had no root partition, or loader. It said something like "Invalid Partition table". Grub had gone! So following swerdna's "How to Boot into openSUSE" tutorial I used the openSuse 11.1 install CD rescue option to get to the command prompt, su'd, went to grub and followed the stated commands. So far so good.
However the new grub entry openSUSE (Failsafe) has a problem. It starts to boot in the usual way, but I note fatal Module errors in the boot log relating to sata_nv not found, ide_pci_generic not found etc, and Fatal error inserting edd (/lib/modules/2.6.27.39-0.2-default/kernel/driver/firmware/edd.ko): no such device but uses udev as boot source until Waiting for device /dev/disk/by-id/ataST3120827AS-4M60PX7V-part6...... and then it exits to /bin/sh.
My fdisk looks
Dev Boot Start End Blocks Id Syst
/dev/sda1 1 1306 10490413 c w95 fat32
/dev/sda2 1307 2612 10690445 c w95 fat32
/dev/sda3 * 2613 14593 96237382 f w95 ext'd
/dev/sda5 5486 8096 20972862 83 linux
/dev/sda6 8097 10695 20987643 83 linux
/dev/sda7 10699 14593 31310653+ 83 linux
Recently installed some minor software, some games and Ubuntu Tweak, I am not sure if that's what caused this issue or not. I shutdown after the installations, then when I tried to start back up the small, white ubuntu logo appears just like it normally does, then it just goes to a black screen. I turned off the computer and restarted in (Recovery Mode). It goes about its thing then it says it is waiting for root file system, then after about 30 seconds it says "Gave up waiting for Root File System" how to fix this without reinstalling?
View 2 Replies View RelatedI have been trying to update my server from 6.06 server to 10.04 server. My attempts have been complicated by versions later than 6.06 not being able to properly read my CD-ROM. I used the 'do-release-upgrade' mechanism to upgrade to from 6.06 to 8.04 and then to 10.04. 8.04 loaded OK, but 10.04 fails to boot with the surprisingly common "Gave up waiting for root device" error. It stops at the built-in shell prompt. If I exit from the shell, it seems to boot up normally.
I have verified that the boot partition is /dev/sda1 and the UUID for the partition is correct. My system is an older IBM eServer xSeries 350 with quad 700MHz XEON processors and a 36GB SCSI drive. This system properly installed from the 6.06 CD and boots under this version without problems. So I have some questions. Only the first one needs an answer.
1. What do I need to do to get my system to boot properly?
2. Why was this software released with this error?
3. Why wasn't the faulty loader pulled from the release until it was fixed?
4. Is it possible to revert to the 6.06 loader, which works fine?
5. Why doesn't the loader attempt to try something else that should work instead of just giving up?
i have this problem i install android sdk, and i install libreries: libstdc++5, lib32stdc++6, lib32ncurses5 and libstdl1.2-dev,
now if i use ldd comand don't have problem, but when i use eclipse and i compile a simple example (hello word example), i have this
error: [Emulator] SDL init failure, reason is: No available video device i have a notebook toshiba satellite A300-1RI whit ATI Radeon 3650, i install the amd driver and all work well.
openSUSE Install/Boot/Login: I am looking for a Linux distribution with a working LTSP OOTB. LTSP-openSUSE / KIWI-LTSP looks interesting (http://en.opensuse.org/LTSP).
When I boot openSUSE-11.1-DVD-i586.iso, go through the installer, and attempt to use encrypted LVM, I get the following error dialog:
Code:
YaST2
Error Failure occurred during following action: Setting up encrypted dm device on /dev/sda2 System error code was: -3034
For backup purposes, I built a RAID6 array on USB. When during the night the backup filesystem is being mounted, every so many days, a random disk fails:
Code: sd 9:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 9:0:0:0: [sdb] Sense Key : Illegal Request [current]
sd 9:0:0:0: [sdb] Add. Sense: Invalid field in cdb[code].....
In other words, my RAID set fails every so many mounts, but I know how to fix it.What I want to find out is:
- Why is a random drive failed every now and then?
- How can I prevent that drive from being failed?
BTW: I have a second RAID set that has been functioning for years without error, so the setup I use must be correct. The only difference between both RAID arrays is the different vendor of the disks.
why I'd be receiving this error. I have created a partition and filesystem and put the label in fstab. Everytime I reboot the server it is unable to mount the filesystem. However I am able to mount it manually.
View 5 Replies View RelatedWhat can be the cause of this error.
dmesg | grep -i time
ACPI: PM-Timer IO Port: 0x408
Calibrating delay using timer specific routine.. 4658.19 BogoMIPS (lpj=2329098)
Using local APIC timer interrupts.
[code]....
I'm a long time Linux user. Finally got around to upgrading my Fedora 11 system to Fedora 12 by using the 'preupgrade' tool. The upgrade appeared to go well (downloaded packages, rebooted into installer, etc). However, now that the upgrade is complete, I'm unable to boot my system.
Here's my configuration:
/dev/sda (80Gb)
200Mb /boot partition (ext3)
52Gb / partition (ext4 - managed as logical volume)
2Gb swap partition (managed as logical volume)
20Gb /spare partition (ext3 - managed as logical volume) .....
All worked fine under Fedora 11 for the last few months. Grub now presents me with 'Fedora' and 'Windows XP' boot options. The /boot/grub/menu.lst file is essentially the same as it was for Fedora 11, except for the different kernel versions, etc. The boot sequence shows the Fedora bubble (??) and gets about 80% full when the screen goes black and the message displayed is:
No root device found
Boot has failed, sleeping forever
If I boot Windows, all works fine.
Am able to boot using a SystemRescueCD disk. The disks all look okay and I can mount/modify all partitions, etc. The grub menu.lst file read as follows (sorry, typed in, not copied):
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.32.11-99.fc12.i686.PAE)
root (hd0,0) .....
I insert my F14 CD and booted the computer; I see the beginning of the installation and the the screen goes black and says:
No root device found.Sleeping forever. Boot failure.
I initially thought the problem had to do with the Lucid Lynx upgrade, a lot of people have been reporting similar issues with drive mapping and things along those line. My issue is that an external drive, formatted in FAT32 appears to be corrupted, and overtime begins to read or mounts as 'read-only.'
What I've read, and deduced, is that this is ultimately and issue with the drive. I've backed it up, reformatted, and been able to write to the drive successfully, but I've been moving a lot of files (backing up) and the system has been reporting input/output errors in transferring some files (through the GUI).
The only thing I can think of, is that the device itself is corrupted or damaged, and that I need to be thinking of other back-up options for the future. Any suggestions on disk-doctoring? I'm hoping to do a clean-install of the OS once I back up my files manually.
I got opensuse 11 running on a dedicated HDD and got another 4 HDDs created as RAID 10 via the Intel Matrix RAID Controller of the ICH10 southbridge. I simulated a device failure and disconnected one of the drives and during POST the controller simply says that I need to rebuilt the array from the OS. So how am I supposed to do that since there were no usable raid utitlities for openSuSe delivered out of the box.
View 8 Replies View RelatedRecently, I created a device sc0 through device mapper. The divice could be found in /dev/mapper/sc0. My problem is that the device doesn't exist in /dev/partitions which will block my following test.BTW, I found dm-0 in /dev/partitions. Is it the same as /dev/mapper/sc0? But the device /dev/dm-0 doesn't exist!
View 2 Replies View RelatedI am working on an embedded system, which is an USB MSC device that supports some vendor specific scsi commands. I am using FC10 laptop as USB host for testing, and it runs some small apps based on sg3. All has been well for ~ a week. The FC10 laptop is able to communicate with the device and retrieve data. Suddenly, starting from today, the laptop is not able to properly detect the device. When plugged-in, the MSC device is detected as input device (I thought). This is observed from "dmesg" output and changes in "/dev/input/".The device under development is running at full speed. When I connect to winXP, no problem. A windows file explorer pops up, showing the content of the drive.Also, the FC10 has no problem with other USB flash drive (high speed).
View 1 Replies View RelatedAll my music editing software programs say, "unable to open device /dev/dsp.Device or resource busy." How can I fix this?
View 3 Replies View RelatedI rebooted my server and out of nowhere the RAID5 array won't assemble. I've tried everything I could think of to reassemble the thing. I fear that the array is ruined, but I can't imagine how. Here are various bits of information: The simplest failure (with and without partition numbers, which have not been needed in the past):
Code:
richard@nas:~$ sudo mdadm --assemble --verbose /dev/md0 /dev/sd[bcd]
mdadm: looking for devices for /dev/md0
mdadm: cannot open device /dev/sdb: Device or resource busy
[code]...