Hello Everyone,
Sorry to intrude here with a not (yet?) hacked device, from a not (yet?) linuxhacker (:)), but "you are my only hope".
So I got a NSA310 from a friend, who had it run for several years, when all of a sudden it was unavailable. Upon restarting, after some blinking for 30secs, there was only an eternal beep-beep-beep-.. from the buzzer. This is the situation with the original HDD, a blank new HDD, or no HDD.
He gave it to me, to see if there is some chance of revival, but I am noob in these embedded linux stuff. Sadly most resources (official firmware, usb force update script) got pulled offline after the EOL of the device.
On a whim I bought a CP2012, manage to connect to the device, and seen some messages during boot, see attached.
Some googling upon key words brought me to some threads on this forum - but I am too inexperienced to understand them.
Could you help in answering the following basic questions?
1) Are the bad eraseblock messages blocks, that have been predetermined as bad in factory, or does this means that the NAND is getting worse?
Bad eraseblock 611 at 0x000004c60000
Bad eraseblock 621 at 0x000004da0000
2) what is wrong? :) I mean i see
ls: /zyxel/mnt/nand/sysdisk.img.gz: No such file or directory
NAND Flash Corrupt...
the sys-root image /dev/mtdblock6 is currupt !!
Dual images are currupt !!!
From quickly reading some topics on this forum, i see these also could be substituted from a flash drive using debian images - but is there a way to get the original content back?
3) I found this https://github.com/vch42/NSA3xx-usb-recovery-stick, but this does nothing, i think because
sda
checking sda
Trying to mount /dev/sda1
FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
cmd = cat /etc/Zy_Private /mnt/parnerkey/nsa310_fw/usb_key_func.sh | md5sum -c /mnt/parnerkey/nsa310_fw/Upgrade_C0
md5sum: WARNING: 1 of 1 computed checksum did NOT match
md5 check error
Has someone had any luck with this?
4) If the NAND is toast, and transitioning to a debian would be a solution, would this be a usable guide?
https://github.com/peeter123/NSA310-320-debian
The Known Bugs section seems scary:
Samba crashes whole system
Ethernet leds don't work @ 1gbit
All mtd blocks read as bad. The chip is somehow not supported by kernel.
I am thankful for any advice,
Peter
Sorry to intrude here with a not (yet?) hacked device, from a not (yet?) linuxhacker (:)), but "you are my only hope".
So I got a NSA310 from a friend, who had it run for several years, when all of a sudden it was unavailable. Upon restarting, after some blinking for 30secs, there was only an eternal beep-beep-beep-.. from the buzzer. This is the situation with the original HDD, a blank new HDD, or no HDD.
He gave it to me, to see if there is some chance of revival, but I am noob in these embedded linux stuff. Sadly most resources (official firmware, usb force update script) got pulled offline after the EOL of the device.
On a whim I bought a CP2012, manage to connect to the device, and seen some messages during boot, see attached.
Some googling upon key words brought me to some threads on this forum - but I am too inexperienced to understand them.
Could you help in answering the following basic questions?
1) Are the bad eraseblock messages blocks, that have been predetermined as bad in factory, or does this means that the NAND is getting worse?
Bad eraseblock 611 at 0x000004c60000
Bad eraseblock 621 at 0x000004da0000
2) what is wrong? :) I mean i see
ls: /zyxel/mnt/nand/sysdisk.img.gz: No such file or directory
NAND Flash Corrupt...
the sys-root image /dev/mtdblock6 is currupt !!
Dual images are currupt !!!
From quickly reading some topics on this forum, i see these also could be substituted from a flash drive using debian images - but is there a way to get the original content back?
3) I found this https://github.com/vch42/NSA3xx-usb-recovery-stick, but this does nothing, i think because
sda
checking sda
Trying to mount /dev/sda1
FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
cmd = cat /etc/Zy_Private /mnt/parnerkey/nsa310_fw/usb_key_func.sh | md5sum -c /mnt/parnerkey/nsa310_fw/Upgrade_C0
md5sum: WARNING: 1 of 1 computed checksum did NOT match
md5 check error
Has someone had any luck with this?
4) If the NAND is toast, and transitioning to a debian would be a solution, would this be a usable guide?
https://github.com/peeter123/NSA310-320-debian
The Known Bugs section seems scary:
Samba crashes whole system
Ethernet leds don't work @ 1gbit
All mtd blocks read as bad. The chip is somehow not supported by kernel.
I am thankful for any advice,
Peter