RazzaDazzla

As per the screenshot, I have a few shares. One of them, "LinuxUbuntu" has become unaccesible. I'm unable to map it via WIndows, I'm even unable to browse it when typing in the address directly into Windows Explorer. E.g. \\diskstation\LinuxUbuntu. I'm able to access all other shares, both via Windows and via the Diskstation's built in File Station. Of concern, when I browse the Diskstation's built in File Station, I can't see the "LinuxUbuntu" share. (as Capture2.png). I've tried mounting and un-mounting this share multiple times, but it fails to show. What can I do to access the data in this share?

So after lots of boot attempts I managed to get it to boot successfully once or twice. I then had to power off the machine to move it. I'm now getting all sorts of errors. things like: Error loading /s.v00 Fatal error: 33 (inconsistent data) and: Error loading /scsi_bnx.v01 fatal error: 6 (Buffer too small) Then sometimes it gets to the Esxi purple screen and I get: The system has found a problem on your machine and cannot continue. Could not load multiboot modules: Boot image is corrupted. I'm hoping this may be something simple like some bad RAM that when replaced will fix the issue. If that doesn't solve the issue, is it possible to repair the Esxi installation without losing all the configurations etc. for the RAID and Expeneology DSM etc? Or am I in a world of hurt?

Turned my trusty HP54L off over the Christmas period for a few days when I wasn't using it. Came home, booted it and Esxi won't boot. While trying to boot, it gives: error loading /s.v00 fatal error: 6 (Buffer too small) This sounded to me like a RAM issue. 2GB RAM is successfully detected upon boot. When I initially installed Esxi years ago, I followed a guide to hack the Esxi install to allow 2GB RAM. I took the RAM out, gave it a technical blow, put it back into the other RAM slot. Re-booted and same error. Again, 2GB RAM is successfully detected. Any suggestions on how to troubleshoot further?

Sorry, but I'll be keeping ESXi - Not going to re-build. There must be a way to get SMART info such as temperatures from the hard drives.

Can I give DSM access to the drive sensors? It would be very handy for DSM to send me emails if disk temperatures get too hot. It is also pretty important for DSM (or something else) to email me if a disk starts to fail. Edit: can I view HDD temps in the vSphere GUI client?

I've got a newly built HP54L with ESXI and Xpenology running. I get warning emails from Diskstation Synology (Xpeneology) saying my disk "is -1 ºC, which is not within the operating temperature, 0 ºC ~ 70 ºC." My disk is definitely not at -1ºC, I wish it was . So how do I get Xpeneolgy to give me accurate disk temperature warnings?

I've got a HP54L and I've got ESXi wokring, have a virtual machine running and have booted Nanoboot. I am trying to install DSM via the Synology web assistant and after I select the PAT file from my local machine I get the following error: An error occurred during installation. The telnet service of Diskstation is turned on for error determinination. Please configure your router to forward port 23 to Diskstation, and then contact Synology support. (21). How do I troubleshoot what's causing this error? are there any logs I can view anywhere? Any help you can give would be greatly appreciated. EDIT: I directly connected my PC to the HP54L via Ethernet cable and got the same error message.

I've got a HP54L and I've got ESXi wokring, have a virtual machine running and have booted Nanoboot. I am trying to install DSM via the Synology web assistant and after I select the PAT file from my local machine I get the following error: How do I troubleshoot what's causing this error? are there any logs I can view anywhere? Any help you can give would be greatly appreciated. EDIT: I directly connected my PC to the HP54L via Ethernet cable and got the same error message.