[clue-tech] Re: kernel drivers (linux kernel: hde: drive_cmd:

Wed Jan 4 08:39:11 MST 2006

but the weird part is these errors are coming from hdf too, both
connected to the ata controller and I don't beieve that drive is at
all corrupted, so do you think this could be caused by some minor
incompatibilities with suse and the controller card (perhaps
incompatible commands?) and thus it can be ignored?

On 1/4/06, Hex Star <hexstar at gmail.com> wrote:
> mm, well after the installation of linux it turns out that the IDE
> cable connection to the ATA controller was actually half out for some
> reason, it's now completely in...do you think this could be the cause
> of these errors and thus they could be ignored (perhaps some minor
> corruption occured due to that but it can be ignored)? Or do you think
> it'd be worth trying a reinstall since this may mean there's major
> corruption? Thanks for your reply and help! :-)
>
> On 1/4/06, Jim Ockers <ockers at ockers.net> wrote:
> > Hi "Hex Star" (whatever your real name is):
> >
> > I'm top posting intentionally due to the length of your e-mail.
> >
> > Those error messages indicate you should replace the drive.  The
> > block device should never return errors like that if it is
> > functioning properly.  Reliance on fsck to repair the filesystem
> > on a defective block device is not a good long term strategy.
> >
> > You have a misunderstanding of the relationship between the BIOS
> > and the Linux kernel.  The kernel and its IDE device drivers do
> > not use the BIOS, for anything, once booted.  The boot loader does
> > use the BIOS of course, to boot the kernel.
> >
> > The kernel and its IDE device driver interrogate the chipset (IDE
> > controller) about the devices on the bus, and then they interrogate
> > each device to determine its characteristics.  IDE hard drives are
> > treated as block devices, with "n" blocks, starting at block 0,
> > and going to the nth block.  All blocks are assumed to be error
> > free.
> >
> > It really doesn't matter how "big" the BIOS thinks your drive is;
> > it will report its block count to the kernel, and the kernel will
> > use the drive at whatever size the drive says its block count is.
> >
> > You could make a small boot partition at the beginning (first few
> > megabytes) of the drive, and put the kernel on it.  Then the BIOS
> > would be able to boot the kernel from that drive, and you can use
> > the rest of the drive as one big partition if you wanted.  The
> > BIOS is mostly irrelevant except for booting.
> >
> > Hope this helps,
> > Jim
> >
> > --
> > Jim Ockers, P.Eng. (ockers at ockers.net)
> > Contact info: please see http://www.ockers.net/
> >
> > Hex Star wrote:
> > >
> > > Oh right, and the latest BIOS only supports half of my 300GB HD
> > > (150GB) and costs $60 so I figured my money would be better spent on a
> > > $50 ATA card which can see the whole HD without a dynamic drive
> > > overlay (as needed to due my BIOSes shortcomings, it only sees 60GBs
> > > max), hope I was right that this was a better choice to make! :-)
> > >
> > > On 1/3/06, Hex Star <hexstar at gmail.com> wrote:
> > > > Can I ignore this error? What is this error? Should I do anything?
> > > >
> > > > Those questions are for these errors:
> > > >
> > > > Jan 3 15:45:05 linux kernel: hde: drive_cmd: status=0x51 { DriveReady
> > > > SeekComplete Error }
> > > > Jan 3 15:45:05 linux kernel: hde: drive_cmd: error=0x04 { DriveStatusError }
> > > > Jan 3 15:45:05 linux kernel: hdf: drive_cmd: status=0x51 { DriveReady
> > > > SeekComplete Error }
> > > > Jan 3 15:45:05 linux kernel: hdf: drive_cmd: error=0x04 { DriveStatusError }
> > > > Jan 3 15:45:05 linux [powersave_proxy][2336]: WARNING: hdparm returned error 5
> > > > Jan 3 15:45:05 linux kernel: hdf: task_no_data_intr: status=0x51 {
> > > > DriveReady SeekComplete Error }
> > > > Jan 3 15:45:05 linux kernel: hdf: task_no_data_intr: error=0x04 {
> > > > DriveStatusError }
> > > >
> > > > and not for these:
> > > >
> > > > Warning: device does not support Error Logging
> > > > Error SMART Error Log Read failed: Input/output error
> > > > Smartctl: SMART Error Log Read Failed
> > > > Warning: device does not support Self Test Logging
> > > > Error SMART Error Self-Test Log Read failed: Input/output error
> > > > Smartctl: SMART Self Test Log Read Failed
> > > >
> > > > which I believe were caused simply because the HD didn't support those
> > > > methods as the program mentioned...
> > > >
> > > > Also note that Suse 9.1 runs fine, everything loads timely, things
> > > > save fine, etc etc and windows also works fine (mutlibooting via lilo)
> > > > on the HD in question so what's up with these errors? Are they
> > > > ignorable or do they indicate I need to do something and if so what
> > > > and how do I do that something? Note that this is running from a AMD
> > > > motherboard (some unidentifiable Gateway AMD motherboard, no utility
> > > > seems to be able to ID the motherboard, motheboard is used in a custom
> > > > built PC that seems to work fine which I got from eBay), the processor
> > > > is a AMD 600MHz processor, I need the ATA controller to see the whole
> > > > drive, otherwise I have to install a dynamic drive overlay which linux
> > > > doesn't seem to be able to cope with. Please help, I'd like to at
> > > > least be able to rest peacefully by knowing this error is nothing to
> > > > worry about and can be ignored or if a solution is needed I'll do that
> > > > to solve this issue if it is indeed a issue that needs solving. So
> > > > please, any help is greatly appreciated, thanks!
> > > >
> > > > On 1/3/06, Hex Star <hexstar at gmail.com> wrote:
> > > > > Hi, while googling about this error (linux kernel: hde: drive_cmd:
> > > > > status=0x51 { DriveReady SeekComplete Error }) I came upon these
> > > > > postings in your list:
> > > > >
> > > > > http://clue.denver.co.us/pipermail/clue-tech/2004-August/010916.html
> > > > > http://clue.denver.co.us/pipermail/clue-tech/2004-August/010925.html
> > > > > http://clue.denver.co.us/pipermail/clue-tech/2004-August/010927.html
> > > > > http://clue.denver.co.us/pipermail/clue-tech/2004-August/010930.html
> > > > > http://clue.denver.co.us/pipermail/clue-tech/2004-August/010931.html
> > > > > http://clue.denver.co.us/pipermail/clue-tech/2004-August/010937.html
> > > > > http://clue.denver.co.us/pipermail/clue-tech/2004-August/010939.html
> > > > >
> > > > > However I don't have a VIA chipset, I am running my HDs from this ATA
> > > > > controller: http://www.compusa.com/products/product_info.asp?product_code=305320&pfp=BROWSE
> > > > > and am getting the following errors in my system log and am running
> > > > > Suse 9.1 Pro:
> > > > >
> > > > > Jan 3 15:45:05 linux kernel: hde: drive_cmd: status=0x51 { DriveReady
> > > > > SeekComplete Error }
> > > > > Jan 3 15:45:05 linux kernel: hde: drive_cmd: error=0x04 { DriveStatusError }
> > > > > Jan 3 15:45:05 linux kernel: hdf: drive_cmd: status=0x51 { DriveReady
> > > > > SeekComplete Error }
> > > > > Jan 3 15:45:05 linux kernel: hdf: drive_cmd: error=0x04 { DriveStatusError }
> > > > > Jan 3 15:45:05 linux [powersave_proxy][2336]: WARNING: hdparm returned error 5
> > > > > Jan 3 15:45:05 linux kernel: hdf: task_no_data_intr: status=0x51 {
> > > > > DriveReady SeekComplete Error }
> > > > > Jan 3 15:45:05 linux kernel: hdf: task_no_data_intr: error=0x04 {
> > > > > DriveStatusError }
> > > > >
> > > > > Both drives in question have passed fsck without errors and have
> > > > > passed SMART testing (don't have logs for fsck due to it running in
> > > > > recovery mode but I do have SMART logs shown below):
> > > > >
> > > > > linux:/home/hexstar # smartctl -a /dev/hde
> > > > > smartctl version 5.30 Copyright (c) 2002-4 Bruce Allen
> > > > > Home page is http://smartmontools.sourceforge.net/
> > > > >
> > > > > === START OF INFORMATION SECTION ===
> > > > > Device Model: WDC WD3000JB-00KFA0
> > > > > Serial Number: WD-WMAMR1422138
> > > > > Firmware Version: 08.05J08
> > > > > Device is: Not in smartctl database [for details use: -P showall]
> > > > > ATA Version is: 6
> > > > > ATA Standard is: Exact ATA specification draft version not indicated
> > > > > Local Time is: Tue Jan 3 20:01:16 2006 PST
> > > > > SMART support is: Available - device has SMART capability.
> > > > > SMART support is: Enabled
> > > > >
> > > > > === START OF READ SMART DATA SECTION ===
> > > > > SMART overall-health self-assessment test result: PASSED
> > > > >
> > > > > General SMART Values:
> > > > > Offline data collection status: (0x84) Offline data collection activity was
> > > > > suspended by an interrupting command from host.
> > > > > Auto Offline Data Collection: Enabled.
> > > > > Self-test execution status: ( 0) The previous self-test routine completed
> > > > > without error or no self-test has ever
> > > > > been run.
> > > > > Total time to complete Offline
> > > > > data collection: (9600) seconds.
> > > > > Offline data collection
> > > > > capabilities: (0x7b) SMART execute Offline immediate.
> > > > > Auto Offline data collection on/off support.
> > > > > Suspend Offline collection upon new
> > > > > command.
> > > > > Offline surface scan supported.
> > > > > Self-test supported.
> > > > > Conveyance Self-test supported.
> > > > > Selective Self-test supported.
> > > > > SMART capabilities: (0x0003) Saves SMART data before entering
> > > > > power-saving mode.
> > > > > Supports SMART auto save timer.
> > > > > Error logging capability: (0x01) Error logging supported.
> > > > > No General Purpose Logging support.
> > > > > Short self-test routine
> > > > > recommended polling time: ( 2) minutes.
> > > > > Extended self-test routine
> > > > > recommended polling time: ( 116) minutes.
> > > > > Conveyance self-test routine
> > > > > recommended polling time: ( 6) minutes.
> > > > >
> > > > > SMART Attributes Data Structure revision number: 16
> > > > > Vendor Specific SMART Attributes with Thresholds:
> > > > > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
> > > > > 1 Raw_Read_Error_Rate 0x000f 200 200 051 Pre-fail Always - 0
> > > > > 3 Spin_Up_Time 0x0003 188 187 021 Pre-fail Always - 5575
> > > > > 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 86
> > > > > 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
> > > > > 7 Seek_Error_Rate 0x000f 100 253 051 Pre-fail Always - 0
> > > > > 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 33
> > > > > 10 Spin_Retry_Count 0x0013 100 253 051 Pre-fail Always - 0
> > > > > 11 Calibration_Retry_Count 0x0012 100 253 051 Old_age Always - 0
> > > > > 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 85
> > > > > 194 Temperature_Celsius 0x0022 124 100 000 Old_age Always - 26
> > > > > 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
> > > > > 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 0
> > > > > 198 Offline_Uncorrectable 0x0010 200 200 000 Old_age Offline - 0
> > > > > 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
> > > > > 200 Multi_Zone_Error_Rate 0x0009 200 200 051 Pre-fail Offline - 0
> > > > >
> > > > > SMART Error Log Version: 1
> > > > > No Errors Logged
> > > > >
> > > > > SMART Self-test log structure revision number 1
> > > > > No self-tests have been logged. [To run self-tests, use: smartctl -t]
> > > > >
> > > > > That was hde...now for hdf....
> > > > >
> > > > > linux:/home/hexstar # smartctl -a -s on /dev/hdf
> > > > > smartctl version 5.30 Copyright (c) 2002-4 Bruce Allen
> > > > > Home page is http://smartmontools.sourceforge.net/
> > > > >
> > > > > === START OF INFORMATION SECTION ===
> > > > > Device Model: Maxtor 91728D8
> > > > > Serial Number: A809D48C
> > > > > Firmware Version: GAS54112
> > > > > Device is: In smartctl database [for details use: -P show]
> > > > > ATA Version is: 4
> > > > > ATA Standard is: ATA/ATAPI-4 T13 1153D revision 17
> > > > > Local Time is: Tue Jan 3 20:02:32 2006 PST
> > > > > SMART support is: Available - device has SMART capability.
> > > > > SMART support is: Disabled
> > > > >
> > > > > === START OF ENABLE/DISABLE COMMANDS SECTION ===
> > > > > SMART Enabled.
> > > > >
> > > > > === START OF READ SMART DATA SECTION ===
> > > > > SMART overall-health self-assessment test result: PASSED
> > > > >
> > > > > General SMART Values:
> > > > > Offline data collection status: (0x00) Offline data collection activity was
> > > > > never started.
> > > > > Auto Offline Data Collection: Disabled.
> > > > > Total time to complete Offline
> > > > > data collection: ( 0) seconds.
> > > > > Offline data collection
> > > > > capabilities: (0x0f) SMART execute Offline immediate.
> > > > > Auto Offline data collection on/off support.
> > > > > Abort Offline collection upon new
> > > > > command.
> > > > > Offline surface scan supported.
> > > > > No Self-test supported.
> > > > > No Conveyance Self-test supported.
> > > > > No Selective Self-test supported.
> > > > > SMART capabilities: (0x0003) Saves SMART data before entering
> > > > > power-saving mode.
> > > > > Supports SMART auto save timer.
> > > > > Error logging capability: (0x00) Error logging NOT supported.
> > > > > No General Purpose Logging support.
> > > > >
> > > > > SMART Attributes Data Structure revision number: 6
> > > > > Vendor Specific SMART Attributes with Thresholds:
> > > > > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
> > > > > 1 Raw_Read_Error_Rate 0x000b 253 240 000 Pre-fail Always - 446677048288
> > > > > 3 Spin_Up_Time 0x0027 204 204 063 Pre-fail Always - 58
> > > > > 4 Start_Stop_Count 0x0032 253 253 000 Old_age Always - 258
> > > > > 5 Reallocated_Sector_Ct 0x0033 253 253 063 Pre-fail Always - 0
> > > > > 6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail Offline - 0
> > > > > 7 Seek_Error_Rate 0x000a 253 252 000 Old_age Always - 88631
> > > > > 8 Seek_Time_Performance 0x0027 249 247 187 Pre-fail Always - 205058919474216
> > > > > 9 Power_On_Minutes 0x0032 206 206 000 Old_age Always - 16533h+19m
> > > > > 10 Spin_Retry_Count 0x002b 253 252 223 Pre-fail Always - 54
> > > > > 11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail Always - 57
> > > > > 12 Power_Cycle_Count 0x0032 253 253 000 Old_age Always - 334
> > > > > 199 UDMA_CRC_Error_Count 0x0008 199 200 000 Old_age Offline - 0
> > > > > 200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age Always - 423085
> > > > > 201 Soft_Read_Error_Rate 0x000a 253 250 000 Old_age Always - 47245089760
> > > > > 202 TA_Increase_Count 0x000a 253 252 000 Old_age Always - 449504
> > > > > 203 Run_Out_Cancel 0x000a 253 252 000 Old_age Always - 449504
> > > > > 204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age Always - 449504
> > > > > 205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age Always - 449504
> > > > > 206 Flying_Height_Measurement0x0026 224 224 000 Old_age Always - 33406255628354
> > > > > 207 Spin_High_Current 0x002a 253 252 000 Old_age Always - 54
> > > > > 208 Spin_Buzz 0x002a 253 252 000 Old_age Always - 54
> > > > > 209 Offline_Seek_Performnce 0x0024 253 253 000 Old_age Offline - 0
> > > > >
> > > > > Warning: device does not support Error Logging
> > > > > Error SMART Error Log Read failed: Input/output error
> > > > > Smartctl: SMART Error Log Read Failed
> > > > > Warning: device does not support Self Test Logging
> > > > > Error SMART Error Self-Test Log Read failed: Input/output error
> > > > > Smartctl: SMART Self Test Log Read Failed
> > > > >
> > > > > Can I ignore this error? What is this error? Should I do anything?
> > > > >
> > > >
> > > _______________________________________________
> > > CLUE-tech mailing list
> > > CLUE-tech at cluedenver.org
> > > http://cluedenver.org/mailman/listinfo/clue-tech
> > >
> > _______________________________________________
> > CLUE-tech mailing list
> > CLUE-tech at cluedenver.org
> > http://cluedenver.org/mailman/listinfo/clue-tech
> >
>
_______________________________________________
CLUE-tech mailing list
CLUE-tech at cluedenver.org
http://cluedenver.org/mailman/listinfo/clue-tech