FrankGNL

Members
  • Content Count

    36
  • Joined

  • Last visited

Community Reputation

0 Neutral

About FrankGNL

  • Rank
    Junior Member
  1. Thanks for your reply. There is only one fat32 partition created by unetbootin containing: - menu.c32 - syslinux.cfg - ubinit - ubnkernel I didn't meant on the USB drive, but on my additional HDD
  2. I had the same issue "No boot disk detected" for me the problem was that i had a disk attached with a NTFS partition on it. When i removed the NTFS partitions from that disk it started to work
  3. Maybe this question is asked in the past, but is there a reason that the DS3615xs is used and not for example the DS3617xs? Thanks for all your work
  4. DSM 5 is fully working now, but i would like to hide the USB boot drive, i already used the search function, but couldn't find anything helpful. So my question is it possible to hide the USB boot drive and how can i do this? Thanks
  5. I installed 4.3 on my system, but my 5th hdd is not recognized, i already changed the synoinfo.cfg but it won't work. With 4.2 i had no problem. I see that more people have this problem, is there already a fix for this? Regards
  6. 169.254.x.x is a APIPA address, most of the times you get this when the dhcp server is not reachable
  7. Try the microupdate. Update is not working, i tried it with the next code as well sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info > /autoupd@te.info1 mv /autoupd@te.info1 /autoupd@te.info
  8. I ran it on a vmware environment, i it looks like it is working. Both disk are IDE I don't know what to test, i created a volume, installed a package and rebooted the system. Volume is still there Maybe somebody can check what they did with this build, and use it for a build by trantor
  9. Hi Trantor In the 4.3 issue topic, i saw that 1 of the guys managed that the boot usb device will be invisible in DSM. Is it possible to add this "feature" in your next build? Thanks
  10. First of all, thanks for the great work so far with 4.3!!!! Is the solution from VeNoM and neXus ready for "production"? @Trantor Will you come with an 4.3 version? Thanks in advance
  11. spindown for a second volume on a RAID controller was not working. spindown for a third volume on a onboard RAID controller was not working. Everything is installed on the first volume, second and third volume is only for data like movies Regards
  12. In that same folder there is a menu file, try to change that file
  13. /usr/syno/synoman/webman/resources/images/login, here you can find the logos
  14. I built with official sata_mv.c from kernel.org but system start and shutdown after 30sec. I see error about gpio when booting so I add syno_sata_mv_gpio_write function in sata_mv.c and like your voodoo magic... it's boot Everything seem to work fine. Patched kernel for marvell diff file between original sata_mv.c and syno's one Feedbacks please Is this this the possible fix for your issue with DSM 4.3?