mephy Posted May 23, 2023 Share #1 Posted May 23, 2023 Apologies if anything here is nonsensical, I'm a novice of about 6months to linux. I've been running DSM 7.1.1 for a month or better now on the DS3622xs+ platform. This is running on proxmox 7.3 with a netapp diskshelf and sas controller pass through. I ended up using a vitual usb drive for the redpill loader as that seemed to get the drive "alignment" the closest to actual synology hardware. Things have been going flawlessly, however, I just noticed that I don't have access to any smart logs via the dsm. It appears that the smart logging is working and when connected via ssh all the smart data appears to functioning. I'm wondering if it an issue with drive "alignment" as my drives do appear to be 1 slot off? All logging data avialable is from when the drives were installed in a synology 1821+. Any ideas or help would be much appreciated and thanks for all the work into this project! Quote Link to comment Share on other sites More sharing options...
James62370 Posted July 29, 2023 Share #2 Posted July 29, 2023 I had a similar issue in the past. The fix for me was setting the machine type in my VM to q35. Good luck. Quote Link to comment Share on other sites More sharing options...
mephy Posted December 18, 2023 Author Share #3 Posted December 18, 2023 I was able to resolve this issue and in the event that there is somebody else as ignorant as me, I'm posting my findings..... Revisited this 6 months later as I now have a second disk shelf (same model ,LSI card and hard drive) running Unraid and have access to SMART data. When I first bought the disk shelf, I was told I may have trouble with large Seagate drives (I'm running 16tb Exos). The Ebay merchant gave me a handful of SAS interposers to alleviate this. Well, come to find out.... using the interposers means that SMART data won't be available to the controller. So with that knowledge, I removed the SAS interposers, but could not any of the drives to be recognized. Onto the next headache... After much research into LSI firmware and IOM compatibility, I noticed that my "working" disk shelf was connected via the top IOM. At some point when setting up/purchasing this units I had asked if it mattered which IOM was used and was informed that it did not matter. Well, apparently it does... Connecting to the top IOM made all the drives recognized by the controller and without the SAS interposers. SMART data now available in DSM 7. I'm sure both of these to the more experienced user are relatively silly errors, but now i know! If anybody would like to explain the more technical reasoning behind either of these, I for one would appreciate it! Thanks Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.