Jump to content
XPEnology Community


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

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

andale's Achievements

Advanced Member

Advanced Member (4/7)



  1. Running Jun's mod V1.01 on these bare metal systems with Update 7: ProLiant Gen8 bare metal: OK ASUS P9DWS bare metal: OK GA-990FXA UD3 bare metal: OK MSI Z77-GD65A bare metal: OK
  2. Will update 2.3 include a working driver for the LSI 92078i (based on the SAS2308 controller)? When I tried V2.2 my volume became invisible (--> viewtopic.php?f=2&t=24308&start=210#p82586). And is there any chance to get the Intel X520-DA2 working? Since DSM 6 (Jun's Loader and config tool) I can't use this card anymore, I get this error: "ixgbe unsupported_sfp_notify proc entry initialized" (--> viewtopic.php?f=2&t=20095&p=79713&hilit=sfp+unsupported#p79713). Cheers
  3. Mainboard: MSI Z77A-GD65 (Z77 chipset) CPU: Intel i7 2600k RAM: 4x4GB DDR3 1333 Kingston HyperX NIC: onboard Intel 82579V SAS: LSI 9207-8i (FW: 19.0 IT/IR) Last used & working DSM/loader: DSM 6.0.2-8451 Update 6 with Jun's loader V1.01 HDDs: 6x2TB onboard Intel [RAID 5, btrfs, 1x volume of 9TB], 4x1 TB on LSI [RAID 5, btrfs, 1x volume of 2,7TB) Problem: crashed volumes I did the following: 1.) Prepared an USB drive with the image of config tool V2.2 and let the system boot 2.) Choosed the config tool from boot menu and connected via ssh 3.) Let the system generate VID/PID/... 4.) Set S-ATA portmap to prior settings (628; 6x onboard Intel, 2x onboard Marvell, 8x LSI) 5.) Updated the config tool to V2.3 6.) Tried to reboot the system via ssh - no luck (waited for around 35 mins -> reset) 7.) Selected 1st entry from boot menu and connected via browser 8.) DSM stated "Attention! Your volume crashed" DSM now only "sees" the first volume which consists of the 6x2TB HDDs connected to the onboard controller in AHCI mode. The second volume isn't recognized anymore (connected to the LSI). DSM doesn't offer a repair option. I tried to reboot and choosed the config tool again -> Troubleshooting... Only the 6x2TB HDDs are shown. Now I'm currently trying to repair the installation with my "old" boot stick and Jun's V1.01 (good to know that I've a fresh backup of all files).
  4. The SPP for ProLiants usually comes as a bootable ISO file. You can: - mount it on a Windows/MAC machine and create a bootable USB stick (instructions can be found within the ISO) - burn it on DVD and boot from this - extract everything from it an install it within your system's browser Since you're running DSM on bare metal you should give option 1 or 2 a try. Running HP sum won't work on your system...
  5. I've the same problem with an X520-DA2. The card isn't recognized within the control panel of DSM 6.0.2. I also tried the "fix" with insmod as root via SSH. [ 14.594060] Intel(R) 10 Gigabit PCI Express Network Driver - version 4.3.13 [ 14.594062] Copyright (c) 1999-2015 Intel Corporation. [ 14.594098] ixgbe unsupported_sfp_notify proc entry initialized
  6. andale

    DSM 6.1.x Loader

    Are there any plans to fix the error with Intel X520-DA2 cards and similar models? Or are any workarounds available?
  7. andale

    DSM 6.1.x Loader

    Here a few initial experiences with the new DSM loader for 6.0.2 on different bare metal systems... (and one was REALLY strange!) 1st system (AMD): ASROCK FM2A87M-ITX+ with 8GB DDR3 and 6x2TB Seagate - boot up without any problems, upgraded and runs fine 2nd system (Intel): MSI ZA77-GD65 with Intel Core i7 2600K, 16GB DDR3 and 6x1TB Seagate (onboard) and 4x1TB WD (LSI HBA) - boot up without any problems, etc. 3rd system (Intel): HP Microserver Gen8, 16GB ECC, Xeon, 4x4TB Seagate - same over here, no problems (I use the SD card) 4th system (Intel) - this cost me 2 days and one sleepless night: ASUS P9D WS, Xeon, 16GB ECC, 6x4TB Seagate (onboard), Intel X520DA-2 - don't ask what happened but it makes no sense (details below). Note: I have this mainboard/CPU/RAM combo twice (one system on hold for spare parts) and tried it first with a test installation on the spare system from DSM 5.2 with no errors. After a successful test on the spare system I made the upgrade on the live system - worked without errors. Then I had the great idea to install a LSI 9200-8e (FW P19) to connect to a HP P2000 G3 SAS (12x2TB in a RAID10 vdsik). So I shut down DSM, stripped the power supply, plugged in the LSI and fired it up again. The HBA acknowledged the P2000 and DSM began to boot. But nothing happened. No ping, no putty, nothing. So I shut it down (thought of a driver problem with the HBA), removed the LSI and startet again. Same sh*t... Next thing I tried was the reinstall mode within the boot menu. Syno assistant found it immediately through DHCP and I reinstalled DSM 6. During the reboot I manually selected the 1st entry within the boot menu and let it go. Same result. No ping, no DHCP lease, etc. I changed the USB stick (with modifications in grub.cfg) - nothing. Switched USB 2.0 ports - nothing. Tried DSM 5.2 which only offered a recovery (useless). Booted Ubuntu 16 (live version) and gained access with mdadm - everything there, no disk errors, etc. Note: I began at 9 in the morning - at this time it was 4 p.m. The situation became more and more odd. Nothing worked with the DSM 6 loader (no reinstall or force install mode, I even didn't get access). I set the BIOS to defaults, tried the spare system, absolutely nothing. Then I switched to another Intel system (Z77 chipset) where I installed the 6 S-ATA HDDs. Changed the MAC (for onboard LAN) within the grub.cfg, started the system and bingo - welcome back. I reinstalled DSM 6 again and the system ran fine with no data loss. DSM ran a parity check for 3-4 hours. And now the funny thing: I switched it off, plugged the HDDs back to the P9D WS system, changed the MAC again (same USB stick), powered it on and hello! WTF???????
  8. I found the solution for the "unusable" boot stick. It seems that using two special USB 3.0 ports on my X99 chipset leads to this error. When I tried 2 older USB 2.0 ports everything worked fine... Really strange...
  9. Tried 12 different USB sticks on 6 different bare metal systems, downloaded the IMG several times - no luck... And I set up around 30 XPEnologys with DSM 5.2 within the last year...
  10. An ISO would be nice (or a short HOWTO). I also tried to convert the IMG with a full version of PowerISO but with no luck. When you try to convert the IMG to an ISO, PowerISO finds three partitions within the IMG file (1x GPT FAT16 @30MB with 21MB used, 1x GPT FAT16 @15MB and 1x GPT @3MB). If I select the largest partition with 30MB and create this ISO, the file can't be used as a (virtual) boot media in Hyper-V or other systems. The IMG file is also not suitable to create suitable boot sticks for bare metal systems.
  11. Thanks for your reply. Yesterday I finally managed to connect the vdisk volume (RAID 10 on 12x2TB P2000 G3) to my XPenology with the SC08e. Unfortunately every time I try to create a volume DSM stops the process immediately. I think that my controller's firmware (afaik the SC08e is a branded LSI 9200-8e) needs a downgrade to the P19 (IT mode). I'll try this and report back. P.S.: I connected both ports from the P2000 with the HBA. Is it normal that one vdisk volume shows up 2 times in DSM?
  12. The HP Support ISOs are usually restricted to paying customers. I found an actual copy of the SPP (Service Pack for ProLiant) here: http://ddl2.digiboy.ir/SPP2016040.2016_0317.20.iso You can either burn the ISO to DVD or mount it within a Windows system. Take a closer look at the subfolder .\usb\usbkey . Inside this folder you'll find"hpkeyusb.exe". You can create a bootable USB stick (>8GB) with all firmware updates with this tool.
  13. Hi @all. Does anyone know if the HPE SC08e card works with XPEnology? I have a HP MSA P2000 G3 with 12x2TB which I would like to connect to one of my XPEnology bare-metal systems. Cheers
  14. First: transfer rates of ~120MB/s over 1Gb ethernet are pretty normal and the maximum for standard ethernet. Load balancing has to be supported by your router. Even if it does support that your client systems also have to be connected with 2x 1Gb and must support that. Regarding your MAC transfer rates: check your network settings both in DSM (Jumbo Frames, MTU size) and on your MAC.
  • Create New...