Test on Seagate 110 NAS - SUCCESS #6
Comments
|
Looks like a problem with the USB stick or maybe the file is missing? Try fatls to list the directory contents |
Hi Hajo Thanks for reply! For some reason it was not possible to read the USB stick file system [a common mistake, I did not check if the file system was readable before opening the thread]. I wiped the partition table and reformatted the USB stick and everything worked perfectly. YES, WORK ON BA110! Soon I will test on BA440 too and I will report the result... Cheers PS: |
|
Congratulations :) And thank you for contributing back your findings! To re-install the system, just wipe the partition table and start the Debian installation again. |
@luctrev , I have I Seagate 110 NAS too, but I'm getting CPU reset when loading the kernel/bootloader. How did you do to bootloader upgrade? Mine is as follow: | | | | | __ ) ___ ___ | |_ ** MARVELL BOARD: MONO LE U-Boot 1.1.4 (Nov 6 2009 - 11:15:26) Marvell version: 3.4.18 U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CDE60 Soc: 88F6192 A1 (DDR2) DRAM CAS Latency = 3 tRP = 3 tRAS = 8 tRCD=3 Marvell Serial ATA Adapter CPU : Marvell Feroceon (Rev 1) Streaming disabled USB 0: host mode |
|
Hello wellsouz, And a question again: is there any information as to whether >4 TB HD's are supported by BA110? Thanks and |
|
Hello @w6s8 I'm not sure (I did it a couple of years ago), but I think it's correct. I'm not at home to check it, but you can safely verify the correct pinout connecting just the GND, 3.3v, and T1IN line of the MAX3232 and booting up the BA110 (the boot process is very verbose). If nothing appears, try the other pin. Regarding the >4 TB HD's, the main problem is the bootloader support, but I think it's OK with this new version @hn created. It upgrades the bootloader and stores the new kernel entirely in flash, so the hard disk is really required only by the kernel when is already running. The real HD limit is the Linux kernel, so >4 TB is totally fine. I think a good approach to avoid any HD issues is to unplug it and use a fast USB flash drive (> 8GB) to upgrade the bootloader/firmware and to install the Debian OS on it. After the whole system is OK, you can reconnect the HD and use it just as a huge mounting point. This is the setup I'm using right now. Best's. |
|
Hey @luctrev, @w6s8 —sorry to bring this back from the dead but I'm also trying to Install Debian on my NAS110. You mentioned you were able to flash the Das U-Boot bootloader. I've been trying to do this myself but have not been able to stop the autoboot from running. No matter what keystrokes I press it does not stop. Any tips? |
|
Hey cdixon1, |
|
Hi @w6s8, Sure. I am using the instructions here: https://github.com/hn/seagate-blackarmor-nas As for what step I am in, I have gotten to the point in those instructions where it says to, "Use the serial terminal to stop the Seagate boot process and to show the ethernet MAC address:". For some more context, I asked a very detailed question on stack overflow here that might help you understand what I'm trying to do: https://stackoverflow.com/questions/67169585/having-trouble-stopping-u-boot-autoboot Thanks! |
|
Install Seagates original linux system to your HDDs. Then use |
|
Hi @hn, Thanks for your response. I'm also having trouble getting the board to respond to any commands. Here is a link to what the boot process looks like: https://streamable.com/87zvxf. At the end I'm hitting keys on my keyboard but nothing seems to be happening. Here is a complete copy of the serial terminal output: |
|
Another update—I had purchased the shell of a BlackArmor NAS 220 and was able to stop the autoboot which is great. However now I'm having an issue where when I issue the |
@cdixon1, try using extload instead of fatload. The usb drive needs to be formatted in ext2. You will probably need to upgrade the bootloader. Please, check this: #7 (comment) |
Thanks! Following the instructions in that thread worked! I just now have to find out the issue with my NAS110. After my experience working with the NAS220 it seems that maybe the RX pin on the board isn't working. Is there any way around that? To be clear my issue with that device is that none of my keyboard commands seem to be received by the device. If I hit keys nothing happens while connected via TTL serial. |
After a complete boot, are you able to enter letters at the prompt You can use a multimeter to confirm that you are using the correct pin and the soldering is in good shape. Also, you can follow the RX and TX tracks and test continuity with your TTL-serial converter. |
No, when I get to a prompt nothing shows up when I type.
With the board powered on and using my multimeter:
The values are the same if I use a screw on the board instead of the ground pin for measuring the voltage at the RX and TX pins. This seems to suggest that all the connections are good?
Sorry for my lack of knowledge, but how would I do this? Edit: After doing some testing with the multimeter there is continuity between the +3.3V and RX pins. I assume this is bad? |
Maybe you have done a short-circuit between the pins during the soldering process. Try using the the multimeter at the continuity scale (the one that beeps when you put the black and red probes together). Unplug the power supply and test each pin with the others. It must not beep continuously.
Using the same approach above, you can test continuity between the pins and the circuit components, following the track that starts at the pin. |
Yes. This is bad. But remember to test continuity with the power supply unplugged. If the problem remains, try to remove all soldering you did and test the pins without the TTL converter. There should be no continuity between the pins. |
|
First of all, thanks for all of your help!
I haven't done any soldering, the pins were already there when I cracked open the box. From seeing posts from others it seems it's like that from the factory. When I test resistance between the pins of the serial port the multimeter measures a ~2kΩ but no beeping on the continuity setting.
No beeping.
I don't see any tracks starting from the pins of the serial ports. Possibly a multilayer board?
Tested with the board unplugged and there is no beeping, but it does measure a resistance (~2kΩ). Should it be 0? If the board is toast it's not big deal as I have the 220. |
|
Thanks! |
|
|
So it turns out there is a short between the RX and +3.3V pins so that's probably why I can't send any commands with the 110. It's not the end of the world I can still use one of the modified stock firmwares floating around to at least have SSH access. With the 220 I completed the installation, but on the first boot I ran into this error: Thoughts? Edit: Using the information here and running the command After that if I run |
|
Alright I have figured out what I need to change in the u-boot environment variables but I cant figure out how the change them and have the changes save persistently . My current u-boot environment variables are: I have figured out I have to change:
to
I know I can do this by using Edit: I figured out that I have to enclose the variable in single quotes to get it to set without running the code. I could then run |
Hello
I have a problem here!
I'm trying to install Debian 9 Stretch on a NAS110, but after successfully performed the Flashing Das U-Boot bootloader. When I try start the Debian installation I get the following error message:
Could reading failure be caused by a problem with my USB stick (FAT formatted)? Does anyone have a guess?
Here the full terminal output:
PS:
cheers
LST
The text was updated successfully, but these errors were encountered: