General NAS-Central Forums

Welcome to the NAS community
It is currently Mon Jul 24, 2017 8:29 pm

All times are UTC




Post new topic Reply to topic  [ 9 posts ] 
Author Message
 Post subject: MHNDHD frozen
PostPosted: Thu Mar 12, 2015 9:00 pm 
Offline

Joined: Thu Mar 12, 2015 8:57 pm
Posts: 2
Hi, my MHNDHD disc broke and tried eh replace it using the following link: http://iomega.nas-central.org/wiki/Inst ... Home_Media ) and all is well .
The problem is that after a few days of use I can no longer access the disk , and can only responds to ping but can not be accessed by http or data , turning off and turning on the NAS works again .
Probe with several different sizes and disk brand and to even put a fan as it could be a temperature problem , but nothing does it work more than a few days, something happens ?


Top
 Profile  
 
 Post subject: Re: MHNDHD frozen
PostPosted: Sat Mar 28, 2015 6:22 pm 
Offline

Joined: Sat Mar 28, 2015 3:13 pm
Posts: 5
I have the same issue.
No idea what is happening.


Top
 Profile  
 
 Post subject: Re: MHNDHD frozen
PostPosted: Mon Mar 30, 2015 7:40 pm 
Offline

Joined: Fri Apr 08, 2011 9:59 am
Posts: 160
If you have ssh (or telnet) could you post the result of dmesg?

Other than that you could run a crontab that reboots the NAS every day or something.


Top
 Profile  
 
 Post subject: Re: MHNDHD frozen
PostPosted: Wed Apr 01, 2015 9:03 pm 
Offline

Joined: Sat Mar 28, 2015 3:13 pm
Posts: 5
No reaction on telnet, port 80 for webportal etc. But the autorestart with cron is a good idea. I'll test this.


Top
 Profile  
 
 Post subject: Re: MHNDHD frozen
PostPosted: Thu Apr 02, 2015 10:42 am 
Offline

Joined: Fri Apr 08, 2011 9:59 am
Posts: 160
I meant getting the results from dmesg after the nas restarted and is working. You can get telnet access by following this guide.


Top
 Profile  
 
 Post subject: Re: MHNDHD frozen
PostPosted: Sat Apr 04, 2015 12:36 pm 
Offline

Joined: Sat Mar 28, 2015 3:13 pm
Posts: 5
Driminicus wrote:
I meant getting the results from dmesg after the nas restarted and is working. You can get telnet access by following this guide.


below the output of dmesg
---

Linux version 2.6.24.4 (gp@mactel1.local) (gcc version 4.3.2 (crosstool-NG-1.3.1) ) #1 Mon Jun 1 11:21:53 MDT 2009
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: Oxsemi NAS
Ignoring unrecognised tag 0x00000000
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 16384
DMA zone: 128 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 16256 pages, LIFO batch:3
Normal zone: 0 pages used for memmap
Movable zone: 0 pages used for memmap
CPU0: D VIVT write-back cache
CPU0: I cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets
CPU0: D cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
Kernel command line: elevator=cfq panic=20 root=/dev/sda1 console=ttyS0,115200 init=/linuxrc mem=64M poweroutage=yes
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
Using fractional divider baud 115200, clock 183333333 dlf 80
console [ttyS0] enabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 61860KB available (2712K code, 156K data, 104K init)
Calibrating delay loop... 183.09 BogoMIPS (lpj=915456)
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 64 bytes
NET: Registered protocol family 16
Number of DMA channels = 5, version = 4
Allocating 891 SRAM generic DMA descriptors
Chip Id: die-id 0x07a039f46680 read back 0xbeefcafe
PCI: bus0: Fast back to back transfers enabled
SCSI subsystem initialized
libata version 3.00 loaded.
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
Power button driver registered
Recovery button driver registered
SGI XFS with no debug enabled
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x44300000 (irq = 24) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 10240K size 1024 blocksize
loop: module loaded
Driver 'sd' needs updating - please use bus_type methods
ox810sata: OX810 sata core.
scsi0 : oxnassata
ata1: SATA max UDMA/133 irq 18
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: HPA detected: current 3907029168, native 18446744073321613488
ata1.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133
ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 0/32)
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access WDC WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 3907029168 512-byte hardware sectors (2000399 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 3907029168 512-byte hardware sectors (2000399 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2 sda3
sd 0:0:0:0: [sda] Attached SCSI disk
ox810sata: OX810 sata core.
scsi1 : oxnassata
ata2: SATA max UDMA/133 irq 18
ata2: SATA link down (SStatus 0 SControl 300)
mice: PS/2 mouse device common for all mice
Registered led device: oxnas-leds:bright
Registered led device: oxnas-leds:state
Registered led device: oxnas-leds:gauge
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda1, internal journal
ext3_orphan_cleanup: deleting unreferenced inode 225791
ext3_orphan_cleanup: deleting unreferenced inode 145123
EXT3-fs: sda1: 2 orphan inodes deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem).
Freeing init memory: 104K
Using fractional divider baud 115200, clock 183333333 dlf 80
Using fractional divider baud 115200, clock 183333333 dlf 80
Using fractional divider baud 115200, clock 183333333 dlf 80
Using fractional divider baud 115200, clock 183333333 dlf 80
Using fractional divider baud 115200, clock 183333333 dlf 80
Using fractional divider baud 115200, clock 183333333 dlf 80
Using fractional divider baud 115200, clock 183333333 dlf 80
Probing for Synopsis GMAC, unit 0
eth0: PHY is ICPlus 1001
eth0: GMAC ver = 51, vendor ver = 17 at 0xe8000000, IRQ 8
eth0: Found PHY at address 1, type 0x02430d90 -> 10/100/1000
eth0: Ethernet addr: 00:d0:b8:09:68:1e
thermAndFan: initializing - ox810
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
10 Dec 2004 USB 2.0 'Enhanced' Host Controller (EHCI) Driver@e7000000 Device ID register 42fa05
oxnas-ehci oxnas-ehci.0: OXNAS EHCI Host Controller
oxnas-ehci oxnas-ehci.0: new USB bus registered, assigned bus number 1
oxnas-ehci oxnas-ehci.0: irq 7, io mem 0x00000000
oxnas-ehci oxnas-ehci.0: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
usbcore: registered new interface driver libusual
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usblp
Adding 524280k swap on /usr/local/swap. Priority:-1 extents:11 across:1552488k
eth0: PHY is ICPlus 1001
CoPro: Programming start address as 0x9801e000 (basic adr = 0x9801e000)
Resetting GMAC
GMAC reset complete
eth0: PHY is ICPlus 1001
eth0: link down
eth0: link up, 100Mbps, full-duplex, using pause, lpa 0x45E1
XFS mounting filesystem sda2
Starting XFS recovery on filesystem: sda2 (logdev: internal)
Ending XFS recovery on filesystem: sda2 (logdev: internal)
Using fractional divider baud 115200, clock 183333333 dlf 80


Top
 Profile  
 
 Post subject: Re: MHNDHD frozen
PostPosted: Sat May 23, 2015 7:15 pm 
Offline

Joined: Sat Mar 28, 2015 3:13 pm
Posts: 5
an update for all who are confronted with this : I disabled the DLNA server in the GUI, and I also tweaked the startup scripts ( using the telnet login ) so that the twonkyserver is never started again. After that, the system runs perfectly as network disk.
I fear that the latest version of the dlna server is causing the system to stall ...


Top
 Profile  
 
 Post subject: Re: MHNDHD frozen
PostPosted: Wed Jun 03, 2015 5:38 pm 
Offline

Joined: Thu Mar 12, 2015 8:57 pm
Posts: 2
Hi, I tried to disable DNLA folders and disable the telnet service from and took two days no problem, I'll comerntar in a few days.


Top
 Profile  
 
 Post subject: Re: MHNDHD frozen
PostPosted: Fri Nov 06, 2015 9:31 am 
Offline

Joined: Sat Mar 15, 2014 9:30 am
Posts: 36
My personal history recovering Iomegas MHNDHD :

Just Yesterday i sucessfully restored two identical Iomega┬┤s "Home Media Network Hard Drive"
This tutorial is awesome, because i sucessfully restores with different hdd sizes, from 160GB to 2000Gb !
They are now working happy with 2TB Hard Drives !!!
Thanks to Mijzelf !

Image

Image

Image


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

All times are UTC


Who is online

Users browsing this forum: No registered users and 9 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