× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

My NAS Duo is stuck, slow or dead!

kema
Aspirant

My NAS Duo is stuck, slow or dead!

Hi again. Suddenly my NAS is running very, very slow. Just to open it frontview takes 5 min, and maybe a hold 15 min to navigate to where I can shut it down. To copy 4gb to my pc would take 12 hours, and to navigate around in my shares takes forever, I think you get the point! While writing this I had 5 min where everything was at the normal speed. I have done a firmware reinstall, but didn’t help. I got 65% used on 1tb hard drive. I have 2 installed and they are X-RAID (Expandable RAID), 2 disks (redundant)
I have tried to boot up only on disc at the time, to see if one of my hard drives are failing. But getting the same result with both of em. I have upgraded to the newest firmware, cant get in to se what it is called, but is the one frontwiev get online, maybe 4,1,7. I have done a static ip for my NAS. If I do a file system check it will take all not night and just leave me with an blank raidar. It is now stucked at 100% with only my second hard drive and cant browse or go to frontview, so I cant get a test with IOmeter but was transferring with 600b/sec in windows (yeah I had read the post so please don’t :slap: me) I did get out an log file, only took me 2 hours, but don’t know what to look for!
I have also tried to connect the network cable from the NAS directly to my pc. It made no difference!
NIC on my PC? Meaning?
Hope that was enough to begin with.
what could curse this, and what can I do. By the way it makes no difference if use a line or the wireless network! I have a ReadyNAS duo.
Message 1 of 6
kema
Aspirant

Re: My NAS Duo is stuck, slow or dead!

from volume tab in frontview: Resync 3% complete, Time to finish 81 hr 56 min, Speed 3122 KB/sec.
Is it normal to take 81 hours to resync 600 gb data. Gonna let it finish, and then do a volume and file scan on the next rebot. maybe thats gonna help!
Message 2 of 6
kema
Aspirant

Re: My NAS Duo is stuck, slow or dead!

I just took a little bite of my system log. maybe it means something for someone.


Aug 10 18:44:57 Basserne kernel: padre_power_down_task
Aug 10 21:38:19 Basserne syslogd 1.4.1#10: restart.
Aug 10 21:38:19 Basserne kernel: klogd 1.4.1#10, log source = /proc/kmsg started.
Aug 10 21:38:19 Basserne kernel: Linux version 2.6.17.14ReadyNAS (root@calzone) (gcc version 3.3.5 (Infrant 3.3.5-1)) #1 Wed Sep 22 04:42:09 PDT 2010
Aug 10 21:38:19 Basserne kernel: You system is PZERO.
Aug 10 21:38:19 Basserne kernel: ASIC=IT3107
Aug 10 21:38:19 Basserne kernel: On node 0 totalpages: 16384
Aug 10 21:38:19 Basserne kernel: Normal zone: 15360 pages, LIFO batch:3
Aug 10 21:38:19 Basserne kernel: DMA zone: 1024 pages, LIFO batch:0
Aug 10 21:38:19 Basserne kernel: zlist 0 802ef15c
Aug 10 21:38:19 Basserne kernel: zone 802eef14, name Normal
Aug 10 21:38:19 Basserne kernel: zlist 1 802ef170
Aug 10 21:38:19 Basserne kernel: zone 802eeccc, name DMA
Aug 10 21:38:19 Basserne kernel: zlist 2 802ef184
Aug 10 21:38:19 Basserne kernel: zone 802eef14, name Normal
Aug 10 21:38:19 Basserne kernel: Built 1 zonelists
Aug 10 21:38:19 Basserne kernel: Kernel command line: root=/dev/ram0 init=/linuxrc rw raid=noautodetect profile=2
Aug 10 21:38:19 Basserne kernel: kernel profiling enabled (shift: 2)
Aug 10 21:38:19 Basserne kernel: PID hash table entries: 2048 (order: 11, 8192 bytes)
Aug 10 21:38:19 Basserne kernel: Dentry cache hash table entries: 32768 (order: 3, 131072 bytes)
Aug 10 21:38:19 Basserne kernel: Inode-cache hash table entries: 16384 (order: 2, 65536 bytes)
Aug 10 21:38:19 Basserne kernel: Memory: 226176k/262144k available (2592k kernel code, 35872k reserved, 656k data, 96k init, 0k highmem)
Aug 10 21:38:19 Basserne kernel: init_mm.pgd 8f0ff000
Aug 10 21:38:19 Basserne kernel: Calibrating delay loop... 186.36 BogoMIPS (lpj=931840)
Aug 10 21:38:19 Basserne kernel: Mount-cache hash table entries: 2048
Aug 10 21:38:19 Basserne kernel: checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Aug 10 21:38:19 Basserne kernel: Freeing initrd memory: 16384k freed
Aug 10 21:38:19 Basserne kernel: NET: Registered protocol family 16
Aug 10 21:38:19 Basserne kernel: usbcore: registered new driver usbfs
Aug 10 21:38:19 Basserne kernel: usbcore: registered new driver hub
Aug 10 21:38:19 Basserne kernel: NET: Registered protocol family 2
Aug 10 21:38:19 Basserne kernel: IP route cache hash table entries: 2048 (order: -1, 8192 bytes)
Aug 10 21:38:19 Basserne kernel: TCP established hash table entries: 8192 (order: 1, 32768 bytes)
Aug 10 21:38:19 Basserne kernel: TCP bind hash table entries: 4096 (order: 0, 16384 bytes)
Aug 10 21:38:19 Basserne kernel: TCP: Hash tables configured (established 8192 bind 4096)
Aug 10 21:38:19 Basserne kernel: TCP reno registered
Aug 10 21:38:19 Basserne kernel: audit: initializing netlink socket (disabled)
Aug 10 21:38:19 Basserne kernel: audit(1070280003.190:1): initialized
Aug 10 21:38:19 Basserne kernel: VFS: Disk quotas dquot_6.5.1
Aug 10 21:38:19 Basserne kernel: Dquot-cache hash table entries: 4096 (order 0, 16384 bytes)
Aug 10 21:38:19 Basserne kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Aug 10 21:38:19 Basserne kernel: Initializing Cryptographic API
Aug 10 21:38:19 Basserne kernel: io scheduler noop registered
Aug 10 21:38:19 Basserne kernel: io scheduler anticipatory registered
Aug 10 21:38:19 Basserne kernel: io scheduler deadline registered
Aug 10 21:38:19 Basserne kernel: io scheduler cfq registered (default)
Aug 10 21:38:19 Basserne kernel: RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Aug 10 21:38:19 Basserne kernel: loop: loaded (max 8 devices)
Aug 10 21:38:19 Basserne kernel: nbd: registered device at major 43
Aug 10 21:38:19 Basserne kernel: tun: Universal TUN/TAP device driver, 1.6
Aug 10 21:38:19 Basserne kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Aug 10 21:38:19 Basserne kernel: md: raid0 personality registered for level 0
Aug 10 21:38:19 Basserne kernel: md: raid1 personality registered for level 1
Aug 10 21:38:19 Basserne kernel: md: raid5 personality registered for level 5
Aug 10 21:38:19 Basserne kernel: md: raid4 personality registered for level 4
Aug 10 21:38:19 Basserne kernel: xor engine => SPARC.
Aug 10 21:38:19 Basserne kernel: device-mapper: 4.6.0-ioctl (2006-02-17) initialised: dm-devel@redhat.com
Aug 10 21:38:19 Basserne kernel: Serial: Padre driver $Revision: 1.1.1.1 $ 2 ports
Aug 10 21:38:19 Basserne kernel: ttyS0 at I/O 0x0 (irq = 7) is a padre uart
Aug 10 21:38:19 Basserne kernel: ttyS1 at I/O 0x0 (irq = 😎 is a padre uart
Aug 10 21:38:19 Basserne kernel: oprofile: using timer interrupt.
Aug 10 21:38:19 Basserne kernel: TCP bic registered
Aug 10 21:38:19 Basserne kernel: NET: Registered protocol family 1
Aug 10 21:38:19 Basserne kernel: NET: Registered protocol family 17
Aug 10 21:38:19 Basserne kernel: NET: Registered protocol family 5
Aug 10 21:38:19 Basserne kernel: 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
Aug 10 21:38:19 Basserne kernel: All bugs added by David S. Miller <davem@redhat.com>
Aug 10 21:38:19 Basserne kernel: md: Skipping autodetection of RAID arrays. (raid=noautodetect)
Aug 10 21:38:19 Basserne kernel: RAMDISK: Compressed image found at block 0
Aug 10 21:38:19 Basserne kernel: VFS: Mounted root (ext2 filesystem).
Aug 10 21:38:19 Basserne kernel: Freeing unused kernel memory: 96k freed
Aug 10 21:38:19 Basserne kernel: padre_i2c: module license 'Infrant Technologies, Inc.' taints kernel.
Aug 10 21:38:19 Basserne kernel: padre_i2c: no version for "udiv" found: kernel tainted.
Aug 10 21:38:19 Basserne kernel: TWSI Initialize
Aug 10 21:38:19 Basserne kernel: Padre NSPIO setup: 80353394... No argv, go to default.
Aug 10 21:38:19 Basserne kernel: raid5: xor select to PADRE_RXA.
Aug 10 21:38:19 Basserne kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
Aug 10 21:38:19 Basserne kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Aug 10 21:38:19 Basserne kernel: padre chip scan,token=1
Aug 10 21:38:19 Basserne kernel: Scan the padre NSP IO hardware.
Aug 10 21:38:19 Basserne kernel: Need memory for RTEngine 63680
Aug 10 21:38:19 Basserne kernel: PIO mode on chan 7
Aug 10 21:38:19 Basserne kernel: DMA mode on chan 0
Aug 10 21:38:19 Basserne kernel: DMA mode on chan 1
Aug 10 21:38:19 Basserne kernel: Padre IDE controller, sata start:1
Aug 10 21:38:19 Basserne kernel: WD drive does not support TLER, 0, 3730
Aug 10 21:38:19 Basserne kernel: hdc: WDC WD1002FAEX-00Z3A0 (s/n:WD-WCATR3984285), ATA DISK drive (ATAEXT)
Aug 10 21:38:19 Basserne kernel: No TLER on Hitachi HDT721010SLA360 ^P\200@
Aug 10 21:38:19 Basserne kernel: hde: Hitachi HDT721010SLA360 (s/n:STF607MH1J5VGW), ATA DISK drive (ATAEXT)
Aug 10 21:38:19 Basserne kernel: ide1 at 0x200-0x207,0x208 on irq 32
Aug 10 21:38:19 Basserne kernel: ide2 at 0x280-0x287,0x288 on irq 33
Aug 10 21:38:19 Basserne kernel: Update NSPIO settings 80353394.
Aug 10 21:38:19 Basserne kernel: hdc: max request size: 512KiB
Aug 10 21:38:19 Basserne kernel: hdc: use capacity 1953525168 sectors (1000204 MB)
Aug 10 21:38:19 Basserne kernel: Drive support hpa, still should not change max addr.
Aug 10 21:38:19 Basserne kernel: hdc: 1953108616 sectors (999991 MB), CHS=65535/255/63
Aug 10 21:38:19 Basserne kernel: hdc: cache flushes supported
Aug 10 21:38:19 Basserne kernel: hdc:chn=0, statu/LP_S=0x(d0/d050)29, 8
Aug 10 21:38:19 Basserne kernel: hdc1 hdc2 hdc3 < hdc5 >
Aug 10 21:38:19 Basserne kernel: hde: max request size: 512KiB
Aug 10 21:38:19 Basserne kernel: hde: use capacity 1953525168 sectors (1000204 MB)
Aug 10 21:38:19 Basserne kernel: Drive support hpa, still should not change max addr.
Aug 10 21:38:19 Basserne kernel: hde: 1953108616 sectors (999991 MB) w/15001KiB Cache, CHS=65535/255/63
Aug 10 21:38:19 Basserne kernel: hde: cache flushes supported
Aug 10 21:38:19 Basserne kernel: hde:chn=1, statu/LP_S=0x(d0/d050)29, 8
Aug 10 21:38:19 Basserne kernel: unknown partition table
Aug 10 21:38:19 Basserne kernel: Link to padre IO.
Aug 10 21:38:19 Basserne kernel:
Aug 10 21:38:19 Basserne kernel: RAID disks check:
Aug 10 21:38:19 Basserne kernel: ALL = 22/33/0/0/0/0/0/0, 2
Aug 10 21:38:19 Basserne kernel: IDE = 22/0/0/0/0/0/0/0, 1
Aug 10 21:38:19 Basserne kernel: MD = 0/0/0/0/0/0/0/0, 0
Aug 10 21:38:19 Basserne kernel: RAID rule check result: 0
Aug 10 21:38:19 Basserne kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
Aug 10 21:38:19 Basserne kernel: md: bitmap version 4.39
Aug 10 21:38:19 Basserne kernel: Disk protected mark = 1
Aug 10 21:38:19 Basserne kernel: x_raid_start: 1,current:0
Aug 10 21:38:19 Basserne kernel: BDL_count= 0, fw=SN04, model=
Aug 10 21:38:19 Basserne kernel: BDL_count= 1, fw=SN04, model=
Aug 10 21:38:19 Basserne kernel: GOT MEMORY FOR DJ: 128*4k
Aug 10 21:38:19 Basserne kernel: Drive hdc SB at 1953511632(-sbs) CURRENT
Aug 10 21:38:19 Basserne kernel: Drive hde SB at 1953511632(-sbs) CURRENT
Aug 10 21:38:19 Basserne kernel: x_raid_start: 1,result:0
Aug 10 21:38:19 Basserne kernel: Find PHY: 0
Aug 10 21:38:19 Basserne kernel: Lookup PHY ID: 0x0141, 0x0c
Aug 10 21:38:19 Basserne kernel: P0 GPIO initialization... BOARDID=1
Aug 10 21:38:19 Basserne kernel: Boot type/reason: normal/0/21028C7100789
Aug 10 21:38:19 Basserne kernel: Adjusting fan pwm................
Aug 10 21:38:19 Basserne kernel: I2C device 48 doesn't exist
Aug 10 21:38:19 Basserne kernel: I2C device 49 doesn't exist
Aug 10 21:38:19 Basserne kernel: I2C device 4a doesn't exist
Aug 10 21:38:19 Basserne kernel: I2C device 4b doesn't exist
Aug 10 21:38:19 Basserne kernel: The LM75 can not be found
Aug 10 21:38:19 Basserne kernel: NAND device: Manufacture ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB 3,3V 8-bit)
Aug 10 21:38:19 Basserne kernel: Samsung NAND flash rev C
Aug 10 21:38:19 Basserne kernel: size of table 4096
Aug 10 21:38:19 Basserne kernel: table is there 0x8
Aug 10 21:38:19 Basserne kernel: bad block 2310 replacing by 4095
Aug 10 21:38:19 Basserne kernel: bad block 2314 replacing by 4094
Aug 10 21:38:19 Basserne kernel: bad block 2318 replacing by 4093
Aug 10 21:38:19 Basserne kernel: total bad block 3
Aug 10 21:38:19 Basserne kernel: bad 2310 = 4095 bad 2314 = 4094 bad 2318 = 4093 bad 4093 = -1 bad 4094 = -1 bad 4095 = -1 Total bad block number 3
Aug 10 21:38:19 Basserne kernel: retlen = 0x0200
Aug 10 21:38:19 Basserne kernel: VPD checksum = 0xcb1d
Aug 10 21:38:19 Basserne kernel: ECC is ON
Aug 10 21:38:19 Basserne kernel: Creating 2 MTD partitions on "NAND 64MiB 3,3V 8-bit":
Aug 10 21:38:19 Basserne kernel: 0x00000000-0x00100000 : "P0 flash partition 1"
Aug 10 21:38:19 Basserne kernel: 0x00100000-0x03ff4000 : "P0 flash partition 2"
Aug 10 21:38:19 Basserne kernel: NEON flash: probing 8-bit flash bus
Aug 10 21:38:19 Basserne kernel: CFI: Found no NEON flash device at location zero
Aug 10 21:38:19 Basserne kernel: NEON flash: unknown flash device, mfr id 0x1, dev id 0x0
Aug 10 21:38:19 Basserne kernel: NEON flash: Found no Atmel device at location zero
Aug 10 21:38:19 Basserne kernel: This board is not supported.
Aug 10 21:38:19 Basserne kernel: You can use parm_extport=X module parm.
Aug 10 21:38:19 Basserne kernel: I2C device 1f doesn't exist
Aug 10 21:38:19 Basserne kernel: I2C device 1b doesn't exist
Aug 10 21:38:19 Basserne kernel: LCD device not found
Aug 10 21:38:19 Basserne kernel: X_RAID_START
Aug 10 21:38:19 Basserne kernel: startstop XRAID command = start, flash_cache=0
Aug 10 21:38:19 Basserne kernel: X_RAID clean shutdown indicator: 0x3.
Aug 10 21:38:19 Basserne kernel: 0 2 2 0 0 0 0 0
Aug 10 21:38:20 Basserne kernel: 0 1 0 0
Aug 10 21:38:20 Basserne kernel: 1 0 0 0
Aug 10 21:38:20 Basserne kernel: 0 0 0 0
Aug 10 21:38:20 Basserne kernel: 0 0 0 0
Aug 10 21:38:20 Basserne kernel: Update time for sb 1 = 4dfd0357.
Aug 10 21:38:20 Basserne kernel: Update time for sb 2 = 4dfd0357.
Aug 10 21:38:20 Basserne kernel: Update time for sb 3 = 0.
Aug 10 21:38:20 Basserne kernel: Update time for sb 4 = 0.
Aug 10 21:38:20 Basserne kernel: recent_ID = 1, select_ID=1, most_ID=2 right_mac=2
Aug 10 21:38:20 Basserne kernel: Selected sb 1, ctime=4dfd0357, id=3fb67861.
Aug 10 21:38:20 Basserne kernel: Use this image: 1
Aug 10 21:38:20 Basserne kernel:
Aug 10 21:38:20 Basserne kernel: VERSION/ID : SB=(V:0.1.0) ID=<3fb67861.00000000.00000000.00000000> CT:4dfd0357
Aug 10 21:38:20 Basserne kernel: RAID_INFO : DISKS(TOTAL:2 RAID:2 PARITY:1 ONL:2 WRK:2 FAILED:0 SPARE:0 BASE:0)
Aug 10 21:38:20 Basserne kernel: SZ:1953108616 UT:00000000 STATE:0 LUNS:2 EXTCMD:1 LSZ:1953108614
Aug 10 21:38:20 Basserne kernel: LOGICAL_DRIVE : 0: B:0000000002 E:0004096000 R:1 O:1 I:1:000000000 DM:3
Aug 10 21:38:20 Basserne kernel: LOGICAL_DRIVE : 1: B:0004096002 E:1949012614 R:1 O:1 I:1:1578438658 DM:3
Aug 10 21:38:20 Basserne kernel: PHYSICAL_DRIVE: 0: DISK<N:0/1,hdc(22,0),ID:0,PT:1,SZ:1953108616,ST: B:online>
Aug 10 21:38:20 Basserne kernel: PHYSICAL_DRIVE: 1: DISK<N:1/2,hde(33,0),ID:1,PT:1,SZ:1953108616,ST:P :online>
Aug 10 21:38:20 Basserne kernel: CURRENT_DRIVE : DISK<N:0/1,XXX(22,0),ID:0,PT:1,SZ:1953108616,ST: B:online>
Aug 10 21:38:20 Basserne kernel: Need to do drives searching.
Aug 10 21:38:20 Basserne kernel: Find p d at 1, chn 1
Aug 10 21:38:20 Basserne kernel: Total=2; raid=2; ready=0; work=2; failed=0
Aug 10 21:38:20 Basserne kernel: Check degraded mode, start_pos=1
Aug 10 21:38:20 Basserne kernel: No drive missing, X_RAID run in opt mode.
Aug 10 21:38:20 Basserne kernel: Change X_RAID running mode from 0 to 1
Aug 10 21:38:20 Basserne kernel: Update backup SB.
Aug 10 21:38:20 Basserne kernel: X_RAID: recovery thread got woken up ...
Aug 10 21:38:20 Basserne kernel: New = 1, source drives = 3, current/active=2/2
Aug 10 21:38:20 Basserne kernel: hdc:chn=0, statu/LP_S=0x(d0/d050)29, 8
Aug 10 21:38:20 Basserne kernel: hdc1 hdc2 hdc3 < hdc5 >
Aug 10 21:38:20 Basserne kernel: hde: unknown partition table
Aug 10 21:38:20 Basserne kernel: chn=0, statu/LP_S=0x(d0/d050)29, 32
Aug 10 21:38:20 Basserne kernel: kjournald starting. Commit interval 5 seconds
Aug 10 21:38:20 Basserne kernel: EXT3 FS on hdc1, internal journal
Aug 10 21:38:20 Basserne kernel: EXT3-fs: recovery complete.
Aug 10 21:38:20 Basserne kernel: EXT3-fs: mounted filesystem with ordered data mode.
Aug 10 21:38:20 Basserne kernel: linked, 1000mbps mode
Aug 10 21:38:20 Basserne kernel: hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Aug 10 21:38:20 Basserne kernel: hdc: drive_cmd: error=0x04 { DriveStatusError }
Aug 10 21:38:20 Basserne kernel: ide: failed opcode was: 0xef
Message 3 of 6
InTheShires
Tutor

Re: My NAS Duo is stuck, slow or dead!

If it's running a resync, performance is extremely slow, and usability severely dampened.

Definitely, if possible, leave it well alone while it's running the resync. At the start, the % estimate is quite high, but it did come down to a more sensible estimate after a while, and my 2x 2tb, drives took around 8hrs if I remember correctly.

Once the sync is done, see what performance is like after that. If it's still flaky, then you can start fretting. 😉

EDIT Maybe you have hard drive issues?
Message 4 of 6
kema
Aspirant

Re: My NAS Duo is stuck, slow or dead!

I don’t think that it is because of resyncing it is slow. As I told my NAS started out to be slow with no warning, just one morning it decided to go 10 times less my normal speed. And both my hard drives was still slow with only 1 hard drive in place
Well after 40 hours and 30% done of the resync, it decided to get stuck. Raidar and frontview couldn’t find it anymore. Waited until the next day, but still the same. Try to hold down the power button to restart it, tried it 4 times for 10 min, and gave up. Dooku described in another post “ the only way out now is to pull the plug” so I did. Now it’s doing a file system check. When its done doing that, expect 12 hours or so I have this plan:
Taking the hard drive, that I know contains all my files, out of the NAS. Get the other hard drive in slot 1 and do a total factory default. Then I will check if I have a NAS with a good performance again. If that is the case, I will shut down the NAS put the clean hard drive in slot 2, and the one containing my files in slot 1, then start my NAS up. Then it will sync my files to the clean drive right? After that I will take out the, before clean disc, and check if it is containing all my files. Then I will do a factory default with only the disc in slot 1. Then the file are wiped out on that drive to, and then check the speed on that drive to. I will shut down the NAS changes the disc so that my files are in slot 1, power it up and make it resync. If both my drives are ok, then I would have an fast NAS again right?
Hope it makes sense, hard to make sense all the way from Denmark 😉
Is that a good solution, or any other ideas?
Message 5 of 6
kema
Aspirant

Re: My NAS Duo is stuck, slow or dead!

Ok. I have now moved the second disc so it isn’t syncing anymore. Did a rebot and a file system check found some errors and corrected them. Its still very slow. I’m now trying to copy my files to my pc, so I can start all over again. But with a transfer speed at 700KB/sec I will never get my 600gb transferred. I could really need some help. Please!
Message 6 of 6
Top Contributors
Discussion stats
  • 5 replies
  • 1396 views
  • 0 kudos
  • 2 in conversation
Announcements