Jump to content
XPEnology Community

sagrotan

Member
  • Posts

    27
  • Joined

  • Last visited

  • Days Won

    1

sagrotan last won the day on September 22 2023

sagrotan had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

sagrotan's Achievements

Junior Member

Junior Member (2/7)

2

Reputation

  1. Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.2.1-69057 Update 3 - Loader version and model: @Peter Suh's TCRP v1.0.0.0 (M-Shell) - DS3622xs+ - Using custom extra.lzma: NO - Installation type: VM - ESX6.5- HP ProLiant MicroServer Gen8/LSI 9220 passtrough - Additional comments: Manual update via DSM Control Panel - took some time
  2. Thanks for your reply! Tried directly again with SATA1 (0:0) and (0:1), but still no luck. Out of ideas, I deleted SATA Controller 1 and moved storage disk to SATA0 (0:1) and now I am able to install DSM. Could it be something with SataPortMap/DiskIdxMap? I don't know. My production VM has a LSI2008 attached via passtrough, but I still read about problems with mpt3sas. I think it's a good idea to stick at 7.1.1 for some time.
  3. No drives under 7.2 / 7.1 all fine Using TCRP0.9.5.0 Mshell with a test VM on ESXI6.5U3 on a Microserver Gen8 with a E3-1265V2. Synoboot at SATA0 (0:0) Testdisk at SATA1 (0:0) 21GB I can build a 7.1.1 loader with no problems and I am able to install DSM. When I build the 7.2 loader with the same process, I always get "no drives detected". Tried DS3622 and DS3617 and let MShell do the ID Magic with the Drives. I am out of ideas what to test or where to read. Anyone an idea?
  4. Thanks a lot for your reply. So it was my own inability to include the module successfully. As far as I read in the meantime, it is part of the all modules package which can added with the "ext" statement. Will try it again in a few days. Thanks again Mat
  5. - Outcome of the update: FAILED - DSM version prior update: TRPL DSM 7.1.1-42962 Update 5 - Loader version and model: TRPL v0.9.4.3-2, DSM 7.2 64570 Update 1, DS3617xs - Using custom extra.lzma: NO - Installation type: ESXi - Microserver Gen8 - Additional comments: passtrough drives not recognized, lost Apps & Setting during rollback to 7.1.1
  6. Tried to get form 7.1 to 7.2 yesterday, but failed with loss of my DSM Apps & Settings. DSM was not able to recognize my passtrough drives on ESXi. After some information here and in GIT about mpt3sas problems, I decided to revert back to 7.1.1 with loss of my Settings. I am currently confused, if my struggle was caused by the mpt3sas Issues, or just my personal config fault. Is the mpt3sas Issue still there? Great forum and projects, but sometimes hard to get the current valid information in threads across month an several product versions. Thanks for reading Mat
  7. Hi guys, I am caught with a degraded disk array in DSM. 1 of 4 3TB WD Red had bad sector errors and DSM degraded the disk array. In DSM Drive Nr. 5 is shown as dead. I got a replacement disk but now I am unable to identify the physical disk, which is dead. Because of the buildin Raid Controller B120i I declared every single disk as seperate Raid0. Within the ESX, I published the drives as RDM Mapping into the DSM. Now I need to follow the chain DSM -> RDM Link -> Raid0 -> Driveslot to get the proper disk replaced, but have no clue how to do? Cheers Mat
  8. Hi guys I currently run DSM6.1.x on a Microserver Gen8 on ESXI 6 with 4 drives mapped as RDM. Now I want to change the drives to a LSI Controller and run pass-trough config into DSM. CPU is a Xeon. I am really unsure about the migration path to accomplish that. Just move SATA cable to the LSI controller, configure pass-trough to DSM and everything is fine? Someone there who did the same? Backups are available, but my aim is to keep migration as safe as possible for the data and - I am lazy and do not want to spend hours of rebuild my datastore from the backups. thx Mat
  9. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5 15254 - Loader version and model: Jun's Loader v1.02b - DS3615+ - Installation type: ESX6 on Microserver Gen8 - Additional comments: No reboot required
  10. Thanks for your reply. I read about the license topic several time, but missed it to combine this to my issue. I solved the problem with a valid license which I got from google pictures. Great to see the thumbnails again
  11. Hi guys, my issue is not related directly to Xpenology, but I hope to find some modding guys like you are, which faced the same problem. I use the DS photo app on Galaxy S8 and Iphone to upload pictures and videos to the Photo Station. Unfortunately I did not get thumbnails for any video uploaded, neither on the phones, nor on computers/tablets with different browsers. They stay as grey video-icons. In the DSM logs, I find a lot of entries like "System failed to convert video [/volume4/photo/iPhone/IMG_4688.MOV] to mpeg4", which seem to be related to the issue. I tried to reindex several times without success. Someone any ideas? THX!
  12. All went fine! HP Gen8, ds3615xs, ESX6, Jun1.02b Feedback: Great new structure here, I love it. Suggestion: A template in the initial Post in every new Update thread, which we can copy in each reply AND/OR maybe a poll gives a good status of the update sucess for our xpenology boxes.
  13. Hp Gen 8 ESX6 Update ended with "System Partition failed" - Storage Manager was completely empty - Data accessible Triggered reboot - got nervous "System Partition failed" showed again - Storage Manager was then OK, hit "repair" and all is fine now, but extreme laggy
  14. as I already mentioned earlier in this post: https://homeservershow.com/forums/topic/11872-esxi-65-b120i-hpvsa-hp-microserver-gen8-low-performance/ https://communities.vmware.com/thread/547372 https://seiler.it/solving-performance-issues-with-esxi-6-gen8/ I run ESX6 with scsi-hpvsa-5.5.0-88 without issues. Before downgrade of the driver, I had also very poor troughput. Give it a try
  15. sagrotan

    DSM 6.1.x Loader

    you can use this vmdk, which point to the synoboot.img. Put both in the datastore folder of your VM. I had a crashed/degraded RaiD after bootup on ESX6. One Disk was unlinked from Raidgroup and marked as unused. Had to do a repair over night. I do not think it belongs to the loader.
×
×
  • Create New...