NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Readynas RN204 - Stuck at Booting... 42%
RN204, OS 6.9.0 Noticed iSCSI misbehaving (no connection, normal shares operational), logged on web GUI, initiated reboot. Reboot stuck on "see you soon". Power-button no reaction. Eventually po...
StephenB wrote:I suggest paid support (my.netgear.com)
That sounds serious. :O
Is it "oh yeah, known problem, don't use iSCSI, you are f*cked but paid support can help you recover the data" or "Have not seen this particular sequence earlier, maybe support'll know"........?
davor242 wrote:
StephenB wrote:
I suggest paid support (my.netgear.com)
That sounds serious. :O
Is it "oh yeah, known problem, don't use iSCSI, you are f*cked but paid support can help you recover the data" or "Have not seen this particular sequence earlier, maybe support'll know"........?
Closer to the latter. Failure to boot with possibility of data loss, complicated by the fact that iSCSI data is opaque to the NAS. I was assuming that you had no backup (though that was a guess).
Though it looks like you've also installed stuff with ssh (pilgrim anyway), which could complicate things further.
Any idea what mount is mounting?
Closer to the latter. Failure to boot with possibility of data loss, complicated by the fact that iSCSI data is opaque to the NAS. I was assuming that you had no backup (though that was a guess).
Though it looks like you've also installed stuff with ssh (pilgrim anyway), which could complicate things further.
Any idea what mount is mounting?
I only installed mc (midnight commander).
pilgrim appears to be what controls the front panel LCD of the NAS.
Usage: pilgrim [-c] [-l path] [ -p path] [-s hex] [-t "term cmd"] [-u file]
-c Clear LCD on termination
-l Message list file path(/var/readynasd/pilgrim.list)
-p Socket path (\0/org/freedesktop/plymouthd)
-s Solid box character code in hex (ff)
-t Termnation cmd (none)
-u Termnation unit ("readynasd.service")Still at 98%.
/bin/mount /dev/disk/by-label/1177b17c:data /data -t btrfs
After 80 minutes, boot finishes.
This time volume is there, but shares are not. Interestingly, shares can be seen from SSH.
davor242 wrote:I only installed mc (midnight commander).
pilgrim appears to be what controls the front panel LCD of the NAS.
So it is (it's not something I'd noticed before).
Is top telling you what the mount command is doing? The "c" toggle should give you it's command line.
davor242 wrote:
In essence, I believe there are issues with iSCSI implementation. :/
Clearly something is wrong, but I don't think you've isolated it to iSCSI just yet. Lots of things will misbehave when the system is running at 98% CPU.
I have created a new LUN with thick privisioning and moved data there. This seems more stable, however iSCSI dropped out again (normal shares work fine).
What I have noticed is that every time the iSCSI drops the btrfs-transacti is running at 100% (i.e one core full load).
The btrfs-transacti will eventually calm down and iSCSI pops up again without NAS restart (although Windows may or may not be confused at that point and PC restart may be necessary, have not kept track of this fully).
So my current guess is:
* Something triggers this btrfs storm
* This affects iSCSI which drops
* Restarting the NAS at this point should be avoided
I am guessing that this btrfs-transacti is doing something useful. But I would consider dropping the iSCSI as a product bug.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
