Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Error Oxc00000f a required device is inaccessible


  • Please log in to reply
13 replies to this topic

#1 Requiem7

Requiem7

  • Members
  • 44 posts
  • OFFLINE
  •  
  • Local time:10:29 PM

Posted 04 May 2016 - 12:34 PM

Hello,

 

I'm getting this error message:Error Oxc00000f a required device is inaccessible on my Alien laptop computer with Vista. I tried using the repair disk it didn't work I tried to reinstall vista and that didn't work.  I've been searching the net trying various fixs people say that work for them but no luck.  Does anyone have anymore advice or do I have to accept the fact that I just got a brick .

 

Phillip 



BC AdBot (Login to Remove)

 


#2 JohnC_21

JohnC_21

  • Members
  • 24,289 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:29 PM

Posted 04 May 2016 - 02:43 PM

Sounds like a hard drive issue. Download the UBCD iso. Create a bootable disk and at the main menu select Parted Magic, At the Parted Magic desktop click on Disk Health and run the short/long tests.

 

If you do not have burning program that can burn a disk image you can use Imgburn. If you have a spare flash drive you can use Rufus to create a bootable USB flash drive.



#3 Requiem7

Requiem7
  • Topic Starter

  • Members
  • 44 posts
  • OFFLINE
  •  
  • Local time:10:29 PM

Posted 05 May 2016 - 10:20 AM

Will do. Will get back to you when done. 



#4 Requiem7

Requiem7
  • Topic Starter

  • Members
  • 44 posts
  • OFFLINE
  •  
  • Local time:10:29 PM

Posted 05 May 2016 - 05:44 PM

Ok, this is what I got:

smartctl 5.43 2012-06-30 r3573 [i686-linux-3.10.4-pmagic] (local build)
Copyright © 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Momentus 7200.1
Device Model:     ST910021AS
Serial Number:    3MH0EV4N
Firmware Version: 3.06
User Capacity:    100,030,242,816 bytes [100 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Thu May  5 18:35:58 2016 AKDT
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
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status:  (0x82)    Offline data collection activity
                    was completed without error.
                    Auto Offline Data Collection: Enabled.
Self-test execution status:      ( 121)    The previous self-test completed having
                    the read element of the test failed.
Total time to complete Offline
data collection:         (  426) seconds.
Offline data collection
capabilities:              (0x5b) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    Offline surface scan supported.
                    Self-test supported.
                    No 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:      (   1) minutes.
Extended self-test routine
recommended polling time:      ( 111) minutes.
SCT capabilities:            (0x0001)    SCT Status supported.

SMART Attributes Data Structure revision number: 10
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   100   253   006    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0003   094   092   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   099   099   020    Old_age   Always       -       1957
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       35
  7 Seek_Error_Rate         0x000f   077   060   030    Pre-fail  Always       -       21768035390
  9 Power_On_Hours          0x0032   096   096   000    Old_age   Always       -       3890
 10 Spin_Retry_Count        0x0013   100   099   034    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   099   099   020    Old_age   Always       -       1957
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       6139
189 High_Fly_Writes         0x003a   001   001   000    Old_age   Always       -       376
190 Airflow_Temperature_Cel 0x0022   065   039   045    Old_age   Always   In_the_past 35 (0 4 35 22 0)
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       337
193 Load_Cycle_Count        0x0032   080   080   000    Old_age   Always       -       40106
194 Temperature_Celsius     0x0022   035   061   000    Old_age   Always       -       35 (0 14 0 0 0)
195 Hardware_ECC_Recovered  0x001a   083   045   000    Old_age   Always       -       110745351
197 Current_Pending_Sector  0x0012   088   088   000    Old_age   Always       -       260
198 Offline_Uncorrectable   0x0010   088   088   000    Old_age   Offline      -       260
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0
202 Data_Address_Mark_Errs  0x0032   100   253   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 3469 (device log contains only the most recent five errors)
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 3469 occurred at disk power-on lifetime: 3889 hours (162 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 16 89 9d e2  Error: UNC at LBA = 0x029d8916 = 43878678

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 80 af 88 9d e2 00      00:04:25.760  READ DMA
  ca 00 8f c7 75 b5 e4 00      00:04:25.749  WRITE DMA
  c8 00 08 af 88 9d e2 00      00:04:25.748  READ DMA
  ca 00 8a 07 e8 9e e4 00      00:04:25.734  WRITE DMA
  c8 00 80 af 88 9d e2 00      00:04:25.734  READ DMA

Error 3468 occurred at disk power-on lifetime: 3889 hours (162 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 16 89 9d e2  Error: UNC at LBA = 0x029d8916 = 43878678

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 80 af 88 9d e2 00      00:04:25.760  READ DMA
  c8 00 07 ff 1f a0 e2 00      00:04:25.749  READ DMA
  c8 00 80 7f 1f a0 e2 00      00:04:25.748  READ DMA
  c8 00 08 af 09 61 e0 00      00:04:25.734  READ DMA
  c8 00 08 e7 06 99 e2 00      00:04:25.734  READ DMA

Error 3467 occurred at disk power-on lifetime: 3889 hours (162 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 1b 44 bb e0  Error: UNC at LBA = 0x00bb441b = 12272667

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 00 4f 43 bb e0 00      00:04:19.991  READ DMA
  c8 00 00 4f 42 bb e0 00      00:04:17.689  READ DMA
  c8 00 00 4f 41 bb e0 00      00:04:17.688  READ DMA
  c8 00 00 4f 40 bb e0 00      00:04:17.688  READ DMA
  c8 00 00 4f 3f bb e0 00      00:04:17.688  READ DMA

Error 3466 occurred at disk power-on lifetime: 3889 hours (162 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 1b 41 bb e0  Error: UNC at LBA = 0x00bb411b = 12271899

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 00 4f 40 bb e0 00      00:04:19.991  READ DMA
  c8 00 00 4f 3f bb e0 00      00:04:17.689  READ DMA
  c8 00 00 4f 3e bb e0 00      00:04:17.688  READ DMA
  c8 00 00 4f 3d bb e0 00      00:04:17.688  READ DMA
  ca 00 08 ef 02 02 e0 00      00:04:17.688  WRITE DMA

Error 3465 occurred at disk power-on lifetime: 3889 hours (162 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 1b 3e bb e0  Error: UNC at LBA = 0x00bb3e1b = 12271131

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 00 4f 3d bb e0 00      00:04:10.760  READ DMA
  ca 00 08 ef 02 02 e0 00      00:04:17.689  WRITE DMA
  ca 00 08 df c2 01 e0 00      00:04:17.688  WRITE DMA
  c8 00 30 4f 45 bb e0 00      00:04:17.688  READ DMA
  c8 00 00 4f 44 bb e0 00      00:04:17.688  READ DMA

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       90%      3890         12271899
# 2  Extended offline    Completed: read failure       90%      3890         12271899
# 3  Short offline       Completed: read failure       90%      3890         12271899

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.



#5 JohnC_21

JohnC_21

  • Members
  • 24,289 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:29 PM

Posted 05 May 2016 - 06:01 PM

You have quite a few pending sectors that cannot be read. The DMA errors could be due to a bad controller or SATA cable if you have a desktop. Try a new SATA cable and or change SATA ports on the motherboard. I would pull the data from the drive by attaching it to another computer using a USB enclosure or adapter. Another option is to pull the data using Parted Magic to an external drive. 

 

If replacing the SATA cable does not solve the problem then purchase a new drive.

 

Just a note: Vista will no longer be supported with Security Updates after April 2017. You may want to look at purchasing a new computer if your budget allows or use a different OS such as Linux Mint or Ubuntu as Vista is not allowed the free upgrade to Windows 10.



#6 Requiem7

Requiem7
  • Topic Starter

  • Members
  • 44 posts
  • OFFLINE
  •  
  • Local time:10:29 PM

Posted 06 May 2016 - 08:39 AM

Right now I only use the laptop to hook up to our TV downstairs to play Netfilx, it's older TV.  Chrome Cast will not work on it.  But I think you are right the drive is just gone and the most use I got out it was years ago when I would game from bed. I should try getting a new drive and see if that works and then would windows 10 work good on it is the question or might be time for a new laptop or I need to find another way to hook up the TV to play netfix. 



#7 JohnC_21

JohnC_21

  • Members
  • 24,289 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:29 PM

Posted 06 May 2016 - 09:12 AM

You would still need to purchase Windows 10 as the upgrade is only for Windows 7 or 10. 

 

Windows 10 may have a problem running depending on the computer specs. Do you have a model number of the Alien. If you play Netflix through a browser then linux should work fine. At least you would only need to purchase a new drive to find out. If it is a controller problem then you could still put the drive into an enclosure and use it for backup purposes.

 

http://www.makeuseof.com/tag/watch-netflix-natively-linux-easy-way/

 

http://www.pcworld.com/article/2824623/ubuntu-linux-gets-netflix-without-weird-workarounds.html



#8 Requiem7

Requiem7
  • Topic Starter

  • Members
  • 44 posts
  • OFFLINE
  •  
  • Local time:10:29 PM

Posted 06 May 2016 - 10:41 AM

Its an Area-51 m5550



#9 JohnC_21

JohnC_21

  • Members
  • 24,289 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:29 PM

Posted 06 May 2016 - 11:12 AM

Windows 10 should run fine but there may be an issue with drivers such as your Wifi and printer if you have one.

 

The linux distros I mentioned would run very well on it.



#10 Tomsonn

Tomsonn

  • Banned Spammer
  • 40 posts
  • OFFLINE
  •  
  • Local time:06:29 PM

Posted 10 May 2016 - 02:12 AM

Well if it is indeed a hard disk issue then there is a solution. But I am afraid you would not like it. 
Have you ever heard of "low level format" ? I think it is the solution, but it will take a week (without any break or pause) or maybe a week and few days. 
Good luck



#11 Requiem7

Requiem7
  • Topic Starter

  • Members
  • 44 posts
  • OFFLINE
  •  
  • Local time:10:29 PM

Posted 10 May 2016 - 04:22 PM

Well if it is indeed a hard disk issue then there is a solution. But I am afraid you would not like it. 
Have you ever heard of "low level format" ? I think it is the solution, but it will take a week (without any break or pause) or maybe a week and few days. 
Good luck

What is low level format? 



#12 JohnC_21

JohnC_21

  • Members
  • 24,289 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:29 PM

Posted 10 May 2016 - 06:02 PM

There is no low-level format on modern drives. Today Low Level Format means writing zeros to every sector of the hard drive. On a large drive it will not take a week but could take hours on a large drive.

 

No software of any sort can truly low-level format today's modern drives. The ability to low-level format hard drives was lost back in the early 1990's when disc surfaces began incorporating factory written "embedded servo data". 

 

 

You can zero out the drive using a utility like HDDGuru  Low Level Format . Partition Wizard can also do it on an external drive. Using Seatools for Dos can be used to repair bad sectors using the long test but it cannot be used on an external hard drive.



#13 Requiem7

Requiem7
  • Topic Starter

  • Members
  • 44 posts
  • OFFLINE
  •  
  • Local time:10:29 PM

Posted 12 May 2016 - 04:45 PM

There is no low-level format on modern drives. Today Low Level Format means writing zeros to every sector of the hard drive. On a large drive it will not take a week but could take hours on a large drive.

 

No software of any sort can truly low-level format today's modern drives. The ability to low-level format hard drives was lost back in the early 1990's when disc surfaces began incorporating factory written "embedded servo data". 

 

 

You can zero out the drive using a utility like HDDGuru  Low Level Format . Partition Wizard can also do it on an external drive. Using Seatools for Dos can be used to repair bad sectors using the long test but it cannot be used on an external hard drive.

The question I have how do I install this program on to the labtop? 



#14 Fascist Nation

Fascist Nation

  • Members
  • 110 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Phoenix, AZ
  • Local time:07:29 PM

Posted 12 May 2016 - 05:15 PM

Thank you JohnC, there is no low level format. 

 

The Seagate drive passed the Seagate check.  It is likely good.  Since it is a laptop it isn't the cable.  That leaves, as JohnC listed the motherboard's SATA controller as the likely suspect.  Which if true means the laptop is kaput (not worth repairing). 

 

Test either by putting boot drive on another PC as a secondary or external drive using a transfer cable or ext. drive case (<$20).  Or buy a new 2.5" drive and poke it in and see if you can get it going...though generally you would use a transfer cable if the drive was still limping along to image the new drive for convenience.  Otherwise you need an OS disk/recovery disk.


Edited by Fascist Nation, 12 May 2016 - 05:21 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users