bearcat

Ahh, OK Somehow I was under the impression that you used ESXi 😳 It might be a driver issue with the sensors?

Are you using uptodate version of open-vm-tool ?

@matteoking14 I can not give you any answer, but I do have a question for you: Why is Drive #2 showing as a virtual drive?

@milosv Ok, I see. Have you noticed any problems related to it, any new notifications? Or was it just a false positive?

@milosv Did you ever find out what caused this? I just experienced the same thing.

All being on the mainboard is not equal to being the same controller/chip.

I just noticed a new notification when I logged in to 1 of my NAS'es. A N54L running DSM 5.2-5967 Update 9, after an update from -8 11 days ago. When checking with the Security advisor, I was getting the message in the screendump, telling me : "DSM system files have been modified unexpectedly" Checking another NAS, with the same config, updated at the same time, same message. The BIG question I have, has anyone else seen this? (and, what/how/why... )

Are all the SATA ports served by the same controller? Are all set up as AHCI?

@bagheera Are you running bare-metal? From what earlier DSM and bootloader have you been updating? Have look at my post here, it might help.

@snoob_rob Wenn Sie ein Original-HP-BIOS verwenden, ist Ihr interner SATA-Anschluss für CD-ROM nicht kompatibel, da er die IDE emuliert. Wenn Sie es in DSM verwenden möchten, muss der Port auf AHCI eingestellt sein und Sie benötigen ein modifiziertes BIOS. (Google wurde mit Fehlern übersetzt)

@levikats11 If you try to ckeck your networks settings, they will appear blank I guess From earlier experience with a problem like that, after upgrading (from a different bootloader) try these steps: Activate the SSH service in DSM (if not active) Connect to your NAS with an SSH client (e.g. putty) (or from Win 10, open a cmd window, run : ssh admin@my.nas.ip (replace with the actual IP) Enter your credentials (user: admin) Change folder to root (cd /) Delete the xpenoboot folder (sudo rm -r .xpenoboot) If the SSH service keeps stopping, you have to be quick You might have to reboot after this.

@cornekev As stated by Polanskiman here : " Compatibility of hardware usually depends on the loader you are using and the modules it contains to boot the said hardware" But I have seen people mention (among others) SybaSI-PEX40062 and Asmedia ASM1061 based controllers.

@cornekev if my Google skills are working correct, that mb might be using a nForce4 series sata controller, if so ... ******* out of luck as the say, that seems to be unsupported so if you want to use the mainboard, you will need to add a compatible disk controller.

You can not "jump" from 5.2 to 6.x using the control panel, you will need to read and follow this (or this) guide.

Do you know what SATA controller your mainboard is using? (or the make and model of the mb) Are your drives "clean" (=no filesystem)?

1 - Are your HDD's set up as SATA - AHCI ?

iSCSI is a IP based storage networking standard for linking data storage facilities, using SCSI commands/protocol on top of the TCP/IP protocol What you are referring to on the screenshot, is not iSCSI, it's SCSI, a set of standards for physically connecting and transferring data between computers and peripheral devices. It was widely used earlier (pre-SATA) as a effective way to use many diskdrives, with hight speed and low CPU usage, due to own controllers. Optical units and scanners could allso be used in the daisy-chained bus. Did this make sense for you? btw: This thread should have been in the "Virtual Environment" sub-forum I guess...

That is an .img file that allows you to boot and install DSM on baremetal non-synology devices. Based on what version you use, it will emulate the HW of ie. a DS3615xs, DS3617xs, DS918+ (and so on) This is a spesific set of files, created and maintained by a regular member of this forum, on his own sparetime, for free. Does that answer your question?

@giveortake Congrats with your findings, I hope the rebuild will be all OK. I wonder how/why the settings changed, as that is a unusual thing to happen. What BIOS are you using, the "TheBay"?

@TheBlueVoice just out of curiosity, do you have a PlexPass? (as discussed in another thread..)

@TheBlueVoice as he wrote, no HW acceleration, and according to Plex that is expected when not having a PlexPass, so the previously statement from @toker that he in fact had HW acceleration without it seems to be a misunderstanding.

@Vodka2014 Good to see you resolved your issues, would you care to share what you did/how you fixed it, in case others happen to get in the same situation? btw: out of curiosity, why did you update via SSH instead of the control panel? btw2: the folder that might cause problems like this, is called xpenoboot, not xpenology, it is a leftover folder from an older bootloader.

@Larionov8C OK, so you have "no answer"? Then you better read it one more time...

@Larionov8C pay attention to section 4.

@Locutus Your Q's might be answered allready...