Hello,
I have an NSA310 which has not had alot of use due to the lack support for SMB1 problem.
It has uboot 1.1.4 and Zyxel 4.7 firmware.
Was pleased to discover options available here, but after activating the telnet backdoor and checking the NAND chip as recommended, I see there are bad erase blocks:
I read in one of the posts that there is a "workaround" for this situation, though I couldn't see exactly what that was. Perhaps secondary booting the system off a usb flash drive from the stock uboot
That brings me to the second stumbling block, having trouble accessing anything on a flash drive inserted into the front panel socket. Generally getting status as follows in the boot log.... (eg from attaching a hub with 2 different fat32 4gb flash drives plugged in attempting to mount to sdb1 and sdc1 during boot)... Subsequently I an LS of the /mnt/sdb1 and /mnt/sdc1 paths just shows an empty directory (though there are files on the disks).
I have tried a few drives with and without an intermediate hub.
I should say I am somewhat rusty on linux, though used to do a fair amount of embedded development 20 years ago.
Any advice on either of these issues would be appreciated.
I have an NSA310 which has not had alot of use due to the lack support for SMB1 problem.
It has uboot 1.1.4 and Zyxel 4.7 firmware.
Was pleased to discover options available here, but after activating the telnet backdoor and checking the NAND chip as recommended, I see there are bad erase blocks:
/ # dmesg | grep -i 'bad' Scanning device for bad blocks Bad eraseblock 2 at 0x000000040000 Bad eraseblock 3 at 0x000000060000 Bad eraseblock 294 at 0x0000024c0000 Bad eraseblock 968 at 0x000007900000
I read in one of the posts that there is a "workaround" for this situation, though I couldn't see exactly what that was. Perhaps secondary booting the system off a usb flash drive from the stock uboot
That brings me to the second stumbling block, having trouble accessing anything on a flash drive inserted into the front panel socket. Generally getting status as follows in the boot log.... (eg from attaching a hub with 2 different fat32 4gb flash drives plugged in attempting to mount to sdb1 and sdc1 during boot)... Subsequently I an LS of the /mnt/sdb1 and /mnt/sdc1 paths just shows an empty directory (though there are files on the disks).
scsi 2:0:0:0: Direct-Access General UDISK 5.00 PQ: 0 ANSI: 2 sd 2:0:0:0: [sdb] 7866368 512-byte logical blocks: (4.02 GB/3.75 GiB) sd 2:0:0:0: [sdb] Write Protect is off sd 2:0:0:0: [sdb] Assuming drive cache: write through sd 2:0:0:0: [sdb] Assuming drive cache: write through sdb: sdb1 sd 2:0:0:0: Attached scsi generic sg1 type 0 sd 2:0:0:0: [sdb] Assuming drive cache: write through sd 2:0:0:0: [sdb] Attached SCSI removable disk scsi 3:0:0:0: Direct-Access Easy Disk 1100 PQ: 0 ANSI: 0 CCS sd 3:0:0:0: [sdc] 7928832 512-byte logical blocks: (4.05 GB/3.78 GiB) sd 3:0:0:0: [sdc] Write Protect is off sd 3:0:0:0: [sdc] Assuming drive cache: write through sd 3:0:0:0: [sdc] Assuming drive cache: write through sdc: sd 3:0:0:0: Attached scsi generic sg2 type 0 sdc1 sd 3:0:0:0: [sdc] Assuming drive cache: write through sd 3:0:0:0: [sdc] Attached SCSI removable disk sda sdb sdc checking sda Trying to mount /dev/sda1 mount: /dev/sda1 already mounted or /mnt/parnerkey busy mount: according to mtab, /dev/sda1 is mounted on /zyxel/mnt/sysdisk Fail to mount /dev/sda1 checking sdb Trying to mount /dev/sdb1 FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! checking sdc Trying to mount /dev/sdc1 FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! Press ENTER to continue...
I have tried a few drives with and without an intermediate hub.
I should say I am somewhat rusty on linux, though used to do a fair amount of embedded development 20 years ago.
Any advice on either of these issues would be appreciated.