Drobo

Drobo 5N (not 5N2) failed firmware upgrade

Hi Community,

I’m posting here because I was given some advice that there are more users monitoring this than the dead 5N forum. I’m hopeful that the two devices are similar enough that help won’t be too difficult.

I have a 5N that failed a FW upgrade. I can no longer access the device via Drobo Dashboard, but I can ping to and from the 5N. I followed the instructions here and can watch what I believe are successful boots of both the Linux side and the VxW side.

It seems that nasd is the service that allows the device to talk to the dashboard software. Is that true? I checked to make sure that it was running with a ps -ax, and it was present. Then I saw in the previously linked forum post that restarting nasd sometimes helps.

So, at the Drobo 5N prompt in Linux I issued the command '/sbin/nasd’ and it errors out saying that it is unable to access a file named /tmp/nasd.lock

Drobo5N:/ # sudo /sbin/nasd
Last login: Tue Sep 28 07:27:14 PDT 2021
nasd built 15:28:49 Jan 6 2020 rev 114093.10
[2021-09-28,07:31:34.227925880] main: Unable to acquire a lock on /tmp/nasd.lock: Resource temporarily unavailable (11)
Drobo5N:/ #

To resolve that I ‘pkill -f’ the nasd process, ‘rm /tmp/nasd.lock’, and then issue the ‘/sbin/nasd’ command again. (It has to be done quickly to be the restart from monitrc) It appears to move forward in the nasd startup then get hung up again. This is actually what I believe is happening on initial startup, too, with the difference being that I can see the debug output on the restart.

Here are some captures of what I am seeing now.

Drobo5N:/ # sudo /sbin/nasd
Last login: Tue Sep 28 07:25:52 PDT 2021
nasd built 15:28:49 Jan 6 2020 rev 114093.10
[2021-09-28,07:27:14.352048755] SledNetAgent: starting agent
[2021-09-28,07:27:14.753127604] SledNetAgent: allocated threads
[2021-09-28,07:27:14.753184964] main: INFO: === Initializing Net Agent ===
[2021-09-28,07:27:15.153634243] Registered listener
[2021-09-28,07:27:16.055342182] CountNetworkInterfaces: INFO: Device has 1 ports
[2021-09-28,07:27:16.055666867] CountNetworkBonds: INFO: Device has 0 bonds
[2021-09-28,07:27:16.055771389] ******configWriteEnabled = true
[2021-09-28,07:27:16.256072991] main: INFO: === Initializing Console Command Thread & Handler ===
[2021-09-28,07:27:16.256105311] HandleTimeoutEvent: icore_control: INFO: Starting control loop with a 16384 bytes buffer.
[2021-09-28,07:27:16.256307355] DNAS Console Commands registered
[2021-09-28,07:27:16.262781459] HandleTimeoutEvent: icore_control: INFO: Unable to open sysfs: No such file or directory (2).
[2021-09-28,07:27:16.262853020] HandleTimeoutEvent: icore_control: INFO: Exiting control loop for 10 seconds.
[2021-09-28,07:27:16.331837441] Executing command ‘dnasStatus’
1
[2021-09-28,07:27:18.013047586] SledDiscoveryListener::AddHost: Added client info for 192.168.0.119:58277 (flags 0x3e, 0x3e)
[2021-09-28,07:27:21.059703269] ValidateNetworkConfig: Called with XML:

<?xml version="1.0" encoding="UTF-8"?> 11 100 full Drobo5N Workgroup 1 192.168.0.127 255.255.255.0 192.168.0.1 1.1.1.1 8.8.8.8 0 1500

[2021-09-28,07:27:21.059899191] ValidateNetworkConfig: INFO: Node NasMinimumProtocol is not valid, using default value ‘’
[2021-09-28,07:27:21.059942871] ValidateNetworkConfig: Node NumInterface not found, assuming old style config
[2021-09-28,07:27:21.059981512] parseOldXML: INFO: Reading static IP config for eth0.
[2021-09-28,07:27:26.269531604] HandleTimeoutEvent: icore_control: INFO: Starting control loop with a 16384 bytes buffer.
[2021-09-28,07:27:26.275896223] HandleTimeoutEvent: icore_control: INFO: Unable to open sysfs: No such file or directory (2).
[2021-09-28,07:27:26.275967784] HandleTimeoutEvent: icore_control: INFO: Exiting control loop for 10 seconds.
[2021-09-28,07:27:26.370088756] Executing command ‘dnasStatus’
1

It looks like DHCP is working correctly, but then something else is going wrong. Perhaps my next hurdle is to figure out what this means ‘Unable to open sysfs: No such file or directory (2),’ or maybe there’s something else I’m missing that should be happening first.

Oh, and if I go to ‘Drobo Discovery Settings’ and Add ‘Drobo by IP’ I can force some kind of basic communication that looks like this

[2021-09-28,07:33:03.223019878] SledCommandListener::HandleTimeoutEvent: Got a command connection from 192.168.0.119!
[2021-09-28,07:33:03.223095879] SledCommandListener::HandleTimeoutEvent: No session yet so refusing command connection from 192.168.0.119
[2021-09-28,07:33:07.700472562] Executing command ‘dnasStatus’
1

I wish I knew more about the Drobo’s protocols to determine what to troubleshoot next. If anyone can help, I’d be very grateful.

Thanks in advance for any help that can be provided!