General NAS-Central Forums

Welcome to the NAS community
It is currently Fri Oct 31, 2014 8:34 pm

All times are UTC




Post new topic Reply to topic  [ 34 posts ]  Go to page 1, 2, 3  Next
Author Message
PostPosted: Thu Apr 14, 2011 5:08 pm 
Offline

Joined: Thu Apr 14, 2011 4:54 pm
Posts: 2
Hope someone can help me, or even if a fix is possible.
My 1TB Home Media Network Drive powers up, white light goes on, blue light flashes a bit, then both lights go out and stay off. All I hear is the fan running.
No computer (XP or Win 7) can find it on the network and the Iomega manager also has no devices found.
It worked fine until I has to change my router but since the new one couldn't find it, I went back to the old one but the drive is still gone.
Any steps to troubleshoot or even better to a solution?


Top
 Profile  
 
PostPosted: Thu Apr 14, 2011 5:51 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 4564
Hm. Both leds off is not a valid condition, according to the wiki.
Have you already tried a factory reset?


Top
 Profile  
 
PostPosted: Thu Apr 14, 2011 6:58 pm 
Offline

Joined: Thu Apr 14, 2011 4:54 pm
Posts: 2
You can see exactly what the lights do here: http://www.youtube.com/watch?v=9y3mzL7U8kg
The power button and the reset button do not do anything when pressed, and I did hold down the reset for 5 seconds. Iomega support said the issue might be the power cable, but its the same Iomega power cord that came with the unit, plus the unit lights up, then nothing, but the fan keeps running.
Is there a way to reinstall the firmware into the drive? Would that possibly fix it?


Top
 Profile  
 
PostPosted: Fri Apr 15, 2011 11:23 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 4564
grandzu wrote:
Is there a way to reinstall the firmware into the drive? Would that possibly fix it?
Could be. It's seems to me the disk is OK. The time the blue LED is blinking is enough to have the box booted into it's rootfs. So maybe some startscript is damaged, leaving the box here.
But another possibility is that you fried your network port with the new router, and that the kernel crashes when trying to initialize it.

Anyway, (re-)installing the firmware is discussed here. In your case only a subset is needed, I think. The commands
Code:
mke2fs -j /dev/sdb1
mkdir /tmp/sdb1
mount /dev/sdb1 /tmp/sdb1
cd /tmp/sdb1
tar -xzf /full/path/to/sda1-2064.tgz
should do, *after* you have checked that /dev/sdb1 is the right paritition, of course.


Top
 Profile  
 
PostPosted: Sun May 29, 2011 6:40 pm 
Offline

Joined: Sun May 29, 2011 6:11 pm
Posts: 6
Hi Mijzelf,

I am having the same issue. When looking at diskutility, it finds the hard drive but the partitions are unknown. On trying the mount the drive, it asks to specify a file type and I am not too sure about that.....

As you can guess...I am a total newbie and I have ubuntu running from a usb with hard drive connected via sata/usb...

Would appreciate any help!

Thanks

Rohan


Top
 Profile  
 
PostPosted: Mon May 30, 2011 7:37 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 4564
That sounds bad. The disk has 3 partitions, the first one (4GB) being ext3, the second one (490+GB) xfs, and the third one (24MB) has no filesystem. (BTW, this are the logical indexes. In reality the 3rd partition is the first one on the disk.)
The bad thing is that Ubuntu should recognize the filesystems automatically. So something is damaged. But it doesn't hurt to specify the right filesystem.
I suppose you first want to rescue your data. In that case you don't need to bother about the 1st and 3rd partition. Only the 2nd one contains userdata, the rest is firmware.


Top
 Profile  
 
PostPosted: Tue May 31, 2011 2:32 am 
Offline

Joined: Sun May 29, 2011 6:11 pm
Posts: 6
You are right...I am only interested in retrieving my data. Does that mean that I mount only that partition? After I do that, how do I retrieve my data.

Thanks for your help!

Rohan


Top
 Profile  
 
PostPosted: Tue May 31, 2011 8:22 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 4564
You can mount that partition with the commands:
Code:
# create mountpoint
mkdir /tmp/data
# find out which partition to mount:
cat /proc/partitions
# The partition size is given in kB.
# Assuming it's sdb2, mount it:
sudo mount /dev/sdb2 /tmp/data
# When it fails, because of a not recognized filesystem, try:
sudo mount -t xfs /dev/sdb2 /tmp/data
When this succeeds you can use the GUI to copy your data from /tmp/data elsewhere. (To a different disk, of course).
When this doesn't succeed, post the output of
Code:
dmesg | tail -n 30


Top
 Profile  
 
PostPosted: Wed Jun 01, 2011 1:17 am 
Offline

Joined: Sun May 29, 2011 6:11 pm
Posts: 6
Tried what you said...it still gave me the file type error and so I specified the command as you suggested and I got an error saying cant read superblock.

Here is the error:

ubuntu@ubuntu:~$ sudo mount -t xfs /dev/sdc2 /tmp/data
mount: /dev/sdc2: can't read superblock
ubuntu@ubuntu:~$ dmesg | tail -n 30
[ 323.262112] sd 6:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 323.262119] sd 6:0:0:0: [sdc] Sense Key : Hardware Error [current]
[ 323.262126] sd 6:0:0:0: [sdc] Add. Sense: No additional sense information
[ 323.262134] sd 6:0:0:0: [sdc] CDB: Read(10): 28 00 00 7e 3e c3 00 00 08 00
[ 323.262150] end_request: I/O error, dev sdc, sector 8273603
[ 323.268246] sd 6:0:0:0: [sdc] Unhandled sense code
[ 323.268251] sd 6:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 323.268257] sd 6:0:0:0: [sdc] Sense Key : Hardware Error [current]
[ 323.268264] sd 6:0:0:0: [sdc] Add. Sense: No additional sense information
[ 323.268272] sd 6:0:0:0: [sdc] CDB: Read(10): 28 00 00 7e 3e 43 00 00 08 00
[ 323.268289] end_request: I/O error, dev sdc, sector 8273475
[ 323.274360] sd 6:0:0:0: [sdc] Unhandled sense code
[ 323.274364] sd 6:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 323.274370] sd 6:0:0:0: [sdc] Sense Key : Hardware Error [current]
[ 323.274377] sd 6:0:0:0: [sdc] Add. Sense: No additional sense information
[ 323.274385] sd 6:0:0:0: [sdc] CDB: Read(10): 28 00 00 7e 3e 43 00 00 08 00
[ 323.274402] end_request: I/O error, dev sdc, sector 8273475
[ 323.280494] sd 6:0:0:0: [sdc] Unhandled sense code
[ 323.280498] sd 6:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 323.280504] sd 6:0:0:0: [sdc] Sense Key : Hardware Error [current]
[ 323.280512] sd 6:0:0:0: [sdc] Add. Sense: No additional sense information
[ 323.280520] sd 6:0:0:0: [sdc] CDB: Read(10): 28 00 00 7e 4e 43 00 00 08 00
[ 323.280536] end_request: I/O error, dev sdc, sector 8277571
[ 344.357247] sd 6:0:0:0: [sdc] Unhandled sense code
[ 344.357252] sd 6:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 344.357256] sd 6:0:0:0: [sdc] Sense Key : Hardware Error [current]
[ 344.357261] sd 6:0:0:0: [sdc] Add. Sense: No additional sense information
[ 344.357267] sd 6:0:0:0: [sdc] CDB: Read(10): 28 00 00 7e 3e 43 00 00 01 00
[ 344.357278] end_request: I/O error, dev sdc, sector 8273475
[ 344.357314] XFS: SB buffer read failed
ubuntu@ubuntu:~$


All I am hoping to do at this point is somehow retrieve the data!

Thanks in advance!

Rohan


Top
 Profile  
 
PostPosted: Wed Jun 01, 2011 1:34 am 
Offline

Joined: Sun May 29, 2011 6:11 pm
Posts: 6
Also tried xfs check and repair commands....no luck!

root@ubuntu:/home/ubuntu# sudo xfs_check /dev/sdc2
xfs_check: /dev/sdc2 is invalid (cannot read first 512 bytes)
root@ubuntu:/home/ubuntu# sudo xfs_repair /dev/sdc2
Phase 1 - find and verify superblock...
superblock read failed, offset 0, size 524288, ag 0, rval -1

fatal error -- Input/output error
root@ubuntu:/home/ubuntu# # dumpe2fs /dev/sdc2 | grep superblock
root@ubuntu:/home/ubuntu# dumpe2fs /dev/sdc2 | grep superblock
dumpe2fs 1.41.14 (22-Dec-2010)
dumpe2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/sdc2
Couldn't find valid filesystem superblock.


Top
 Profile  
 
PostPosted: Wed Jun 01, 2011 7:38 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 4564
Quote:
[ 323.268251] sd 6:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 323.268257] sd 6:0:0:0: [sdc] Sense Key : Hardware Error [current]
This is a hardware error. So either your disk or your USB-Sata controller is defective. What did the NAS status led do? When that was 'alternating white/red' or 'solid red', then I'm afraid your disk is dead. When it was something else, then the USB-Sata controller could be the problem, or the power supply (or your USB port? Don't think so).

On the other hand, the partition table is recognized, so *something* is still alive. You could try to clone your data partition to another disk using ddrescue. (That will last a *long* time, maybe several days). Then you could try xfs repair (and/or PhotoRec, depending on the nature of the data) on the copy (or the copy of the copy, if you have the diskspace).

When your data is really valuable, you should stop now, and bring the disk to a professional data recovery company.


Top
 Profile  
 
PostPosted: Wed Jun 01, 2011 1:35 pm 
Offline

Joined: Sun May 29, 2011 6:11 pm
Posts: 6
I just bought the usb/sata controller.... regarding the lights: on plugging in blinking white light and then blinking blue light and then both out. Disk is still spinning and no weird noises.

Data is personal stuff like pics which are a treasured memory but not worth the cost of a data recovery company.

Will try ddrescue...

BTW...can I run ddrescue when running ubuntu from a usb?


Top
 Profile  
 
PostPosted: Wed Jun 01, 2011 2:11 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 4564
rohancd wrote:
regarding the lights: on plugging in blinking white light and then blinking blue light and then both out. Disk is still spinning and no weird noises.
Hm. This is not valid condition, at least it's not documented by Iomega. But I suppose it could be a sign of a defective disk.
Quote:
BTW...can I run ddrescue when running ubuntu from a usb?
Yes. No problem. It is possible that you have to (re)install it after each boot, that would be the case when booted from CD rom.


Top
 Profile  
 
PostPosted: Sat Aug 27, 2011 9:30 pm 
Offline

Joined: Sat Aug 27, 2011 9:26 pm
Posts: 1
I have the same issue but my log results are different:

araote@ubuntu:~$ sudo mount -t xfs /dev/sdb2 /tmp/sdb2
mount: /dev/sdb2: can't read superblock
araote@ubuntu:~$ dmesg | tail -n 30
[ 6033.025467] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 6033.025477] ata2.00: BMDMA stat 0x4
[ 6033.025485] ata2.00: failed command: READ DMA
[ 6033.025501] ata2.00: cmd c8/00:08:23:4d:5f/00:00:00:00:00/e2 tag 0 dma 4096 in
[ 6033.025504] res 51/40:00:25:4d:5f/40:00:57:00:00/02 Emask 0x9 (media error)
[ 6033.025511] ata2.00: status: { DRDY ERR }
[ 6033.025516] ata2.00: error: { UNC }
[ 6033.200228] ata2.00: configured for UDMA/133
[ 6033.200257] ata2: EH complete
[ 6036.090426] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 6036.090436] ata2.00: BMDMA stat 0x4
[ 6036.090444] ata2.00: failed command: READ DMA
[ 6036.090459] ata2.00: cmd c8/00:08:23:4d:5f/00:00:00:00:00/e2 tag 0 dma 4096 in
[ 6036.090462] res 51/40:00:25:4d:5f/40:00:57:00:00/02 Emask 0x9 (media error)
[ 6036.090469] ata2.00: status: { DRDY ERR }
[ 6036.090474] ata2.00: error: { UNC }
[ 6036.430242] ata2.00: configured for UDMA/133
[ 6036.430274] sd 1:0:0:0: [sdb] Unhandled sense code
[ 6036.430280] sd 1:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 6036.430288] sd 1:0:0:0: [sdb] Sense Key : Medium Error [current] [descriptor]
[ 6036.430298] Descriptor sense data with sense descriptors (in hex):
[ 6036.430303] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 6036.430322] 02 5f 4d 25
[ 6036.430331] sd 1:0:0:0: [sdb] Add. Sense: Unrecovered read error - auto reallocate failed
[ 6036.430341] sd 1:0:0:0: [sdb] CDB: Read(10): 28 00 02 5f 4d 23 00 00 08 00
[ 6036.430358] end_request: I/O error, dev sdb, sector 39800101
[ 6036.430416] ata2: EH complete
[ 6036.430431] I/O error in filesystem ("sdb2") meta-data dev sdb2 block 0x1e10ee0 ("xlog_recover_do..(read#1)") error 5 buf count 4096
[ 6036.430460] XFS: log mount/recovery failed: error 5
[ 6036.430554] XFS: log mount failed

What can I do next?


Top
 Profile  
 
PostPosted: Sun Aug 28, 2011 11:45 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 4564
You connected the disk to a SATA port, I presume? I'm not an expert, but it looks to me as if the DMA transfer fails. That is also a hardware error. Maybe the same one, when accessing the disk via a USB-SATA controller things look different, from the kernels point of view.
So basically you can try the same. Try ddrescue to get a raw copy of the disk, and try to recover your data from the copy. Or stop immediately and bring the disk to a professional data recovery company.
Unfortunately rohancd never reported back if he saved his data.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 34 posts ]  Go to page 1, 2, 3  Next

All times are UTC


Who is online

Users browsing this forum: No registered users and 12 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:  
Powered by phpBB® Forum Software © phpBB Group