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

Sec Slave Hdd Error


  • Please log in to reply
2 replies to this topic

#1 Ayeme

Ayeme

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:12:18 AM

Posted 25 October 2006 - 04:45 AM

The power went out where I live and shut down my main computer. I turned it back on and the following error showed up:

pri master A1y. 1500 quantum fireballp as40.0
ultra dma mode-2. s.m.a.r.t. capable but disabled

Pri slave 1.04 dm-828 1.04 20021010

Sec master 80c4 fujitsu mpg3204at e
ultra dma mode-5 s.m.a.r.t. capable but disabled

sec slave hdd error

I went in to my BIOS and tried the "load fail safe defaults" computer rebooted same error as above occured. I went back into BIOS and tried the "load optimized defaults" rebooted and the same error as above repeated. I went back into BIOS for a third time and enabled the S.M.A.R.T. the system rebooted and now the following error reads.

pri master A1y. 1500 quantum fireballp as40.0
ultra dma mode-2. s.m.a.r.t. capable and status OK

Pri slave 1.04 dm-828 1.04 20021010

Sec master 80c4 fujitsu mpg3204at e
ultra dma mode-5 s.m.a.r.t. capable and status OK

sec slave hdd error

Pressing F1 starts my computer in original format. I went into the device manager and checked the primary and secondary IDE both are running in Ultra DMA.

Any ideas of how I can resolve this issue?

BC AdBot (Login to Remove)

 


#2 Enthusiast

Enthusiast

  • Members
  • 5,898 posts
  • OFFLINE
  •  
  • Location:Florida, USA
  • Local time:12:18 AM

Posted 25 October 2006 - 03:31 PM

I would try physically disconnecting the drive, rebooting, then shutting down the computer, reconnecting the drive and rebooting again.

#3 Ayeme

Ayeme
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:12:18 AM

Posted 28 October 2006 - 01:54 AM

It took some time and playing with the bios but it worked thank you!!!




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users