Enough problems in one topic for ya?
I finally resolved my eSATA problem: got a 750G drive which is 9.5mm, which then fits in an eSATA enclosure that my OXNAS plug will talk to.
So in prep for eSATA nirvana, I booted off my USB stick with the Arch Linux ARM kernel, and noticed that the LED keeps on blinking. The problem seems to be that I don't have an xce.ko installed. And it may be due to the fact that at one point I got desperate to unbrick this thing by just downloading and unpacking the rootfs for OXNAS (plus setting the MAC address file manually).
Time to Google and search the Arch Linux ARM forums...
Ah, ok, the script grabs some of the cloudengine binaries from NAND and merges them in with the rootfs. Fine, I can do that.
Oh, but, oops, none of my /dev/mtdblock devices will mount:
$this->bbcode_second_pass_code('', '[root@alarm usb]# ls /tmp
ce ssh-pfQgZD1417 usb
[root@alarm usb]# mount /dev/mtdblock0 /tmp/ce
mount: you must specify the filesystem type
[root@alarm usb]# mount /dev/mtdblock1 /tmp/ce
mount: you must specify the filesystem type
[root@alarm usb]# mount /dev/mtdblock2 /tmp/ce
mount: you must specify the filesystem type
[root@alarm usb]# ls /dev/mtdblock*
/dev/mtdblock0 /dev/mtdblock1 /dev/mtdblock2
[root@alarm usb]# mount -t ext2 /dev/mtdblock0 /tmp/ce
mount: wrong fs type, bad option, bad superblock on /dev/mtdblock0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
[root@alarm usb]# mount -t ext2 /dev/mtdblock1 /tmp/ce
mount: wrong fs type, bad option, bad superblock on /dev/mtdblock1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
[root@alarm usb]# mount -t ext2 /dev/mtdblock2 /tmp/ce
mount: wrong fs type, bad option, bad superblock on /dev/mtdblock2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
[root@alarm usb]#
')
So somewhere in my beat-it-with-a-bigger-sledgehammer-until-it-boots procedure, the NAND blocks got borked.
Ugh.
So, ok, now what? Any creative ideas?
Thanks much...