Lost access to eSATA drive - Reboot solved the problem

All questions, comments, discussion about firmware 518 can be placed here. Please place regular support questions in one of the subjects below.
Forum rules
1) This is a user forum for Synology users to share experience/help out each other: if you need direct assistance from the Synology technical support team, please use the following form:

https://account.synology.com/support/su ... p?lang=enu



2) To avoid putting users' DiskStation at risk, please don't paste links to any patches provided by our Support team as we will systematically remove them. Our Support team will provide the correct patch for your DiskStation model.
Jan
Trainee
Trainee
Posts: 19
Joined: Wed Jan 23, 2008 4:05 pm

Lost access to eSATA drive - Reboot solved the problem

Unread post by Jan » Wed Jan 23, 2008 4:37 pm

A strange thing happened to me yesterday.
While trying to connect to a share on the external SATA drive I noticed this share was no longer available.
The other shares were available (the 2 USB drives)
Going to the management console everything seemed to work OK exept for the External Devices/eSATA Disk tab and the Status page. (Both pages contain eSATA information.)
The log files didn't give any information about what could have happened.
Rebooting the DS106 through the management console solved the problem.
I'm not sure this is a Diskstation problem or simply a power glitch that affected my eSATA drive.

I'm running a DS-106 Firmware Version: 2.0.3 - 0518
Internal drive WDC WD2500JD-00HBC0
2 USB drives - 1 of the drives is connected through a USB hub
LaCie, Ltd - LaCie Hard Drive USB 500GB FAT
Genesys Logic, Inc. - USB2.0 Hub
l--> Genesys Logic, Inc. - USB2.0 Hub
l--> JMicron - JM20336 SATA, USB Combo 300GB Native
external eSATA: SAMSUNG HD501LJ 500GB FAT

User avatar
Franklin
Synology Inc
Synology Inc
Posts: 6662
Joined: Sat Oct 14, 2006 11:33 pm
Location: Washington, USA

Unread post by Franklin » Wed Jan 23, 2008 9:47 pm

When attempting to access the eSATA drive, did you wait a few seconds (upwards to 30) to wait for the eSATA drive to spin up? If it is still spinning up, it may appear to your network that the drive no longer existed. Please try again after the drive spins up.

Note, you may also have to wait for the DS drive to spin up first, before you can access the eSATA drive.
**Franklin is not available**
**Please do not Private Message me for support questions; leave it on the forum so all members can learn. Thanks!**
Library ~ SynologyWiki ~ Synology FAQ ~ Compatibility Lists
Forum Links ~ Forum Policy ~ 3rd-party forums ~ Help us help you ~ Posting Images
Demo Links ~ DSM GUI ~ Photo Station
Downloads ~ Firmware Downloads ~ Beta Program
Support ~ Support Form ~ Submit Kernel ~ Synology eNews

Jan
Trainee
Trainee
Posts: 19
Joined: Wed Jan 23, 2008 4:05 pm

Unread post by Jan » Thu Jan 24, 2008 6:17 pm

Franklin,
Don't think that was the problem.
I've waited a couple minutes and tried from different computers to access the share. At first I thought there was a problem with a router or hub. I cycled power on those before I tried to troubleshoot the problem through the management console. So, plenty of time for both the eSATA drive or or DS to 'warm up'
It could be that the eSATA drive didn't wake up from hibernation. But would that be a problem that can be solved by rebooting the DS?

Anyhow,
I can not try anything atm as this problem occurred one once (luckily :wink: )
and everything worked OK after a reboot.

I just wanted to document this in case other users come across the same problem.

Jan
Trainee
Trainee
Posts: 19
Joined: Wed Jan 23, 2008 4:05 pm

Unread post by Jan » Fri Jan 25, 2008 10:00 pm

Lost my eSATA drive again today.
I think it started when I heard a ticking sound coming from the eSATA drive. Head seeking or always moving to its parking position (if that still exists) This ticking noise was at a rate of about once every second and lasted for (I think) 1 minute. then the noise stopped and the SATA share was gone.

This time the management console told me:
You don't have any eSATA device plugged in now.

I cycled power of the eSATA enclosure and the drive was back. (without rebooting the DS)

The system log of the DS had the following information:
2008/01/25 21:44:57 admin External disk [External SATA Disk] is ejected.

blindhope
Beginner
Beginner
Posts: 26
Joined: Wed Jan 03, 2007 4:47 pm
Location: Somerset PA
Contact:

Unread post by blindhope » Sat Jan 26, 2008 1:35 am

Jan how loud was the ticking?

User avatar
NetBoot
Ace
Ace
Posts: 725
Joined: Tue Oct 24, 2006 8:20 pm
Location: Northeastern U.S.

Unread post by NetBoot » Sat Jan 26, 2008 1:18 pm

I had a USB drive do the same thing. It ended up being the enclosure and not the drive. Any way possible you can use another enclosure?

Net....
Product Model: DS-106
Firmware Version: 2.0.3 - 0640

I have my reasons for my insanity....

Jan
Trainee
Trainee
Posts: 19
Joined: Wed Jan 23, 2008 4:05 pm

Unread post by Jan » Sat Jan 26, 2008 2:57 pm

The ticking noise didn't come from the enclosure. (those sound more like 'humming' noise) This ticking sounded like it was head that was being moved to the park position (remember the early days when you manually had to 'park' your HDD? :wink: )
I also took the enclosure in my hand and the ticking didn't stop. (Humming resonance noise would have stopped if that was the problem.)

I do have a second enclosure (same as the one I'm having trouble with) that is connected to the DS through USB. I could swap them but I never had this problem before I upgraded to 0518.

User avatar
NetBoot
Ace
Ace
Posts: 725
Joined: Tue Oct 24, 2006 8:20 pm
Location: Northeastern U.S.

Unread post by NetBoot » Sat Jan 26, 2008 3:15 pm

Well, it's not what you stated.

***snip***
This ticking noise was at a rate of about once every second and lasted for (I think) 1 minute.
***snip***

Yes, I do remember when you had to park a hard drive. In the field for over 20 years.

***snip***
I also took the enclosure in my hand and the ticking didn't stop. (Humming resonance noise would have stopped if that was the problem.)
***snip***

All hard drives have a humming resonating sound. Holding the enclosure will not stop it from ticking. The ticking is the Synology box trying to read the hard drive and your probably getting I/O errors which is causing the ticking.

To verify this, you can enable telnet on your Synology box. Telnet in and run the command

cat /var/log/messages

See if there are I/O errors.

Net....
Product Model: DS-106
Firmware Version: 2.0.3 - 0640

I have my reasons for my insanity....

Jan
Trainee
Trainee
Posts: 19
Joined: Wed Jan 23, 2008 4:05 pm

Unread post by Jan » Sat Jan 26, 2008 3:43 pm

Netboot,
Thanks for your reply!

It could indeed be that the DS is having problems reading from the drive. That could/would sound the same.

Here is the log from the 2nd time the eSATA drive disappeared:
Jan 25 21:44:55 kernel: ide1: reset phy, status=0x00000113, siimage_reset
Jan 25 21:44:56 hotplugd: ACTION:remove.
Jan 25 21:44:56 hotplugd: DEVNAME:hdc.
Jan 25 21:44:56 hotplugd: DEVICE:.
Jan 25 21:44:56 hotplugd: DEVGUID:.
Jan 25 21:44:56 hotplugd: hotplugd.c (265) ==== eSATA disk [hdc] plugged out====
Jan 25 21:44:56 hotplugd: SYNOReadOneSectorFromDev(1600): failed to open device [/dev/hdc] (errno = 6)
Jan 25 21:44:56 hotplugd: synoshare: delete share satashare ......
Jan 25 21:44:57 kernel: FAT bread failed in fat_clusters_flush
Jan 25 21:44:57 kernel: SYNOFatBmapRelease: release bmap indirect
Jan 25 21:44:57 hotplugd: USB disk is polled out.

The first time it happened gave about 200 lines of:
Jan 22 19:03:23 kernel: hdc: lost interrupt
Jan 22 19:03:43 kernel: hdc: lost interrupt
Jan 22 19:03:58 kernel: hdc: lost interrupt
until the DS was rebooted.

Hope this helps!

And thank you for the tip to have a look at /var/log/messages

Jan

User avatar
NetBoot
Ace
Ace
Posts: 725
Joined: Tue Oct 24, 2006 8:20 pm
Location: Northeastern U.S.

Unread post by NetBoot » Sat Jan 26, 2008 3:58 pm

I would go ahead and put in a support ticket on that.

You may ask Franklin if the 524 firmware addresses this issue.

Net....
Product Model: DS-106
Firmware Version: 2.0.3 - 0640

I have my reasons for my insanity....

wardog
Versed
Versed
Posts: 238
Joined: Fri Nov 02, 2007 6:32 am

Unread post by wardog » Sun Jan 27, 2008 1:55 am

Any chance you're not properly disconnecting(ejecting) the esata drive prior to reconnecting it to the 106?

Or maybe not properly connecting(introducing) the esata drive?

I've seen bits of the logs you posted before and IIRC it related to a user attempting to hotplug and/or hotUNplug an external esata drive. Again, IIRC, it related to the way the user was connecting and disconnecting the device which was shared between Windows and linux.
DS-207 | Two Hitachi E7K500 HDS725050KLA360 (0A32412) 500GB HD's
DS-207 | Two Hitachi 7K1000 HDS721010KLA330 (0A33863) 1TB HD's

wardog
Versed
Versed
Posts: 238
Joined: Fri Nov 02, 2007 6:32 am

Unread post by wardog » Sun Jan 27, 2008 2:01 am

wardog wrote:Any chance you're not properly disconnecting(ejecting) the esata drive prior to reconnecting it to the 106?

Or maybe not properly connecting(introducing) the esata drive?

......... IIRC, it related to the way the user was connecting and disconnecting the device which was shared between Windows and linux.
That a reboot of either device resolves this leads me to ask the above two questions.

Then again, I've been known to not have a clue of what I speak :P 8)
DS-207 | Two Hitachi E7K500 HDS725050KLA360 (0A32412) 500GB HD's
DS-207 | Two Hitachi 7K1000 HDS721010KLA330 (0A33863) 1TB HD's

Jan
Trainee
Trainee
Posts: 19
Joined: Wed Jan 23, 2008 4:05 pm

Unread post by Jan » Sun Jan 27, 2008 6:42 pm

wardog wrote:
Then again, I've been known to not have a clue of what I speak :P 8)
:lol:

Wardog,

It could be that the eSATA device somehow 'failed' and caused a not so clean disconnect. But when these disconnects happened nobody was near the device nor was there network traffice.

I've entered a ticket for this issue, see what they say....

Locked

Return to “Firmware 518 for x07, x06, DS-101j Models”