The issue is that I would need to be able to access the NAS through the lan1 port. However the IP address is no longer responding so no way I can go that route. I read another user who had a similar issue.
No thats not true, the nas doesn't need to have an ip. The fvdw-sl console sends a signal to the bootloader to interrupt boot and let the boot loader upload the standalone kernel and start it. This standalone kernel activates your lan port and has a built in telnet server that lets you talk to it.
The standalone kernel runs from RAM and doesn't need anything from the disks or firmware from lacie to run, that is the beauty of the the standalone kernel, it lets you look inside your nas to study the problem with the disks
Of course the lan port must not be defective.
But very likely this will not be the case. The interface is no working because the lacie firmware failed to load and as result the NIC is not activated.
If the standalone kernel is helpfull can be checked by trying it, no harm will be done to the disks, it doesn't affect the content of the disks unless you give some wrong commands like erase disk.