similar to: hardware error or fs corruption?

I have a usb hd that I use for backup. Occasionally it dies. scsi 6:0:0:0: rejecting I/O to dead device scsi 6:0:0:0: rejecting I/O to dead device scsi 6:0:0:0: rejecting I/O to dead device scsi 6:0:0:0: rejecting I/O to dead device Buffer I/O error on device sdc1, logical block 0 lost page write due to I/O error on sdc1 EXT2-fs error (device sdc1): read_inode_bitmap: Cannot read inode bitmap -

Hi there Firstly, you may want to check out this thread on Experts Exchange: http://www.experts-exchange.com/Operating_Systems/Linux/Q_20815085.html essentially this is my problem - I can connect to and browse a windows file share with smbclient, but when i try to mount it with mount.cifs I get errors. Note that this only happens when I have to authenticate to a domain controller - I can use

Hi, I get the below from dmesg. The server seems to run fine, but it does worry me. What should I do? Other than take a backup.. :-) hda: dma_timer_expiry: dma status == 0x21 hda: DMA timeout error hda: dma timeout error: status=0xd0 { Busy } ide: failed opcode was: unknown hda: DMA disabled ide0: reset: success hda: dma_timer_expiry: dma status == 0x21 hda: dma_intr: status=0x51 { DriveReady

Hello all. I'm using RedHat 7.2 now and haven't have any problems until today. I can still boot into the system at this time, but cannot load X at all. I'm getting the following error message when I try to run fsck. /contains a file system with errors, check forced. Pass 1: Checking inodes, blocks and sizes Error reading block 1277964 (Attempt to read block from filesystem resulted

Hi, I run hundreds of Redhat 8.0 boxes and Fedora Core 1 boxes, both Operation systems boxes give me some trouble reporting disk errors like the following (collected from /var/log/messages of each linux boxes by my own script). And a "badblocks" command on some of the related hard drive reports that failed sectors found, while others reports no, false-positive. Any one can give me

Hi, Sorry if this is an old and fixed issue but I can't really seem to find a definitive explanation/fix to this in the mail lists. Ever since I upgraded to FC2 my server randomly decides that it can no longer access the disk and "aborts" the ext3 journal leaving it read-only as expected. I've seen the same errors on other mail list, explained away as disk or disk cable

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

On Thu, 7 Feb 2002 ext3-users-request@redhat.com wrote: > Ext3-users -- confirmation of subscription -- request 905448 > > We have received a request from 66.88.179.82 for subscription of your > email address, <mhaque@haque.net>, to the ext3-users@redhat.com > mailing list. To confirm the request, please send a message to > ext3-users-request@redhat.com, and either: >

Hello I just brought my machine back up from a very nasty crash. Not sure what caused it yet but whatever happeed cause the journal to be foobared. fsck dropped the journal and then proceeded to check the fs. I have a directory called websites which fsck unlinked. however when i look in debugfs i see this.. 622669 40755 0 0 4096 13-Jan-2002 22:39 home3 2133571369 --- error ---

Hello I seem to be getting some messages via email and in var/log/messages as well, i think its a hard drive gone bad but was wondering if anyone has seen something similar to this or would have some ideas if its fixable or not, here are the messages This email was generated by the smartd daemon running on: host name: localhost.localdomain DNS domain: localdomain NIS domain: (none)

Device manufacturer: Fideltronik INIGO Device name: Viper 1200 Device type: UPS Bus type: USB WWW: http://fideltronikinigo.com/viper/viper-1200/ " nut-scanner -U" output: [nutdev1] driver = "blazer_usb" port = "auto" vendorid = "0001" productid = "0000" product = "MEC0003" vendor =

Can someone tell me what has to happen to get the aliases working in samba? Below is an earlier posting. Thanks!! Does anyone have aliases working correctly? Suppose I am moving the samba to one server to another, say VIPER > to JOKER. > > In smb.conf I change the 'netbios name = VIPER' to JOKER > and I also want the old name to be seen as well. To do this > I create

On Jul 10, 2015, at 7:42 AM, AWa. <awa_wp at wp.pl> wrote: > Device manufacturer: Fideltronik INIGO > Device name: Viper 1200 > Device type: UPS > Bus type: USB > WWW: http://fideltronikinigo.com/viper/viper-1200/ > Thank you! One question: is ups.load always 0? Some of the NUT command comments didn't make it in, but if you have any other suggestions, this is the

Hi, I'm having some serious problems diagnosing a hardware issue in my linux system. The following error occurs intermittently. I have replaced hard drives and it is still occurring. I'm trying to determine if it's a device conflict, a problem with the motherboard or something else. Can anyone help? hda: dma_intr: status=0x51 {DriveReady SeekComplete Error} hda: dma_intr: 0x40

I am getting occasional seek error on my boot drive. The messages are as follows: pshda: dma_intr: status = 0x51 { Drive ReadySeekComplete Error } hda: dma_intr: error= 0x84 { DriveStatusError BadCRC } ide: failed opcode was: unknown Everything seems to be working fine but these errors do have me concerned. The last time they occurred I was created a fairly large cpio backup file in the

Hi, I have an ext3 file system question for a while: How to obtain failed file (inode) from LBA section reported by Linux kernel? The following lines are a simple example: ... FCbox1: Nov 1 04:08:59 FCbox1 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } FCbox1: Nov 1 04:08:59 FCbox1 kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=165843413, high=9,

Okay, I've narrowed the problem down quite a bit. As previously reported, in CentOS 5.2 I get this: $ cvs log Makefile poll: protocol failure in circuit setup cvs [log aborted]: end of file from server (consult above messages if any) Turns out this is a problem with rsh: $ rsh khan ls connect to address 10.24.15.48 port 544: Connection refused Trying krb4 rsh... connect to address

Another little problem I am now having on CentOS 5.2 that I was not seeing on FC8: [mrichter at sushi lane]$ cvs update poll: protocol failure in circuit setup cvs [update aborted]: end of file from server (consult above messages if any) I could understand if there was something that had changed from FC1 to CentOS 5.2, but if it works in FC8, why not here? Here's what's in the CVS

Hi, yesterday my linux machine gave me some smartd errors so i checked the disk in another machine and it had defective sectors, I installed a new hard disk on the original machine. Today this is being reported in logwatch. I have a Maxtor (200gig) as hda, a cdrom as hdc and another hard disk that is used for storage as hdd. All plain IDE (not sata) --------------------- Kernel Begin

Hi upon booting this morning (Redhat 8.0), i received this error message Nov 17 02:55:07 jaguar kernel: EXT3-fs error (device ide0(3,3)): ext3_find_entry: bad entry in directory #1111941: inode out of bounds - offset=36, inode=537868397, rec_len=12, name_len=4 I've also had these messages too Nov 3 20:25:42 jaguar kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } Nov 3