As background info, I reset / rebooted one of my TeraStation pro's via Web Interface and got an e-mail confirming the shutdown and then the restart. I have not been able to access thru the Web Interface since. When the local network users tried to access data this morning, there was no access to the mapped drive. They powered the station down and it went thru the system shutdown. When powered back on, it went thru initialization but is stuck at the "System is Booting" status. Any ideas on what has caused this and how to resolve the problem?
The message on the display has now changed to "System Error - Can not laod KRNL"
You can try EM mode by holding the INIT button in while the unit is booting. or you can try the TFTP boot.
http://forums.buffalotech.com/buffalo/board/message?board.id=0101&message.id=881&query.id=14098#M881
Fine, but TFTP-Boot seems to be only for the newer devices as the TeraStation II or Live. Those problems here, that concern me too since tonight, are about the older TeraStation I.
If i try to boot to EM mode, the device says it will but then i even get the E04 Flash error. Because the network device does not start, i cannot connect toflash the firmware again. So whatcan i do to reanimate my TeraStation I?!?
Regards
Hi dja,
Did you get an answer to this? I'mhaving exactly the same problems................
@ fintanc
Are you getting a "system error 04 cannot load kernal" message?? If so then its a problem with one of the HDD's, power down the unit and remove the 1st HDD, if it boots up then you know its a problem with that drive, if you still get the same message then power it down again insert drive one and remove drive 2 and repeat the process. Do this with all 4 HDD to see where the problem lies.
Don't know where you take your knowledge from but following Buffalo sources error E04 is a Flash Kernel error, nothing to do with HDD...
Just to add: With my TS pro I even tried to boot the system without any HDD to be sure that i boot from flash to EM, but in my case this did not work either. But it may be a completely other problem...
@davo
The problem with that is that I can't get the box to boot with anything less than 4 drives in it. Don't know why. I couldn't even do a TPTP boot with less than 4 drives, nas navigator doesn't recognise the terastation at all.
I might se if I can get each drive into another PC and format each of them and start all over again :-(
@dja
Beleive me, i have been dealing with these units for years and have alot more experience than you, 99/100 if its an e04 error then its a HDD problem despite what the faq says!
@fintanc what is the exact error message you get when you remove the drives one at a time? do not remove 2 because the software raid needs at least 3 disks for the kernal to boot.
@davo; I'm getting either a E04 or a E00 MPU error (cant remember the exact text, will check later), its random as to which shows up.
If I try to boot into EM more, I just get the standard "booting into EM mode" message and it hangs at that point and goes no further.
I'll try removing the disks one by one later. If its as simple as a bad/damaged drive then it should be ok, I'll just format and re-flash; however the E00 message worries me. Any idea what that is exactly?
Appreciate your help, by the way :smileywink:
crap. I bought it second hand with no disks, hence the TFTP boot, firmware updates etc etc.
And it was all going so well..................I'll check out the disks first anyway, maybe its that.
Fine art, your post. Let me tell you i am working with several Buffalo storage solutions for years too. I really do not think that you can tell me from one or two postings that you have more experience than me, sorry, alot more...
So if you cannot proof your experience or you are unwilling to do, please don't annoy others with such my-is-bigger posting.
Back to topic: As long as you really proof it, E04 IS a Flash error, despite what you say! This has nothing to do with believe or not, only with facts. My TS does only come up with E04, with four drives, with three and without all drives. No normal operating, no EM.
E04 is a corrupted boot sector on one of the hard drives, you can use the TFTP to fix this or try removing on of the drives to boot the unit. If the unit can boot then it can be restored with a firmware flash and a new or formatted drive.
As i wrote, yesterday i tried to leave out one drive after the other and boot the system but i allways end up with E04 and no network.
How do i use TFTP with the old Terastation Pro 1 (TS-0.6TGL/R5-4)? I do not know how to use TFTP if the system does notcome up with network access but i will give it a try, sure...
Well, I had the same problem. EM mode would hang at EM System booting.
Regular boot goes to 'Loading kernel', the E04, then System booting and hangs.
Buffalo had me try removing single drive, one at a time, no help, booting with just 1 hd, no good, booting and looking at tftp, no good. Nothing worked.
They gave me an RMA number.
But here is the good part. It MUST be a drive problem, cause I bought another unit, put the old drives in it, and it exhibited the same symptoms, so I think the whole stripe/4 disks got corrupted somehow.
Thank god for usb drive unattended backups running every night!!!
Restoring to the new disks right now, slowly (see my post about slow transfer speeds).
BTW, E04 can mean disks. They fixed that in the latest firmware, and if it is a bad disk, it gives an "E23 Bad or damaed HDDx"
Hi,
i cannot believe that it is a HDD problem. If it would be, my system had to come up with the old drives that were running till i changed them (remember: I had correctable errors on one drive during the monthly checks and decided to replace all drives one at a night after the other to be on the safe way and the system was running several without any problems for weeks with the four new drives).
I think it is in deed a problem with the flash, as if during the firmware update something interrupted the system after deleting flash and before refllashing. Because of this, the TS isn't able to start the operating system from the HDDs. The problem now would be to get a new firmware into the flash...
Even if i am looking ahead to the answers from Buffalo support (could use the TS as a Backup), i got a new system two weeks ago. And guess what, it is not a Buffalo NAS, sorry. I had weired problems with an old LinkStation years ago before i got the TS after changing the network switch from 3com to Cisco (a hell of read errors when reading from the drive. The TS had not those problems, but now it is broken as well, that means second loss with Buffalo. And because even the newer TS models are missing needed or usefull features, i bought an other vendors product: There are plenty more fish in the sea...
Regards
Dirk
Well, I got that dreaded E04 error message after my kernel loaded over and over. I called tech support and they sent me a replacement unit. I moved the old drives over to the new unit and it managed to get past the kernel message but it kept saying "system rom loading" for a while. I called tech support and as it turns out, they finally had me swap out the drives. I swapped out the very first one and that one did the trick. It booted up just fine but then I had to load a new firmware before I managed to get it up and running again. I had to restructure the entire array which is going to take 12 hours from this point out.
FYI, I did put the new drives from the replacement unit into the old unit but the kernel still loaded over and over before I finally got the E04 error. So I'm guessing that I had TWO things happen to me, a bad drive and a bad unit.