New to this forum format. I have a TS-453D with 4 x 10TB Seagate Ironwolf drives in RAID 5, one large volume.
Not sure which exact firmware, but latest available or one revision old.
I recently shutdown the NAS via the Qmanager App. When starting it up I get the initial beeps but nothing after (which I only just realised).
The power light is on, network light is on and blinking, all 4 x HDD lights are on but solid e.g. no activity.
Plugging into the ethernet direct and setting an IP address on the same subnet as last known IP address doesn’t help, can’t find the NAS via Qfinder, ping is destination host unreachable.
Seems it just stopped booting/working after the last shutdown. Drives were all healthy before shutdown.
Trying to reset admin password and IP to DHCP via hardware reset for 3 seconds didn’t beep.
Any thoughts?
If the unit is fried, can I take the 4 disks and just put them in another NAS and power up and everything will be good?
So, at-worst, you’ll get the wrong mains-input plug. The seller ships to Australia, so ask if they will provide the correct mains plug for the power brick.
If the mains-input cord on the brick is soft-wired (plug-and-socket), just use an Aussie IEC cable, they’re everywhere. Any IT geek will have a few laying around unused.
For some reason, it all came back online overnight. Something weird going on. Should I be concerned this is a sign of imminent failure and get an new NAS? There were no errors as far as I can see in the logs.
If I do, is it as simple as taking the drives out and putting them in the new NAS and away I go?
That’s great news—we’re happy to hear your issue has been resolved! If you need any assistance from our Support Team in the future, please feel free to open a support ticket.
Spoke too soon. It has been starting and powering down on a power schedule for a couple of weeks now, but today it powered on and did not boot. I reseated the HDD’s and memory, still not starting. It passes POST but not booting. Then I randomly plugged a monitor in again and away it went. Not sure what the heck is going on, but why would it just randomly not boot?