bearcat

Members
  • Content Count

    428
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by bearcat

  1. Since I have the Q1900-ITX, I have 4 on-board ports, but I added a microscopic 2 port Delock 95260, as can be seen here.
  2. @chleb As it says, it deletes a folder, called "xpenoboot" (with the files within). This folder are remains from a previously used bootloader, and the files within are making a conflict with the new bootloader and files. With a fresh install, it will not be a problem at all, since the folder/files do not exist, but an update will leave some folders/files and may generate problems.
  3. @fimluyeena From what I can "see" you did what I had in mind, booting from Juns 1.02b, manually installing using DSM_DS3615xs_15284.pat, that should be upgradable to update 3. As in regards to the MTU, unless you "need" to adjust it, it will run on 1500 as default. As can be seen on these pics, the settings looks a bit different on DSM 5.x and 6.x, in 5.x they use the term Jumboframes, in 6.x they just say "manual", but both indicate 2000 as the first "step" above normal. Seeing as you got this far, as to face new problems, there is no doubt that your NIC is working without any "extra.lzma", but sometimes the"find.synology.com" may fail to find any targets, even if Syno assistent find them, as seen below in the dual screendump. Ok, now to how you may do a full, clean install: As long as you don't mind risking/loosing the data on your drives, you may just delete the partitions on them. The drives will all have 3 partition (at least). 1 - DSM system partition 2 - swap partition 3 - your data volume The easiest way to do so, would be to leave the drives in your computer and boot a Live Linux from USB, using parted / Gparted to delete at least 1 and 2 (and maybe even 3 if you want to start all clean). This has to be done on ALL the drives. This way the drives will look as new to the Syno installer when you boot from your bootloader. Now a question from me: How is your local network setup? I notice you mention direct setup to your Mac, internet sharing and no router among other things.
  4. @fimluyeena Ok, then just to make sure you don't spend unnecessary time to debug this, you should "start over" with a fresh USB stick, with no "extra.lzma". (btw: has this been a bare-metal fresh-install with DSM 6.1.7, or has it been updated from a previous version?) Remove the add-on graphics card, as you wont be using it anyways, keeping the system clean. Set all your HDD's to AHCI. Use Jun's 1.02b, DS3615 and the DSM 6.1.7 .pat (manually downloaded and installed). Make sure your grub.cfg is configured with your MAC/VID/PID.. This way your NAS will be found both with the syno assistent or the find.synology.com (and you can also find the IP adress handed out from your DHCP server if you look at the logs etc.) Mac OsX: did you enable the AFP service on the NAS? (you should still be able to access the NAS over SMB/NFS even if AFP is off, if SMB/NFS is enabled on yoru Mac) MTU: What values do you have on your 1- Mac 2- NAS 3- Windows computer 4- Router (they should all be equal and default value for ethernet is 1500)
  5. But .. why? Your G7 will happily work without it. But ... how? Your Windows computer will not tell you the IP of your NAS with it's ipconfig command. By using your combo of Jun's 1.3b, DS3615 and DSM 6.1.7 update X, you should have the best and most stable "out of the box" version for your HP N40L, with no problems.
  6. LOL Somehow I read it, but I did not "see it"... But, I think that for you to be able to see the drives in DSM, you might have to set them up as single drives in Raid-0. If you have a spare drive, with no needed info on it, you could wipe it, and create a single drive Raid-0 on it, and try to install DSM. (this is to be done after you have disconnected all your other drives for security reasons). btw: if you replace your P410 with a 2 or 4 port "standard" SATA controller, with native support, your problems would be over I have a Q1900-ITX running myself, with an added 2port SATA controller in a microPCIe slot, giving me a total of 6 ports.
  7. @usus Would that be the HP smart array P410i ? What is the rest of your HW setup, and what OS are you currently using? If, and I say IF, you want to try any of the "extras" out, make sure you have a full backup set Same thing goes for you current Raid1, assuming it is a HW raid you will not be able to "import" the raidset into DSM. With XPEnology/DSM, you will be using software raid.
  8. @AMelbye Oh *******... If you got hacked, I hope your NAS is not infected by some ransomware, causing the fileproblems.
  9. @usus The HP P400 is a SAS Raid controller if I'm not wrong. how is the drives configured? You might need to configure them as single drives, preferably AHCI (if possible). Found something related here
  10. 1 - make sure all your HDD's are in working order, with no SMART errors. 2 - create .sfv files on your local media before uploading media files and .sfv files to NAS, then download them to another folder, before verifying the media files using the .sfv files 3 - repeat the download and check on an "outside" system, to see if it is a local or external problem. How is your HDD's configured (raid etc.)?
  11. 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.
  12. @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.
  13. 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
  14. 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?
  15. 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.
  16. @wpeterw : The "best" pick for your G7 would be Jun's v1.02b bootloader (DS3615xs), and DSM 6.1.7
  17. @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
  18. 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.
  19. 1 - Try another network cable, and use a different port on your router/switch, reboot your NAS.
  20. @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?
  21. 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?
  22. @Simonshu What BIOS are you currently using?
  23. @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.
  24. @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 :-)
  25. 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