similar to: USB device not connected (CentOS 5.3)

I have just bought a 120GB external usb drive but after plugging it in it is not getting mounted. lines from /var/log/messages: > Oct 22 18:54:49 station2 kernel: usb 1-2: new high speed USB device using ehci_hcd and address 2 > Oct 22 18:54:49 station2 kernel: usb 1-2: configuration #1 chosen from 1 choice > Oct 22 18:54:49 station2 kernel: scsi4 : SCSI emulation for USB Mass Storage

Fresh install of CentOS 4.4. uname -a, lspci, & lsusb output at bottom. I insert my 256MB USB key, light goes on, then off. Never mounts. Here's the end of dmesg: usb 1-1: new full speed USB device using address 11 scsi7 : SCSI emulation for USB Mass Storage devices Vendor: Generic Model: STORAGE DEVICE Rev: 1.02 Type: Direct-Access ANSI SCSI revision:

[previously sent to rhelv5 list, apologies to those on both] I've got a problem I can reproduce easily enough, but really I fail to understand what's going wrong. I've got a 5.3 Dom0, which is running three guests. One is Fedora 10, that runs with local flat files, and works fine. One is Nexenta 2 (opensolaris-based), and that runs off of physical partitions, and seems to work

Hello! I''ve a ubuntu server running over a HVM DomU. After a hang, the domU doesn''t start again. The domU was not able to mount the virtual machine disk so I started with a live cd and I tried to mount the disk root part / with no success so I ran fsck.ext3 and it gave me input/output error in the domU and in dom0 the kernel says: Feb 14 18:22:28 scofield last message

I may have asked about this before, but I can't find any records of so doing in my saved mail (which includes almost everything I ever read or write): All of a sudden, I am not getting flash drives automatically mounted in CentOS 5.3 with GNOME - they are recognized by the hardware, but there seems to be a (new?) problem with the maps. Here's the tail end of dmesg: usb 1-10: new high

Hi, I''ve got similar problem - after HW failure - two of three disks became unavailable and now I''m unable to btrfsck. Btrfs lays on /dev/sdb1,/dev/sdc1,/dev/sdd1 - sdc+sdd became unavailable Here is kernel log: ============================================ Mar  9 23:56:28 ftp2 kernel: [121492.593338] ata7.00: exception Emask 0x60 SAct 0x1 SErr 0x800 action 0x6 frozen Mar  9

Hi there... I have kernel version 2.6.36.3, compiled with gcc 4.4.5, btrfstools version 0.19+20101101 I have a btrfs filesystem (/data) consisting of two 1TB hard disks, raid0. I added in another 1TB hard drive. root@X86-64:~# btrfs filesystem show failed to read /dev/sdh failed to read /dev/sdg failed to read /dev/sdf failed to read /dev/sde failed to read /dev/sr0 failed to read /dev/fd0u800

I've been having an extremely hard time using the on board SATA controller on my nvidia based board. I have two 160gig Maxtor SATA drives attached to the on board controller, setup as software raid0. The problem is the array is extremely unreliable, where I'm getting constant I/O errors like: sd 0:0:0:0: SCSI error: return code = 0x00040000 end_request: I/O error, dev sda, sector

We have a 3TB external USB drive that I am trying to attach to some CentOS5 servers. I have tried an older Dell PE1950 and a newer R310 but neither one seems to be able to read the drive. It works no problem on windows servers/workstations and I was able to format with NTFS. I know there are different methods for formatting large disks but this one doesn't even seem to show up as a /dev/

Hi, Sorry for the need of the long winded email. Looking for some answers to the following. I am setting up a xen PV domU on top of a LVM partitioned DRBD device. Everything was going just fine until I tried to test the filesystems in the domU. Here is my setup; Dom0 OS: CentOS release 5 (Final) Kernel: 2.6.18-8.1.4.el5.centos.plusxen Xen: xen-3.0.3-25.0.3.el5 DRBD:

There are a number of flaws in the blktap userspace daemon when dealing with I/O errors. - The backends which use AIO check the io_events.res member to determine if an I/O error occurred. Which is good. But when calling the callback to signal completion of the I/O, they pass the io_events.res2 member Now this seems fine at first glance[1] "res is the usual result of an I/O

Hi All, I had to reboot a machine as I lost the ssh connectivity to it. I could ping to it though. On rebooting, the dmesg buffer showed the following messsage hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440 end_request: I/O error, dev 16:02 (hdc), sector 1820440 hdc: dma_intr: status=0x51 { DriveReady

Hi List, What this means? md: syncing RAID array md0 md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc. md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction. md: using 128k window, over a total of 2096384 blocks. md: md0: sync done. RAID1 conf printout: --- wd:2 rd:2 disk 0, wo:0, o:1, dev:sda2 disk 1, wo:0, o:1, dev:sdb2 sd 0:0:0:0:

Sparc Solaris / UFS file system. I have some ACL's set up for a handful of users and its all worked flawlessly with every incarnation of Samba I've used over the past couple years, which would be most. Last Friday evening I upgraded from 3.0.11 to 3.0.13 and some of the users I have some ACL's set up for promptly found Monday that they couldn't save new Excel files, they'd be

Hello This is a bit off-topic, but here goes: Try installing the "device-mapper-multipath" package and follow the documentation below - residing at the powerlink.emc.com site: "Native Multipath Failover Based on DM-MPIO for v2.6.x Linux Kernel and EMC(r) Storage Arrays" When configured this works just as good as PowerPath. This works great on RHEL / CentOS 5 Daniel On

Good day. I''m getting this error: [101017.440858] blkfront: barrier: empty write xvda op failed [101017.440862] blkfront: xvda: barrier or flush: disabled [101017.463438] end_request: I/O error, dev xvda, sector 3676376 [101017.463452] end_request: I/O error, dev xvda, sector 3676376 [101017.463459] Buffer I/O error on device xvda1, logical block 459291 [101017.463464] lost page write

On Thu, March 9, 2017 09:46, John Hodrien wrote: > On Thu, 9 Mar 2017, James B. Byrne wrote: > >> This indicated that a bad sector on the underlying disk system might >> be the source of the problem. The guests were all shutdown, a >> /forcefsck file was created on the host system, and the host system >> remotely restarted. > > fsck's not good at finding

Hi, I know that IBM SDD(Subsystem Device Driver) for linux are all for kernel version 2.6.9 or lower - for RHEL4 or less, SLES9 or less I installed IBMsdd rpm, but failed to command "sdd start". I use XenExpress version (xen-3.0.4 version) with 2.6.16 kernel. My questions are 1. Is there anyone who use IBM SDD module with the dom0''s 2.6.16 kernel on Xen-3.0.4 ???? if then,

Hi - relatively inexperienced user here. I installed CentOS 5.2 yesterday (http install via a mirror, worked brilliantly), as well as a new Seagate 1Tb USB external HDD (from the new Xtreme line), for backup/media storage. Using fdisk I put two primary partitions on the Seagate, /dev/sde1 and /dev/sde2 (roughly half the drive each). Then I used mkfs.ext3 on both to create ext3 filesystems

Hello We were attempting to use scsi-target-utils, hosted on a xen dom0 vm using localhost, and running into some problems. I was not able to reproduce this on a centos 7.2 server using the default kernel. (From dmesg) Apr 4 11:18:42 funk kernel: [ 596.511204] connection2:0: detected conn error (1022) Apr 4 11:18:42 funk kernel: connection2:0: ping timeout of 5 secs expired, recv