Well - - - OS/5 won’t (or at least it shouldn’t) install on a Gen 1 device.
And if it was loaded onto a Gen2 device. . .the Firmware would show a 5.xx.xxx number, right?
That assumes you could still access the dashboard. . .which you can’t, right?
The only way at this point would be to look at the part number to distinguish. . . .but for goodness sake. . .DON’T POWER DOWN THE UNIT.
If it’s truely Gen1. . . it probably will be stuck “forever” and choke on the indexing task.
If it’s Gen2. . . .it’s gonna be doing indexing for a long, long, long time. Turning it off will risk bricking the unit on reboot.
I would recommend waiting a full week and see if it comes back to life.
Put a cooling fan on it if it starts to run hot.
I hope you have backups… . .
If something bad happens. . . . .Look at the various “unbricking” threads in the OS/3 forum. There are ways to reload the operating system and save the device.
- If you do unbrick it. . . . .for goodness sake. . . .don’t load OS/5 on the device. Reload with OS/3.
- If it does come to life without doing an unbrick. . . . .go in and TURN OFF CLOUD ACCESS. This is what triggers indexing. . .and sooner or later. . . .indexing will happen again.
- If data is not backed up. . .and data is important. . . .consider shucking the drive, loading it into a USB enclosure. . .and using a Linux reader program to access the data from a standard PC.