-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test on Seagate 440 NAS #5
Comments
Some thoughts:
I suggest the following steps:
If the kernel and debian installer start without problems, try partitioning the hard disks, installing base system, packages etc. but do not execute my
|
Great thanks, just ordered a FTDI232r, will keep you updated |
Looking at your update on 440. I have one and lost the application that reset it. The problem here was that no new firmware was being developed. So, if it works, I will try also. |
@gazcbm I tried here to put Debian 5. Its works fine, but, there is a problem that I didn't find the solution:
Although, some peoples said that is possible change a file to show the correct messages. I tried it too, but, unsuccessful. So, I reset the NAS to Original Firmware. Remember: I didn't use the NAND Flashing, only using U-boot. |
@gazcbm do you have the application that reset the storage? The one on the Seagate website does not work at all... probably some problematic binary. |
@condector Do you need to format a disk? I remember when my NAS did not want to start to start. So, I removed the HD, and I had used a software (don't remember its name), created a RAID array in Linux. So, I formatted using Diskpart. Put it on NAS and it worked. I remember that the Error messages was: No System HDD found. So, problem solved. But I tried it about 1 year ago and worked well. http://knowledge.seagate.com/articles/en_US/FAQ/3004en |
No no, the disks are ok, the problem is that I want to factory reset my system, but the application that creates the URL using the MAC Address of the NAS not work anymore (the application on the Seagate web site). |
If you have this tool, I will really appreciate you know. |
I looked for it, but I didn't find. Are you sure that NAS is Turn On? If you want, you could reset through the button on the back. I found this link: http://www.tomshardware.com/answers/id-3549625/rebuild-reset-seagate-blackarmor-440-nas.html |
is there the possibility to port this to BlackArmor SRN02D? Here is the boot log: |
@vrtlspd From a quick 1-minute check of the boot log I think it shouldn't be too hard to install a standard Debian GNU/Linux system on the BlackArmor SRN02D. U-Boot is located on flash, Kernel and Initramfs are located on SD card. You can start by stopping the U-Boot loader ( This project is for the "old" Blackarmor series and due to the big differences in hardware it does not make sense to include support for the "new" series. |
Hi, CPU works at 700 MHz (700/1/1) |
Hi After successfully install on NAS110, I am now getting ready to do the installation on NAS400. Thanks |
@luctrev I suggest to try to do the basic install first, to see if things work at all. I think there will be ways to fiddle with the necessary IO pins for LCD and buttons if you have a running system. |
I can't tell (from the above) whether anyone has actually had any success on a BlackArmor 440. The motherboard on mine seems quite different from the 220...I can't find any serial connector/pins to control the boot process. So, there's nothing to connect a FTDI232r to. There is an empty space (labeled CN4, if I recall) that has no pins--just two rows of five solder points where a connector might go. Maybe Seagate removed the serial interface connector to stop folks like us from hacking their systems? (I'm not eager to solder a new connector--not even sure what this empty space is intended for.) Ideas? Has anyone else actually disassembled their 440 NAS? |
Hi Look here https://github.com/hn/seagate-blackarmor-nas/blob/master/seagate-blackarmor-nas.txt
|
Hi @hn When I upgraded BA400 to Debian 6, I saved the following files: /etc/btn.poweroff But in case of a fresh install I don't know if it will work! |
I think this is the right part. When I originally did the pin outs it had the headers. I just used jumper wires to hook things up. Now they have all those ftdi breakout boards. With all the activity on this it make me want to pull the two 440s I have out of storage to play with again. |
@luctrev I think those utilitiy binaries you saved do not help that much because they likely do not contain code to directly access the hardware. The fan speed can be set via I2C: https://github.com/hn/seagate-blackarmor-nas#additional-tuning. It is very likely that the buttons and LCD display are connected via I2C bus or dedicated IO pins as well. You may need to fork/patch the kernel DTS file (https://lore.kernel.org/patchwork/patch/529020/ ) to access them (or to get the kernel running at all, to access additional SATA ports, ...) But that's just a quick guess. If you or someone else owns a BA440, just try to boot the kernel and basic system to see if things work at all. |
@mjseeley (and anyone else with a BA440): I can provide some photos if desired (but it's not pretty--I used a "female" header that I had sitting around, so the connections are extra tall!). Now to upgrade the firmware/OS... |
@LoonSongSoftware any progress on the firmware/OS upgrade? |
No. It failed and the machine bricked. Now I’m trying to find some time to try to reload/reset the firmware via the JTAG interface. Maybe over the winter.
From: Ken-L <[email protected]>
Sent: Monday, December 2, 2019 3:47 PM
To: hn/seagate-blackarmor-nas <[email protected]>
Cc: D. Scott Miller <[email protected]>; Mention <[email protected]>
Subject: Re: [hn/seagate-blackarmor-nas] Test on Seagate 440 NAS (#5)
@LoonSongSoftware<https://github.com/LoonSongSoftware> any progress on the firmware/OS upgrade?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#5?email_source=notifications&email_token=AEHXFITOQWTGICMTQKT26Q3QWVX3RA5CNFSM4GQFU5SKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFU2ZIY#issuecomment-560573603>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEHXFIQJL232Y3OIJ2PFGDTQWVX3RANCNFSM4GQFU5SA>.
|
@LoonSongSoftware what do you exactly mean by 'bricked'? The U-Boot bootloader does not start? Is there any serial output? |
It’s been a while since I fried it. But my recollection is that the board didn’t have a the serial connector soldered on (like your photo). So I think I did make the connections (surface mount) and saw no signals.
But give me 24 hours and I’ll dig out the machine and refresh my memory.
From: Hajo Noerenberg <[email protected]>
Sent: Monday, December 2, 2019 4:19 PM
To: hn/seagate-blackarmor-nas <[email protected]>
Cc: D. Scott Miller <[email protected]>; Mention <[email protected]>
Subject: Re: [hn/seagate-blackarmor-nas] Test on Seagate 440 NAS (#5)
@LoonSongSoftware<https://github.com/LoonSongSoftware> what do you exactly mean by 'bricked'? The U-Boot bootloader does not start? Is there any serial output?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#5?email_source=notifications&email_token=AEHXFITIFEH2EHRTFDHGKPDQWV3VXA5CNFSM4GQFU5SKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFU5V6I#issuecomment-560585465>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEHXFIS2ZAA52ZBJ54LSX7DQWV3VXANCNFSM4GQFU5SA>.
|
@LoonSongSoftware |
I've done some work on the 400/440 in 2015, which may or may not be useful to the discussion here. From my paper notes attached to the device, I can see that back then I got a stock install of Debian Jessie running, but I ended up putting the device away because it randomly crashed and I did not have the time to debug it. My notes are available at https://gist.github.com/bantu/d456865b91be6c99320b Highlights probably include
|
It appears that in my setup, the kernel (and initrd and device tree) is loaded from the ext4 root filesystem held on an external usb drive. This should allow me to trivially make a backup of the system and to try to update to stretch and then buster. |
@bantu thanks for sharing your work! This looks very promising, I've shared your links in my README. Maybe you or somebody else will find some time to finalize the patches (it's christmas again ... :)). |
I've updated from Debian Jessie to Debian Stretch to Debian Buster using the usual |
My device also behaves this way after updating to Debian Buster. I am not sure how to debug this problem. |
Any new developments on this? I have an old 440 I am very interested in trying this on, but I am a little out of my league and was hoping someone might be willing to help me through it. EDIT: Although now I see you had random crash on both Jessie and Buster. I misread that previously. |
I’ll try to spend some time on this over the next day or so. And will let you know.
From: sharrq27 <[email protected]>
Sent: Thursday, February 6, 2020 2:20 PM
To: hn/seagate-blackarmor-nas <[email protected]>
Cc: D. Scott Miller <[email protected]>; Mention <[email protected]>
Subject: Re: [hn/seagate-blackarmor-nas] Test on Seagate 440 NAS (#5)
Any new developments on this? I have an old 440 I am very interested in trying this on, but I am a little out of my league and was hoping someone might be willing to help me through it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#5?email_source=notifications&email_token=AEHXFIQ6D7PSBBO6FRPEPA3RBRPGDA5CNFSM4GQFU5SKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELAOHKI#issuecomment-583066537>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEHXFIQYFWSFAARAUQJNWU3RBRPGDANCNFSM4GQFU5SA>.
|
OK. I finally got around to digging out the NAS440 and trying again. Still no luck. Here are the symptoms:
Sorry I wasn't more successful and don't have any great suggestions. I have lots of backups of the firmware and software, but I didn't anticipate not even getting uBoot to start. Fortunately, I was willing and able to withstand a bricked NAS440. |
Thanks so much for looking into this, really impressed you spent the time to do this investigation. Guess just going to stick with the stock, since it’s better than a brick for me.
… On Feb 17, 2020, at 3:40 PM, LoonSong Software ***@***.***> wrote:
OK. I finally got around to digging out the NAS440 and trying again. Still no luck. Here are the symptoms:
when the machine is plugged in to power, the display shows the row of blocks (typical for startup) and stays like that. The blue power light comes on. Pressing the power or reset buttons does nothing.
if there's a serial connection (as described in README.md, but with nothing attached to pin 9 (+3.3v)), there will appear to be a serial connection, but no obvious data flow. (But I do get a few random bytes if I unplug the power (before the serial connection receives . Linux continues to see /dev/ttyUSB0, so the connection is sort of alive.)).
if I do the same, but also connect the +3.3v to pin 9, I get slightly different behavior: the connection will drop (/dev/ttyUSB0 goes away) when power is turned off, and it doesn't appear in Linux until power is applied to the NAS. That makes it difficult to see if there's any data sent immediately upon NAS power-on, but I doubt it.
The JTAG space is the same as for the serial port--no soldered-on connector. And I only see circuit board traces for GND and nSRST. That doesn't look like anywhere near enough to re-flash uBoot. So I'm not inclined to bother pulling out the soldering gun again.
Sorry I wasn't more successful and don't have any great suggestions. I have lots of backups of the firmware and software, but I didn't anticipate not even getting uBoot to start. Fortunately, I was willing and able to withstand a bricked NAS440.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@LoonSongSoftware I remember successfully using the serial console back then. Here are some pics. |
If I remember correctly, the next step after connecting to the serial console was to "upgrade" to an "u-boot netconsole". However, I do not recall whether that applied only after the u-boot on the flash was updated or also before. |
With no u-boot prompt (or anything), I don’t see how I could try that (all of the Google results suggest that enabling netconsole needs to be done from a u-boot console prompt). But it may be helpful to others.
For anyone considering doing this on a BA440, what I’d do differently (at least) would be to confirm that I can connect to the serial port before overwriting firmware. Yes, it would involve buying a Serial-USB converter (as shown). And, yes, it might involve soldering a connector (or individual leads) to the board. But it would provide a better baseline as to what to expect when connecting if something goes wrong. All I get is (I think) a connection, but with no evidence that data is coming or going. So I can’t tell for sure if it’s crappy soldering (possible, but I doubt it) or no u-boot resident in the firmware (which I suspect).
|
Hi, https://github.com/hn/seagate-blackarmor-nas Everything works well up to postinstall.
Anyway I tried to finish the procedure but, of course, give me error getting kernel
Can anyone help me complete the procedure in the right way? |
@flex4gh , see README.txt:
Commenting |
@hn I know that support for ba440 is allpha. That's not a problem for me. I have time to work on this project. |
@flex4gh I think it's worth trying with the latest patches. And ... even Bullseye works :)
But remember: HDD slots 1 and 2 do NOT work |
I appreciate your work. I have a Nas 440, I am not experienced on linux, so I want to try to use it when it starts working stable. I enjoy following your updates. I hope you succeed, thank you all. |
Hi - I have a Seagate 440 NAS that I would like to try your latest codebase on. Happy to provide my findings here. Is there anything I should be checking beforehand?
The text was updated successfully, but these errors were encountered: