NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS NV - New power supply Power LED 3 fast flash
LED guide says: "OS image on NAND is corrupted, please perform NAND recovery through TFTP or USB" This is a 10 year old, very reliable, Infrant ReadyNas NV -- yes, that old. (-: It's hard to...
JennC- to clarify this -- I'm assuming this must be a ethernet CROSSOVER cable, correct? A straight ethernet cable wouldn't work... This should be easy to try. Thank you.
Just a note about Ethernet cable:
All ReadyNAS ever made(Including thoese based on ancient Sparc processor) support automatic MDI/MDI-X configuration feature(auto sensing), crossover cable is not needed when NAS is directly connected to PC.
Note for USB boot:
The usb command should be same as USB boot triggered by power button, USB recovery image should work. Please let's know what is displayed in serial console once you receive the serial cable (Again, please don't connect the red 5V pin, just leave it not connected) Thanks.
Serial Cable worked perfectly. Thanks for point me in the right direction. Any suggested direction to take on the following boot log? Thanks!
I booted normally (log below). I haven't started digging in on the specific/suspicious areas. Looks like a problem w/ one of the disks (or controller?):
DMA mode on chan 0
DMA mode on chan 1
@2DMA mode on chan 2
DMA mode on chan 3
Padre IDE controller, sata start:1
*** timeout ***=== Full boot log ===
Loading ...
Welcome to iboot 1.00a043
built 15:54 2008-10-01
Reason:
bid = 01
ECC OFF
Ldk
Ldi
zlist 0 802f115c
zone 802f0f14, name Normal
zlist 1 802f1170
zone 802f0ccc, name DMA
zlist 2 802f1184
zone 802f0f14, name Normal
Built 1 zonelists
Kernel command line: root=/dev/ram0 init=/linuxrc rw raid=noautodetect profile=2
kernel profiling enabled (shift: 2)
PID hash table entries: 4096 (order: 12, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 5, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 4, 262144 bytes)
Memory: 1010048k/1048576k available (2592k kernel code, 38016k reserved, 656k data, 96k init, 0k highmem)
init_mm.pgd bf0ff000
Mount-cache hash table entries: 2048
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 16384k freed
NET: Registered protocol family 16
usbcore: registered new driver usbfs
usbcore: registered new driver hub
NET: Registered protocol family 2
IP route cache hash table entries: 8192 (order: 1, 32768 bytes)
TCP established hash table entries: 32768 (order: 3, 131072 bytes)
TCP bind hash table entries: 16384 (order: 2, 65536 bytes)
TCP: Hash tables configured (established 32768 bind 16384)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(1070280003.210:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 4096 (order 0, 16384 bytes)
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
nbd: registered device at major 43
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
xor engine => SPARC.
device-mapper: 4.6.0-ioctl (2006-02-17) initialised: dm-devel@redhat.com
Serial: Padre driver $Revision: 1.1.1.1 $ 2 ports
ttyS0 at I/O 0x0 (irq = 7) is a padre uart
ttyS1 at I/O 0x0 (irq = 8) is a padre uart
oprofile: using timer interrupt.
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 5
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
md: Skipping autodetection of RAID arrays. (raid=noautodetect)
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel mepadre_i2c: module license 'Infrant Technologies, Inc.' taints kernel.
padre_i2c: no version for "udiv" found: kernel tainted.
TWSI Initialize
Padre NSPIO setup: 80353394... No argv, go to default.
raid5: xor select to PADRE_RXA.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
padre chip scan,token=1
Scan the padre NSP IO hardware.
Need memory for RTEngine 63680
PIO mode on chan 7
DMA mode on chan 0
DMA mode on chan 1
@2DMA mode on chan 2
DMA mode on chan 3
Padre IDE controller, sata start:1
*** timeout ***
PIO read data! Breaking out chn=0,count=126
(caller: f81258fc,801b8ea0,801b93ec,801bc588,801bc990,801bcb28,801bd37c,801be2c0).
No TLER on Hitachi HDS723015BLA642 @
hdc: Hitachi HDS723015BLA642 (s/n:MN1B20F316WDUD), ATA DISK drive (ATAEXT)
No TLER on Hitachi HDS723015BLA642 @
hde: Hitachi HDS723015BLA642 (s/n:MN1B20F316U6WD), ATA DISK drive (ATAEXT)
No TLER on ST31500341AS
hdg: ST31500341AS (s/n:9VS0ZYXK), ATA DISK drive (ATAEXT)
No TLER on ST31500341AS
hdi: ST31500341AS (s/n:9VS1RNY7), ATA DISK drive (ATAEXT)
ide1 at 0x200-0x207,0x208 on irq 32
ide2 at 0x280-0x287,0x288 on irq 33
ide3 at 0x300-0x307,0x308 on irq 34
ide4 at 0x380-0x387,0x388 on irq 35
Update NSPIO settings 80353394.
hdc: max request size: 512KiB
hdc: use capacity 2930277168 sectors (1500301 MB)
Drive support hpa, still should not change max addr.
hdc: 2930256688 sectors (1500291 MB) w/32767KiB Cache, CHS=65535/255/63
hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: 0xef
hdc: drive not ready for command ..
hdc: cache flushes supported
hdc:Failing rq 81e9cdb0 on hdc
Buffer I/O error on device hdc, logical block 0 (insmod)
Failing rq 81e9cdb0 on hdc
Buffer I/O error on device hdc, logical block 1 (insmod)
Failing rq 81e9cdb0 on hdc
Buffer I/O error on device hdc, logical block 0 (insmod)
Failing rq 81e9cdb0 on hdc
Buffer I/O error on device hdc, logical block 1 (insmod)
Failing rq 81e9cdb0 on hdc
Buffer I/O error on device hdc, logical block 0 (insmod)
Failing rq 81e9cdb0 on hdc
Buffer I/O error on device hdc, logical block 1 (insmod)
unable to read partition table
Failing rq 80ac37f8 on hdc
hde: max request size: 512KiB
hde: use capacity 2930277168 sectors (1500301 MB)
Drive support hpa, still should not change max addr.
hde: 2930256688 sectors (1500291 MB) w/32767KiB Cache, CHS=65535/255/63
hde: cache flushes supported
hde:chn=1, statu/LP_S=0x(d0/d050)29, 16
unknown partition table
hdg: max request size: 512KiB
hdg: use capacity 2930277168 sectors (1500301 MB)
Drive support hpa, still should not change max addr.
hdg: 2930256688 sectors (1500291 MB), CHS=65535/255/63
hdg: cache flushes supported
hdg: hdg1 hdg2 hdg3 < hdg5 hdg6 >
hdi: max request size: 512KiB
hdi: use capacity 2930277168 sectors (1500301 MB)
Drive support hpa, still should not change max addr.
hdi: 2930256688 sectors (1500291 MB), CHS=65535/255/63
hdi: cache flushes supported
hdi: hdi1 hdi2 hdi3 < hdi5 hdi6 >
Link to padre IO.
RAID disks check:
ALL = 33/34/56/0/0/0/0/0, 3
IDE = 34/56/0/0/0/0/0/0, 2
MD = 0/0/0/0/0/0/0/0, 0
RAID rule check result: 0
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
Reading/Write : hdc not ready, waiting...
Reading/Write : hdc not ready, waiting...
Reading/Write : hdc not ready, waiting...
Reading/Write : hdc not ready, waiting...
Reading/Write : hdc not ready, waiting...
*** timeout ***
PIO read data! Breaking out chn=0,count=256
(caller: f81258fc,801b8ea0,801b93ec,f8108d94,f81090c0,f81095f8,f8125680,801fb3cc).
Disk mark = 0/0x0
Disk protected mark = 1
x_raid_start: 1,current:0
BDL_count= 0, fw=SN04, model=
BDL_count= 1, fw=SN04, model=
GOT MEMORY FOR DJ: 128*4k
Drive hdc SB at 2930263632(-sbs) CURRENT
Reading/Write : hdc not ready, waiting...
Reading/Write : hdc not ready, waiting...
Reading/Write : hdc not ready, waiting...
Reading/Write : hdc not ready, waiting...
Reading/Write : hdc not ready, waiting...
*** timeout ***
PIO read data! Breaking out chn=0,count=6144
(caller: f81258fc,801b8ea0,801b93ec,f8108d94,f81090c0,f810924c,f81094d4,f810dee4).
Drive hde SB at 2930263632(-sbs) CURRENT
Drive hdg SB at 2930263632(-sbs) CURRENT
Drive hdi SB at 2930263632(-sbs) CURRENT
x_raid_start: 1,result:0
Find PHY: 0
Lookup PHY ID: 0x000f, 0x01
P0 GPIO initialization... BOARDID=1
Boot type/reason: normal/0/0
Adjusting fan pwm.....................
Found LM75 at 0x48
NAND device: Manufacture ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB 3,3V 8-bit)
Samsung NAND flash rev C
size of table 4096
table is there 0x8
total bad block 0
Total bad block number 0
retlen = 0x0200
VPD checksum = 0x3533
ECC is ON
Creating 2 MTD partitions on "NAND 64MiB 3,3V 8-bit":
0x00000000-0x00100000 : "P0 flash partition 1"
0x00100000-0x04000000 : "P0 flash partition 2"
NEON flash: probing 8-bit flash bus
NEON flash: Found no Atmel device at location zero
This board is not supported.
You can use parm_extport=X module parm.
I2C device 1f doesn't exist
I2C device 1b doesn't exist
LCD device not found
X_RAID_START
Failing rq 809bba70 on hdc
startstop XRAID command = start, flash_cache=0
X_RAID clean shutdown indicator: 0x4.
Reading/Write : hdc not ready, waiting...
Reading/Write : hdc not ready, waiting...
Reading/Write : hdc not ready, waiting...
Reading/Write : hdc not ready, waiting...
Reading/Write : hdc not ready, waiting...
*** timeout ***
PIO write data!
*** timeout ***
PIO write data!Hi bmehling,
Please try using the steps found on the link on how to send the logs to moderators.
How do I send all logs to ReadyNAS Community moderators?
Regards,
Thanks FramerV -- I'm assuming you're requesting these logs be sent to moderators? Unfortunately I am not able to access RAIDiator(4). My logs are being pulled via a serial connection.
For some unknown reason, the USB/serial device failed and I was unable to continue debugging. I've now got it running again. I went through the entire boot sequence monitoring via the serial connection. The sequence is the same as what I've pasted here. I left the unit running for a while. Every few minutes the following message is repeated:
*** timeout *** PIO write data!
JennC- I have a known working ethernet cable firmly plugged into both a computer and the ReadyNAS NV. The link lights are active. RAIDar never detects the ReadyNAS. I've left the unit on for some time (30+ minutes) and repeatly tried to 'rescan' with no results.
c3po- Would booting from NAND or USB vs. the image on disk make a difference? It doesn't seem to have issues w/ the OS boot.
Any suggestions on the log details? This looks the most troubling to me:
Need memory for RTEngine 63680 PIO mode on chan 7 DMA mode on chan 0 DMA mode on chan 1 @2DMA mode on chan 2 // <--- what is this stray "@2" between chan 1 and 2? DMA mode on chan 3 Padre IDE controller, sata start:1 *** timeout *** // <--- Is this a controller issue or simply reporting the drive didn't come online? PIO read data! Breaking out chn=0,count=126 (caller: f81258fc,801b8ea0,801b93ec,801bc588,801bc990,801bcb28,801bd37c,801be2c0).
Thanks for any advice the community or staff can provide.
- Ben
Hi bmehling,
Based on the description of the issue that you have provided, I may need to check this with others who can probably assist you and get back to you as soon as possible.
Thanks for your cooperation!
Regards,
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
