LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices


Reply
  Search this Thread
Old 10-29-2005, 02:24 AM   #1
duffmckagan
Senior Member
 
Registered: Feb 2005
Distribution: Cent OS 6.4
Posts: 1,163

Rep: Reputation: 49
DMA Problem.


I have installed Debian Sarge 3.1 on a computer witht he following Hardware Details.

Details about the computer.


Sometimes, while shutting down the computer, I get errors similar to this.


Code:
umounting file systems
hdb: dma-timer_expiry
dma status ==0x61
hdb: dma timeout 

hda: DMA disabled.
hdb: no DRQ after issuing WRITE
ide0: reset: success
hdb= dma_timer_expiry= 0xd0 (Busy)
Seems like a problem with the DMA.

The hda is a Samsung 40GB HDD with many partitions for as many as 6 Linices...
and the other one hdb is a Seagate 120GB HDD with the 80GB data partition...with fat32 file system.... I fear of critical data loss on the Fat File system.

Please help. Its urgent.
 
Old 10-29-2005, 02:47 AM   #2
samael26
Member
 
Registered: Oct 2004
Location: France, Provence
Distribution: Debian
Posts: 848

Rep: Reputation: 30
Hi,

1) Install hdparm

#apt-get install hdparm

2) Then edit the file hdparm.conf in your favourite editor,
scrolling down to DMA=... then replace the three dots with 'ON'

3) To enable DMA, as root type :
Code:
hdparm -d1 /dev/ hdsomething
Of course, replace something with the device you want to use.

4) To make it permanent, sorry, I've tried but no matter what I tried
I have to do that at each reboot.


Hope it helps
 
Old 10-29-2005, 04:20 AM   #3
duffmckagan
Senior Member
 
Registered: Feb 2005
Distribution: Cent OS 6.4
Posts: 1,163

Original Poster
Rep: Reputation: 49
But i don't understand what could be the cause for this sudden problem.

I booted into Mandriva and it gave me some error regarding faulty Hardware during bootup.

I got the following message (excerpt from /var/log/boot.log)

Code:
fsck: finished 
Oct 29 05:32:56 Copperskull fsck: Reiserfs super block in block 16 on 0x345 of format 3.6 with standard journal 
Oct 29 05:32:56 Copperskull fsck: Blocks (total/free): 5174928/4640595 by 4096 bytes 
Oct 29 05:32:56 Copperskull fsck: Filesystem is clean 
Oct 29 05:32:56 Copperskull fsck: ******************************************************************** 
Oct 29 05:32:56 Copperskull fsck: * Warning: It was just detected that dma mode was turned off while * 
Oct 29 05:32:56 Copperskull fsck: * operating -- probably  due  to some  problem with your hardware. * 
Oct 29 05:32:56 Copperskull fsck: * Please check your hardware and have a look into the syslog file. * 
Oct 29 05:32:56 Copperskull fsck: * Note: running with --rebuild-tree on faulty hardware may destroy * 
Oct 29 05:32:56 Copperskull fsck: * your data.                                                       * 
Oct 29 05:32:56 Copperskull fsck: ********************************************************************


I will post the messages from other distros, when I discover them in the log files.

The message that I posted were handwritten by me.....and may have not provided a complete insight of the problem.

Also, I will link this post to the Hardware Section of this Forum.


Thanks for the reply.
I was also taking a look at this link.

Last edited by duffmckagan; 10-29-2005 at 04:22 AM.
 
Old 10-29-2005, 04:55 AM   #4
duffmckagan
Senior Member
 
Registered: Feb 2005
Distribution: Cent OS 6.4
Posts: 1,163

Original Poster
Rep: Reputation: 49
Finally, I found the required ERROR Messages.

See if these help you guys finding a more appropriate solution.
I really don't understand what caused this all of a sudden.

I really can't backup this huge amount of data in a short period of time.


Code:
Oct 29 03:28:27 copperskull kernel: hdb: dma_timer_expiry: dma status == 0x61
Oct 29 03:28:37 copperskull kernel: hdb: error waiting for DMA
Oct 29 03:28:37 copperskull kernel: hdb: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }
Oct 29 03:28:37 copperskull kernel: 
Oct 29 03:28:37 copperskull kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Oct 29 03:28:37 copperskull kernel: 
Oct 29 03:28:37 copperskull kernel: hda: drive not ready for command
Oct 29 03:28:37 copperskull kernel: is_tree_node: node level 11051 does not match to the expected one 1
Oct 29 03:28:37 copperskull kernel: ide0(3,9):vs-5150: search_by_key: invalid format found in block 589420. Fsck?
Oct 29 03:28:37 copperskull kernel: ide0(3,9):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [164357 175283 0x0 SD]
Oct 29 03:28:37 copperskull kernel: is_tree_node: node level 11051 does not match to the expected one 1
Oct 29 03:28:37 copperskull kernel: ide0(3,9):vs-5150: search_by_key: invalid format found in block 589420. Fsck?
Oct 29 03:28:37 copperskull kernel: ide0(3,9):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [164357 175283 0x0 SD]
Oct 29 03:28:37 copperskull kernel: hdb: read_intr: status=0x51 { DriveReady SeekComplete Error }
Oct 29 03:28:37 copperskull kernel: hdb: read_intr: error=0x04 { DriveStatusError }
Oct 29 03:28:37 copperskull kernel: hdb: read_intr: status=0x51 { DriveReady SeekComplete Error }
Oct 29 03:28:37 copperskull kernel: hdb: read_intr: error=0x04 { DriveStatusError }
Oct 29 03:28:38 copperskull kernel: hdb: read_intr: status=0x51 { DriveReady SeekComplete Error }
Oct 29 03:28:38 copperskull kernel: hdb: read_intr: error=0x04 { DriveStatusError }
Oct 29 03:28:38 copperskull kernel: hdb: read_intr: status=0x51 { DriveReady SeekComplete Error }
Oct 29 03:28:38 copperskull kernel: hdb: read_intr: error=0x04 { DriveStatusError }
Oct 29 03:28:38 copperskull kernel: ide0: reset: success
Oct 29 03:28:58 copperskull kernel: hdb: dma_timer_expiry: dma status == 0x41
Oct 29 03:29:08 copperskull kernel: hdb: error waiting for DMA
Oct 29 03:29:09 copperskull kernel: hdb: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }
Oct 29 03:29:09 copperskull kernel: 
Oct 29 03:29:09 copperskull kernel: hda: status error: status=0x50 { DriveReady SeekComplete }
Oct 29 03:29:09 copperskull kernel: 
Oct 29 03:29:09 copperskull kernel: hda: no DRQ after issuing MULTWRITE
Oct 29 03:29:09 copperskull kernel: hda: status error: status=0x50 { DriveReady SeekComplete }
Oct 29 03:29:09 copperskull kernel: 
Oct 29 03:29:09 copperskull kernel: hda: no DRQ after issuing MULTWRITE
Oct 29 03:29:29 copperskull kernel: hdb: dma_timer_expiry: dma status == 0x41
Oct 29 03:29:39 copperskull kernel: hdb: error waiting for DMA
Oct 29 03:29:39 copperskull kernel: hdb: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }
Oct 29 03:30:09 copperskull kernel: 
Oct 29 03:30:09 copperskull kernel: hda: status error: status=0x50 { DriveReady SeekComplete }
Oct 29 03:30:09 copperskull kernel: 
Oct 29 03:30:09 copperskull kernel: hda: no DRQ after issuing MULTWRITE
Oct 29 03:30:09 copperskull kernel: hda: status error: status=0x50 { DriveReady SeekComplete }
Oct 29 03:30:09 copperskull kernel: 
Oct 29 03:30:09 copperskull kernel: hda: no DRQ after issuing MULTWRITE
Oct 29 03:30:09 copperskull kernel: hdb: dma_timer_expiry: dma status == 0x41
Oct 29 03:30:09 copperskull kernel: hdb: error waiting for DMA
Oct 29 03:30:09 copperskull kernel: hdb: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }
Oct 29 03:30:09 copperskull kernel: 
Oct 29 03:30:09 copperskull kernel: hda: status error: status=0x50 { DriveReady SeekComplete }
Oct 29 03:30:09 copperskull kernel: 
Oct 29 03:30:09 copperskull kernel: hda: no DRQ after issuing MULTWRITE
Oct 29 03:30:09 copperskull kernel: hda: status error: status=0x50 { DriveReady SeekComplete }
Oct 29 03:30:09 copperskull kernel: 
Oct 29 03:30:09 copperskull kernel: hda: no DRQ after issuing MULTWRITE
Oct 29 03:30:09 copperskull kdm[2403]: X server for display :0 terminated unexpectedly
Oct 29 03:30:10 copperskull kernel: mtrr: no more MTRRs available
Oct 29 03:30:10 copperskull last message repeated 3 times
Oct 29 03:31:00 copperskull kernel: is_tree_node: node level 11051 does not match to the expected one 1
Oct 29 03:31:00 copperskull kernel: ide0(3,9):vs-5150: search_by_key: invalid format found in block 589420. Fsck?
Oct 29 03:31:00 copperskull kernel: ide0(3,9):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [164357 175283 0x0 SD]
Oct 29 03:31:00 copperskull kernel: is_tree_node: node level 11051 does not match to the expected one 1
Oct 29 03:31:00 copperskull kernel: ide0(3,9):vs-5150: search_by_key: invalid format found in block 589420. Fsck?
Oct 29 03:31:00 copperskull kernel: ide0(3,9):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [164357 175283 0x0 SD]
Oct 29 03:34:52 copperskull kernel: is_tree_node: node level 11051 does not match to the expected one 1
Oct 29 03:34:52 copperskull kernel: ide0(3,9):vs-5150: search_by_key: invalid format found in block 589420. Fsck?
Oct 29 03:34:52 copperskull kernel: ide0(3,9):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [164357 175283 0x0 SD]
Oct 29 03:34:52 copperskull kernel: is_tree_node: node level 11051 does not match to the expected one 1
Oct 29 03:34:52 copperskull kernel: ide0(3,9):vs-5150: search_by_key: invalid format found in block 589420. Fsck?
Oct 29 03:34:52 copperskull kernel: ide0(3,9):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [164357 175283 0x0 SD]
Oct 29 03:36:45 copperskull kernel: is_tree_node: node level 11051 does not match to the expected one 1
Oct 29 03:36:45 copperskull kernel: ide0(3,9):vs-5150: search_by_key: invalid format found in block 589420. Fsck?
Oct 29 03:36:45 copperskull kernel: ide0(3,9):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [164357 175282 0x0 SD]
Oct 29 03:36:45 copperskull kernel: is_tree_node: node level 11051 does not match to the expected one 1
Oct 29 03:36:45 copperskull kernel: ide0(3,9):vs-5150: search_by_key: invalid format found in block 589420. Fsck?
Oct 29 03:36:45 copperskull kernel: ide0(3,9):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [164357 175282 0x0 SD]
Oct 29 03:36:45 copperskull kernel: is_tree_node: node level 11051 does not match to the expected one 1
Oct 29 03:36:45 copperskull kernel: ide0(3,9):vs-5150: search_by_key: invalid format found in block 589420. Fsck?
Oct 29 03:36:45 copperskull kernel: ide0(3,9):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [164357 175283 0x0 SD]
Oct 29 03:36:45 copperskull kernel: is_tree_node: node level 11051 does not match to the expected one 1
Oct 29 03:36:45 copperskull kernel: ide0(3,9):vs-5150: search_by_key: invalid format found in block 589420. Fsck?
Oct 29 03:36:45 copperskull kernel: ide0(3,9):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [164357 175283 0x0 SD]
 
Old 10-29-2005, 02:07 PM   #5
duffmckagan
Senior Member
 
Registered: Feb 2005
Distribution: Cent OS 6.4
Posts: 1,163

Original Poster
Rep: Reputation: 49
I don't know where did the problem lie!

I disabled DMA Mode of both the hard disk using hdparm, and on bootup, it was enabled again.

Don't know how I don't get those errors anymore.

Sorry for double posting.
Sorry for not posting in the proper section.

My sincere apologies.
 
Old 10-29-2005, 03:11 PM   #6
samael26
Member
 
Registered: Oct 2004
Location: France, Provence
Distribution: Debian
Posts: 848

Rep: Reputation: 30
Good it worked !
 
Old 10-29-2005, 03:18 PM   #7
duffmckagan
Senior Member
 
Registered: Feb 2005
Distribution: Cent OS 6.4
Posts: 1,163

Original Poster
Rep: Reputation: 49
Problem not solved. Problem disappeared!

;-)

I will post back in case the problem troubles me again.
 
Old 10-30-2005, 01:24 AM   #8
slithy
Member
 
Registered: Jun 2005
Distribution: Debian "Etch"
Posts: 48

Rep: Reputation: 15
If you don't have support for your mobo's chipset integrated into the kernel, then DMA will be turned off by default and you won't be able to change it with hdparm.
 
Old 10-30-2005, 08:32 AM   #9
duffmckagan
Senior Member
 
Registered: Feb 2005
Distribution: Cent OS 6.4
Posts: 1,163

Original Poster
Rep: Reputation: 49
As already told, the problem cropped up all of a sudden.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
DMA problem lp449 Linux - Hardware 18 10-17-2005 01:16 AM
Suse 8.2 change my DMA setting on my DVD-R drive to off & IDE DMA MODE NOT SHOWING IT maximalred Linux - General 0 08-23-2003 04:58 AM
sound card problem sounded like dma problem whansard Linux - Hardware 0 05-22-2003 07:58 PM
DMA problem salparadise Linux - Newbie 10 12-12-2002 05:49 AM
DMA problem eggman Linux - Software 1 05-17-2001 07:22 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian

All times are GMT -5. The time now is 04:11 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration