Jump to content
XPEnology Community

bearcat

Member
  • Posts

    787
  • Joined

  • Last visited

  • Days Won

    25

Everything posted by bearcat

  1. 1 - if you remove the USB where the loader is, how do you think it can boot...? 2 - There is no such thing as a loader called "DS3617-6.2" to my knowledge, and whenever your unknown loader has loaded, and you "upload" your DSM, what version of DSM are you installing, and do *that* version support the internal NIC on your mainboard? Even if the loader itself is supporting it, you might install an updated version with no native support for your NIC, so you loose connection. 3 - Clean your USB drive, download Jun's 1.02 loader for DS3615xs, edit the grub.cfg. write it to your USB. Manually download the DSM 6.1.7 .pat file for DS3615xs, , boot from the new USB, when/if you find it in your network, manually install the .pat file you downloaded. When done, leave the USB installed and reboot.
  2. @ferdytao One of my systems is an AsRock Q1900-ITX, with Jun's 1.04 and the 918+, running all OK, but it was installed on a clean system, not updated from 5.x Since you have updated from DSM 5.x, you might have some old files making a problem for you. Normally, symtoms of this problem is manifesting itself in services behaving strange, and the network info (in controlpanel) shows up empty. 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. Reboot, and see how it behaves now.
  3. If you install 6.2.1 you must disable your internal NIC to have this working. Edit: As mentioned, for the USB 3.0 to work, you will need to search for a new card, with "native" support in DSM 6.2.x
  4. Do you get any error codes when it fails? Are your VID/PID correct? Any filesystem present on the SSD you are trying to install DSM on? Why are the HDD's not connected?
  5. You might want to "invest" in making a new USB stick, if you want to edit the MAC address(es) to reflect your real MAC address(es). Are your current setup based on 3615? That seems to be the "best" version for the G7 series. With the e1000e NIC, you will be able to use the 6.2.x, but then you should disable the internal NIC, to avoid shutdown problems among other things. Is there any real need/gain with the 6.2? Hard to tell, as it still comes security updates to the 6.1 It might become needed further down the road, depending of the packages in use. 2 of my boxes, N54L, only beeing used as plain media storage (NFS shares), are still running DSM 5.2-5967 with the recent Update 9. And I see no need to update them for the time being.
  6. @wpeterw : The "best" pick for your G7 would be Jun's v1.02b bootloader (DS3615xs), and DSM 6.1.7
  7. @unmesh You might try to disable your internal NIC, unless you already did so. Seems like that have helped some with that problem. btw: you might also update your signature
  8. By the looks of it, you have a problem with phpmyadmin and that is not really a Xpenology problem. Either your database is fu**ed up, your your php config is playing with you. Do not blame the HW or the OS, this is an "Error 40" situation.
  9. 1 - Try another network cable, and use a different port on your router/switch, reboot your NAS.
  10. @MCFLY78 Depending on what version of DSM you are aiming for, you can find many compatibility reports right here or here. Edit: strictly speaking, this might not belong in the "Hardware Modding" section?
  11. Oh crap... seem's like your config was not as forgiving as mine, at least my testbox is still running all OK. Not sure what to think, but if your no-name card had some problems that might explain why all "the sh*t is in the fan" (even if your CPU is watercooled ) From what others have reported, the 88SE9215 chipset should be compatible, so unless there is something wrong with your card, this should have worked. Especially after moving it all back as it was, your system should have been able to repair and run as before. What about the drives themself, have you checked the SMART status lately? I bet you made sure all the cables was properly connected?
  12. @Simonshu What BIOS are you currently using?
  13. @a575606 You know what they say, it's not the size of your gear that counts, but how you use it 🤣 Looking forward to an update on how it works out for you 👍 and the name of the card and chipset.
  14. @a575606 I don't think you got the same as me, as I only got a 2 port card. I was getting the Delock 95260, a Mini PCIe half size card, using the Asmedia ASM1061 chipset, supporting 6Gb/s on the SATA ports, but limited to 5Gb/s on the PCI Express. It fits well in the free slot on my Asrock Q1900-ITX, leaving the fullsize PCIe-slot free for a 10Gb NIC or something els if I find a need for it :-)
  15. FYI: it seems like the 3617 in general has some problems that you never see with 3615, especially when it comes to DSM 6.2.x
  16. btw: this thread might need to be moved to the DSM Post-Installation Custom Built section?
  17. @a575606 : My "microscopic" new SATA controller arrived yesterday, and today I had some spare time to do a test. As the picture will tell, it all went well (with my setup). The first pic show how it was originally, Nr 2 show what happened after I installed the new controller while keeping the original enabled, and used as before. In nr 3 I have moved 1 of my drives, that is in a RAID-0 config to the new controller, keeping the other where it was. And finally, in nr 4 I moved the other drive to the new controller. As you see, the "only" difference between the pic's are the position of used/free slots. Notice: my drives are configured in a Storage Pool as RAID-0, ext4.
  18. As stated ... it might be easy or it might be hard but I think it will be all OK with your config. Just make sure you disable the onboard ports before adding the HDD's (in the same order) on the new controller. But as always, make sure your backup files are up-to-date before doing any big changes btw: since I have not tried to do "this thing" myself, I ordered a small controller do try it out in person will be here tomorrow
  19. Did you at any chance disable your internal NIC, or modify your grub.cfg during your attempt to update?
  20. @Olegin : 1.04b / 918 won't work on the HP N54L Microserver G7, and he already tried an Intel NIC (but I'm guessing it was broken..)
  21. @codedmind You might do a test, and install Kodi on any computer you have, and compare how it behaves there. May I ask what other VM's you are running on your host, and how much RAM/what CPU it have?
  22. @codedmind Then, I would blame your mi box for the freezes, as it has nothing to do with your NAS. (or Any library update will make your client scan files on the NAS and update it's local database, scraping for meta data etc. Configure Kodi to only update library when idle. btw: do you access the shares from Kodi using SMB or NFS? (NFS would be the better choice IMHO)
  23. @codedmind Is your kodi client running inside the same VM as your NAS, or is it a separate client (if so, what is it)?
  24. 1 - no problem adding a NIC as long as it is supported by the drives found in the loader, no need to disable the current, or to edit the MAC, but read on... What might happen is: your current NIC, named LAN-1 in DSM, and eth0 in linux is "presenting itself" with the MAC1=... in grub.cfg, when adding another nic, that might be seen as eth0 by linux, and the specified MAC1 will be applied to that nic, if that is the real MAC of your first nic, you will end up with 2 nic's with the same MAC (and possible IP if using DHCP) causing some confusion (been there, done that). So if you want to keep all 3 lan ports running, you better edit the grub.cfg, adding all 3 MAC addresses. 2 - sata controller, depending on how your current drive-layout is, in regards to RAID level, Drive group etc. it might be easy or hard
  25. @yulyo Do you remember what IP range you used before the move? 192.168.x.y / 10.a.b.c ? What IP range / address are you currently getting on your computer now ? Have you tried using the Synology Assistent? If you remember the old IP range, manually set your computer to be in the same IP range, connect it directly to your NAS and try the Syno Assistent or go directly to the old static IP of your NAS.
×
×
  • Create New...