NASLite Network Attached Storage

www.serverelements.com
Task-specific simplicity with low hardware requirements.
It is currently Mon May 05, 2025 7:10 pm

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 6 posts ] 
Author Message
 Post subject: Unable to access Folder
PostPosted: Sat Sep 13, 2008 7:19 pm 
Offline

Joined: Fri Aug 29, 2008 10:30 pm
Posts: 15
I'm getting this error on my server:

\\Naslite-2\Disk-0\Music is not accessible. You might not have permission to use the network resource. Contact the administrator of this server to find out if you have access permission.

The request could not be performed because of an I/O device error.

Anyone have any idea on why I'm unable to access this folder; nor, is it visible when I go to network places.

I'm completely new to NASLite and to a server environment. I thought it was funny when the error said -- Contact the administrator of this server to find out if you have access permission. Why that's me and I don't have a clue.


CarolinaGuy


Top
 Profile  
 
PostPosted: Sat Sep 13, 2008 9:12 pm 
Offline

Joined: Sun Apr 02, 2006 9:05 pm
Posts: 1688
Location: Up State NY in the USA!!!!
A little more info might help us help you.

What type of machine are you using and what is the OS on it? Have you been able to access it in the past or is it a fresh build? Did you do the unlock on it and is it still valid? What is the NIC in your NL machine? If you have access to the console post up your logs.

Mike


Top
 Profile  
 
PostPosted: Sun Sep 14, 2008 10:14 am 
Offline

Joined: Fri Aug 29, 2008 10:30 pm
Posts: 15
Mike,

Thanks for you help. Here’s all the data. I just attempted to access this again and everything is working fine NOW.


NASLite 2.06 Installed on a PC with an ASUS A7N266-C M/B, 512Meg Memory

Name: NASLite-2
Workgroup: MSHome
Address: 192.168.1.125
OS Version: v2.06 10-2007

The system had been working with no problem:
General:
NASLite-2 HDD is currently unlocked and all supported NAS services are enabled for configuration and use. Note that the System ID and Unlock Code may change if there are changes to the existing network hardware.

System 7.7M 4.7M 3.0M UNAVAILABLE UNAVAILABLE USED 61%
Disk-0 56.4G 6.3G 50.0G READ/WRITE TEMP 27°C USED 11%
Disk-1 36.7G 2.3G 34.4G READ/WRITE DISABLED USED 6%

I formated Disk 0, p2 and labeled it Music. I had WMP 9.0 pointed to that directory and was able to access all my MUSIC.

Any idea why I received an error yesterday and today everything is working fine. I have noticed that DISK 0 is TEMPERATURE is in RED on the SERVER STORAGE PAGE. Yesterday it was at 45C.

CarolinaGuy


Top
 Profile  
 
PostPosted: Sun Sep 14, 2008 12:40 pm 
Offline

Joined: Fri Aug 29, 2008 10:30 pm
Posts: 15
PARTIAL LOGS OVER PAST 2 HOURS:

* Sep 14 10:56:01 user.warn kernel:
* Sep 14 10:56:01 user.err kernel: hda: drive not ready for command
* Sep 14 10:57:01 user.warn kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
* Sep 14 10:57:01 user.warn kernel:
* Sep 14 10:57:01 user.err kernel: hda: drive not ready for command
* Sep 14 10:57:01 user.warn kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
* Sep 14 10:57:01 user.warn kernel:
* Sep 14 10:57:01 user.err kernel: hda: drive not ready for command
* Sep 14 10:57:39 user.warn kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
* Sep 14 10:57:39 user.warn kernel:
* Sep 14 10:57:39 user.err kernel: hda: drive not ready for command
* Sep 14 11:44:11 user.warn kernel: hda: irq timeout: status=0xd0 { Busy }
* Sep 14 11:44:11 user.warn kernel:
* Sep 14 11:44:11 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:44:11 user.warn kernel:
* Sep 14 11:44:11 user.err kernel: hda: drive not ready for command
* Sep 14 11:45:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:45:01 user.warn kernel:
* Sep 14 11:45:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:45:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:45:01 user.warn kernel:
* Sep 14 11:45:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:46:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:46:01 user.warn kernel:
* Sep 14 11:46:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:46:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:46:01 user.warn kernel:
* Sep 14 11:46:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:47:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:47:01 user.warn kernel:
* Sep 14 11:47:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:47:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:47:01 user.warn kernel:
* Sep 14 11:47:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:48:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:48:01 user.warn kernel:
* Sep 14 11:48:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:48:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:48:01 user.warn kernel:
* Sep 14 11:48:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:49:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:49:01 user.warn kernel:
* Sep 14 11:49:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:49:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:49:01 user.warn kernel:
* Sep 14 11:49:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:50:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:50:01 user.warn kernel:
* Sep 14 11:50:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:50:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:50:01 user.warn kernel:
* Sep 14 11:50:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:51:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:51:01 user.warn kernel:
* Sep 14 11:51:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:51:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:51:01 user.warn kernel:
* Sep 14 11:51:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:52:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:52:01 user.warn kernel:
* Sep 14 11:52:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:52:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:52:01 user.warn kernel:
* Sep 14 11:52:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:53:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:53:01 user.warn kernel:
* Sep 14 11:53:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:53:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:53:01 user.warn kernel:
* Sep 14 11:53:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:54:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:54:01 user.warn kernel:
* Sep 14 11:54:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:54:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:54:01 user.warn kernel:
* Sep 14 11:54:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:55:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:55:01 user.warn kernel:
* Sep 14 11:55:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:55:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:55:01 user.warn kernel:
* Sep 14 11:55:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:56:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:56:01 user.warn kernel:
* Sep 14 11:56:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:56:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:56:01 user.warn kernel:
* Sep 14 11:56:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:57:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:57:01 user.warn kernel:
* Sep 14 11:57:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:57:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:57:01 user.warn kernel:
* Sep 14 11:57:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:58:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 11:58:01 user.warn kernel:
* Sep 14 11:58:01 user.err kernel: hda: drive not ready for command
* Sep 14 11:58:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }

* Sep 14 12:03:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:03:01 user.warn kernel:
* Sep 14 12:03:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:04:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:04:01 user.warn kernel:
* Sep 14 12:04:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:04:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:04:01 user.warn kernel:
* Sep 14 12:04:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:05:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:05:01 user.warn kernel:
* Sep 14 12:05:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:05:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:05:01 user.warn kernel:
* Sep 14 12:05:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:06:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:06:01 user.warn kernel:
* Sep 14 12:06:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:06:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:06:01 user.warn kernel:
* Sep 14 12:06:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:07:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:07:01 user.warn kernel:
* Sep 14 12:07:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:07:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:07:01 user.warn kernel:
* Sep 14 12:07:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:08:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:08:01 user.warn kernel:
* Sep 14 12:08:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:08:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:08:01 user.warn kernel:
* Sep 14 12:08:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:09:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:09:01 user.warn kernel:
* Sep 14 12:09:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:09:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:09:01 user.warn kernel:
* Sep 14 12:09:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:10:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:10:01 user.warn kernel:
* Sep 14 12:10:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:10:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:10:01 user.warn kernel:
* Sep 14 12:10:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:11:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:11:01 user.warn kernel:
* Sep 14 12:11:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:11:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:11:01 user.warn kernel:

* Sep 14 12:16:01 user.warn kernel:
* Sep 14 12:16:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:16:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:16:01 user.warn kernel:
* Sep 14 12:16:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:17:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:17:01 user.warn kernel:
* Sep 14 12:17:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:17:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:17:01 user.warn kernel:
* Sep 14 12:17:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:18:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:18:01 user.warn kernel:
* Sep 14 12:18:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:18:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:18:01 user.warn kernel:
* Sep 14 12:18:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:19:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:19:01 user.warn kernel:
* Sep 14 12:19:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:19:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:19:01 user.warn kernel:
* Sep 14 12:19:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:20:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:20:01 user.warn kernel:
* Sep 14 12:20:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:20:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:20:01 user.warn kernel:
* Sep 14 12:20:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:21:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:21:01 user.warn kernel:
* Sep 14 12:21:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:21:02 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:21:02 user.warn kernel:
* Sep 14 12:21:02 user.err kernel: hda: drive not ready for command
* Sep 14 12:22:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:22:01 user.warn kernel:
* Sep 14 12:22:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:22:02 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:22:02 user.warn kernel:
* Sep 14 12:22:02 user.err kernel: hda: drive not ready for command
* Sep 14 12:23:02 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:23:02 user.warn kernel:

* Sep 14 12:28:02 user.warn kernel:
* Sep 14 12:28:02 user.err kernel: hda: drive not ready for command
* Sep 14 12:29:02 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:29:02 user.warn kernel:
* Sep 14 12:29:02 user.err kernel: hda: drive not ready for command
* Sep 14 12:29:02 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:29:02 user.warn kernel:
* Sep 14 12:29:02 user.err kernel: hda: drive not ready for command
* Sep 14 12:30:02 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:30:02 user.warn kernel:
* Sep 14 12:30:02 user.err kernel: hda: drive not ready for command
* Sep 14 12:30:02 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:30:02 user.warn kernel:
* Sep 14 12:30:02 user.err kernel: hda: drive not ready for command
* Sep 14 12:31:02 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:31:02 user.warn kernel:
* Sep 14 12:31:02 user.err kernel: hda: drive not ready for command
* Sep 14 12:31:02 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:31:02 user.warn kernel:
* Sep 14 12:31:02 user.err kernel: hda: drive not ready for command
* Sep 14 12:32:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:32:01 user.warn kernel:
* Sep 14 12:32:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:32:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:32:01 user.warn kernel:
* Sep 14 12:32:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:33:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }

* Sep 14 12:43:01 user.warn kernel:
* Sep 14 12:43:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:43:01 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:43:01 user.warn kernel:
* Sep 14 12:43:01 user.err kernel: hda: drive not ready for command
* Sep 14 12:43:34 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:43:34 user.warn kernel:
* Sep 14 12:43:34 user.info kernel: hda: DMA disabled
* Sep 14 12:43:34 user.err kernel: hda: drive not ready for command
* Sep 14 12:43:34 user.warn kernel: ide0: reset: success
* Sep 14 12:44:04 user.warn kernel: hda: irq timeout: status=0xd0 { Busy }
* Sep 14 12:44:04 user.warn kernel:
* Sep 14 12:44:04 user.warn kernel: ide0: reset: success
* Sep 14 12:44:34 user.warn kernel: hda: irq timeout: status=0xd0 { Busy }
* Sep 14 12:44:34 user.warn kernel:
* Sep 14 12:44:34 user.warn kernel: end_request: I/O error, dev 03:01 (hda), sector 4480
* Sep 14 12:44:34 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:44:34 user.warn kernel:
* Sep 14 12:44:34 user.err kernel: hda: drive not ready for command
* Sep 14 12:44:34 user.warn kernel: ide0: reset: success
* Sep 14 12:45:04 user.warn kernel: hda: irq timeout: status=0xd0 { Busy }
* Sep 14 12:45:04 user.warn kernel:
* Sep 14 12:45:04 user.warn kernel: ide0: reset: success
* Sep 14 12:45:34 user.warn kernel: hda: irq timeout: status=0xd0 { Busy }
* Sep 14 12:45:34 user.warn kernel:
* Sep 14 12:45:34 user.warn kernel: end_request: I/O error, dev 03:01 (hda), sector 4488
* Sep 14 12:45:34 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:45:34 user.warn kernel:
* Sep 14 12:45:34 user.err kernel: hda: drive not ready for command
* Sep 14 12:45:34 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:45:34 user.warn kernel:
* Sep 14 12:45:34 user.err kernel: hda: drive not ready for command
* Sep 14 12:45:35 user.warn kernel: ide0: reset: success
* Sep 14 12:46:05 user.warn kernel: hda: irq timeout: status=0xd0 { Busy }
* Sep 14 12:46:05 user.warn kernel:
* Sep 14 12:46:05 user.warn kernel: ide0: reset: success
* Sep 14 12:46:35 user.warn kernel: hda: irq timeout: status=0xd0 { Busy }
* Sep 14 12:46:35 user.warn kernel:
* Sep 14 12:46:35 user.warn kernel: end_request: I/O error, dev 03:01 (hda), sector 4496
* Sep 14 12:46:35 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:46:35 user.warn kernel:
* Sep 14 12:46:35 user.err kernel: hda: drive not ready for command
* Sep 14 12:46:35 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:46:35 user.warn kernel:
* Sep 14 12:46:35 user.err kernel: hda: drive not ready for command
* Sep 14 12:46:35 user.warn kernel: ide0: reset: success
* Sep 14 12:47:05 user.warn kernel: hda: irq timeout: status=0xd0 { Busy }
* Sep 14 12:47:05 user.warn kernel:
* Sep 14 12:47:05 user.warn kernel: ide0: reset: success
* Sep 14 12:47:35 user.warn kernel: hda: irq timeout: status=0xd0 { Busy }
* Sep 14 12:47:35 user.warn kernel:
* Sep 14 12:47:35 user.warn kernel: end_request: I/O error, dev 03:01 (hda), sector 4504
* Sep 14 12:47:35 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:47:35 user.warn kernel:
* Sep 14 12:47:35 user.err kernel: hda: drive not ready for command
* Sep 14 12:47:35 user.warn kernel: ide0: reset: success
* Sep 14 12:48:05 user.warn kernel: hda: irq timeout: status=0xd0 { Busy }
* Sep 14 12:48:05 user.warn kernel:
* Sep 14 12:48:05 user.warn kernel: ide0: reset: success
* Sep 14 12:48:35 user.warn kernel: hda: irq timeout: status=0xd0 { Busy }
* Sep 14 12:48:35 user.warn kernel:
* Sep 14 12:48:35 user.warn kernel: end_request: I/O error, dev 03:01 (hda), sector 4512
* Sep 14 12:48:35 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:48:35 user.warn kernel:
* Sep 14 12:48:35 user.err kernel: hda: drive not ready for command
* Sep 14 12:48:35 user.warn kernel: ide0: reset: success
* Sep 14 12:49:05 user.warn kernel: hda: irq timeout: status=0xd0 { Busy }
* Sep 14 12:49:05 user.warn kernel:
* Sep 14 12:49:05 user.warn kernel: ide0: reset: success
* Sep 14 12:49:35 user.warn kernel: hda: irq timeout: status=0xd0 { Busy }
* Sep 14 12:49:35 user.warn kernel:
* Sep 14 12:49:35 user.warn kernel: end_request: I/O error, dev 03:01 (hda), sector 56
* Sep 14 12:49:35 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:49:35 user.warn kernel:
* Sep 14 12:49:35 user.err kernel: hda: drive not ready for command
* Sep 14 12:49:35 user.warn kernel: ide0: reset: success
* Sep 14 12:50:05 user.warn kernel: hda: irq timeout: status=0xd0 { Busy }
* Sep 14 12:50:05 user.warn kernel:
* Sep 14 12:50:05 user.warn kernel: ide0: reset: success
* Sep 14 12:50:35 user.warn kernel: hda: irq timeout: status=0xd0 { Busy }
* Sep 14 12:50:35 user.warn kernel:
* Sep 14 12:50:35 user.warn kernel: end_request: I/O error, dev 03:01 (hda), sector 4520
* Sep 14 12:50:35 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:50:35 user.warn kernel:
* Sep 14 12:50:35 user.err kernel: hda: drive not ready for command
* Sep 14 12:50:35 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:50:35 user.warn kernel:
* Sep 14 12:50:35 user.err kernel: hda: drive not ready for command
* Sep 14 12:50:35 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:50:35 user.warn kernel:
* Sep 14 12:50:35 user.err kernel: hda: drive not ready for command
* Sep 14 12:50:35 user.warn kernel: hda: status timeout: status=0xd0 { Busy }
* Sep 14 12:50:35 user.warn kernel:
* Sep 14 12:50:35 user.err kernel: hda: drive not ready for command

Is hda - Drive 0 or Drive 1?

Is this something that I should be concerned about?

CarolinaGuy


Top
 Profile  
 
PostPosted: Sun Sep 14, 2008 3:04 pm 
Offline

Joined: Sun Apr 02, 2006 9:05 pm
Posts: 1688
Location: Up State NY in the USA!!!!
You might just have a IRQ conflict. Go into the BIOS and disable all the devices not used like the printer port and the serial ports etc. Also check the SMART report for warnings about the drive. hda is the disk-0 with hda0 being the first partition on disk-0.

Hope this helps a bit.

Mike


Last edited by mikeiver1 on Wed Sep 17, 2008 12:46 pm, edited 1 time in total.

Top
 Profile  
 
PostPosted: Wed Sep 17, 2008 4:24 am 
Offline

Joined: Thu Oct 11, 2007 1:12 pm
Posts: 28
It's not a flakey hard drive is it? Flakey sector reads. And she stated that she tried it again and all was OK.

Disk/system overheating and causing read errors?

Disk with bad sectors?

Even a format won't necessarily find/fix/disable bad regions.

She also stated that she labelled the Disk Music and she's trying to access Music which should be a directory on the root of that disk.

Accessing a directory called Music that doesnt exist would cause such an error.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 6 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 7 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group