Issues with Asustor 6604T + 6004U expansion unit

[wiggles_x]

I have had the 6604T for about 4 months now and never had any issues with it.

About 3 weeks ago I purchased a 6004U expansion unit to add to my existing 6604T. Ever since I have connected it to my main unit, the main unit goes unresponsive after about an hour or so. The drive lights in the front turn off and I can't access the unit. However, the expansion unit lights are still on. When I try to ping it or get to the webpage nothing loads.

I have turned off all the hibernation settings hoping that it was something with that. But that didn't do anything.

I'm kind of at a loss as to what could possibly be wrong.

I have opened up a case with tech support but no resolution for the past 3 weeks. Has anyone else had a similar issue?

Thanks in advance.

[Nazar78]

I'm not using the 6004U but a cheaper 5 bay magnetic enclosure alternative and so far about a year I have no issues. So I have no experience using the 6004U. However we could try to help. Could you verify that without the 6004U connected everything is ok? You mentioned the main unit goes unresponsive after about an hour or so. Let's try to see if we can catch any error before it hangs.

Ssh into your NAS as root then run below:

Code: Select all

dmesg -n7;watch -n.5 'dmesg|tail -50'

Maximize the terminal window and If you use putty ensure it will not automatically close the window when disconnect in its settings. See if you can catch a glimpse of any error every 500ms when it hangs.

If you can't see any errors before it hangs let's try a different approach which is to dump to a log every 100ms sec.

Code: Select all

dmesg -n7;watch -n.1 'dmesg -c|tee -a /volume1/dmesg.log'

Check the last few lines of this /volume1/dmesg.log for any errors hopefully there's some.

For both commands just incase use CTRL+C to abort and you can remove the log after this "rm /volume1/dmesg.log".

[wiggles_x]

Thanks for the info!

I ran it through the weekend and came across this:
[200539.170303] md49: detected capacity change from 0 to 11988265598976
[200539.171020] md: resync of RAID array md49
[200539.445818] BTRFS: device fsid b97c6640-1e96-4ff3-82ac-eb059901f33a devid 1 transid 259 /dev/md49
[200539.446575] BTRFS info (device md49): using free space tree
[200539.446579] BTRFS info (device md49): has skinny extents
[200542.926550] md: md49: resync interrupted.
[200543.225306] BTRFS info (device md49): using free space tree
[200543.225310] BTRFS info (device md49): has skinny extents
[200543.760548] md: resync of RAID array md49

It looks like the main unit is unresponsive but the lights on the expansion unit are still flashing. I plugged it back in this morning.
I'm going to leave it for a while as its a 10TB Raid 5 config. So if it has to resync I believe that it will take some time to do it.

I'll update tomorrow is its back online. Not sure how long it will take.

[wiggles_x]

Quick update.

Removed the RAID volume and recreated it. It took about 14 hours to build but so far so good.

Looks like the original RAID creation was corrupted somehow.

[wiggles_x]

Update:

Issue was actually with the USB board in the expansion unit. Unit has been sent off for RMA.