Drobo

5N failed FW upgrade

Hi Community,

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. I noted that nasd seemed to be the service that allows the device to talk to the dashboard software, so I tried to restart it.

At the Drobo 5N prompt in Linux I issued the command ‘sudo /sbin/nasd’
Sometimes it gives an error about not being able 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 ‘ps -ax’, kill the nasd process, ‘rm /tmp/nasd.lock’
Then I issue the ‘/sbin/nasd’ command again, and it appears to move forward in the nasd startup then get hung up again

Here are some captures of the text that 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. Also, should I post this information on the thread that I linked above?

Thanks in advance for any help that can be provided!

Hello there!

Sorry you’re having trouble.

On my Drobo 5N2, I see that sysfs is mounted in the 10-mount_filesystems init script here:
/etc/init.d/10-mount_filesystems

Here is a snippet of this script:

# mount /sys
if ! mountpoint -q /sys; then
  echo "[$(date +%Y-%m-%d,%H:%M:%S.%N)] 10: INFO: Mounting /sys"
  if [ ! -d /sys ]; then
    mkdir -p /sys
    if [ $? -ne 0 ]; then
      echo "[$(date +%Y-%m-%d,%H:%M:%S.%N)] 10: ERROR: Failed to mkdir /sys"
    fi
  fi
  mount -t sysfs sysfs /sys
  if [ $? -ne 0 ]; then
    echo "[$(date +%Y-%m-%d,%H:%M:%S.%N)] 10: ERROR: Failed to mount /sys"
  fi
fi

Can you check your init scripts to make sure that everything is present under init.d?

On my old DroboFS, I messed up a firmware upgrade because I had modified a little too much via SSH (changing the profiles and whatnot to add a non-admin user to sudoers or something, this was years ago). My memory is a little hazy, but I think I ended up removing my disk pack and reapplying the firmware to get out of it.

You might also want to post this in the 5N2 forum. Both devices are almost the same, but you might get more visibility outside of the “End of Sale” forum.

Let me know if there is anything else I can do to help.

Regards,

Dom

Thanks for the reply, Dom! My init.d contains the lines of code that you posted. I’ll try posting in the 5N2 forum to see if there are more helping hands there.