dgrigo

Members
  • Content count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About dgrigo

  • Rank
    Newbie
  1. DSM 6.1.3-15152 Update 6

    It was an out of the blue Page not found when starting dsm... someone posted a picture and i had exactly that. If you need to see search for timebomb, but keep in mind imo is not a timebomb but a bug. regards
  2. DSM 6.1.3-15152 Update 6

    Updated DSM to Update 6 on baremetal DS3617,Using jun's 1.02b Loader and everything looks fine.. Did restarts and 2 Shutdowns. BTW I never experienced that Timebomb you all say in various topics, but 1 time when i had ds3615XS with update 1. Imo i think it must be a synology bug and not a timebomb... /wave
  3. Oki Guys thank you very much for the confirmation, yeah i guess only serial number. Any info on the 2 errors i am getting in dmesg /thanks
  4. Hello, I need someone to explain me why the hardware ports are different than the numbers in storage manager... found out the hard way (glad i had raid 6) as i had to replace disk 2 as of DSM reported. So i removed Hardware port 1 Disk and found out i had removed disk 6 according to dsm. As off now, the only way i can identify a hard disk is by checking the serial number.... I guess DSM writes on disk the info but don't have any match on the hardware controller. Maybe @Polanskiman can give me some info? also i need some clarifications on some red errors i am getting on dmseg 1 . invalid raid superblock magic on sda3 - sdx3 does not have a valid v0.90 superblock, not importing 2 . BTRFS has skinny extents
  5. DSM 6.1.1-15101

    Well I bit the bullet and updated , everything works fine up to now, jun's alpha with latest DSM. /wave
  6. DSM 6.1.1-15101

    Hi, Just did a test by taking off my hard-disk and placed a single disk in my baremetal, the usb stick in on mainboard slot and using Jun's first alpha build. My hardware is an ASROCK 236 WSI with an i3 6320 with 16 gb. I started with that single hard disk from scratch did the installation of 6.1 created a share , created a bond interface with the onboard lan ports and updated to 6.1 update 1 first and did a restart. As the update that was offered from synology by air was 6.1.1 I downloaded the small updates for 6.1 and did a manual install until my rig was back to 6.1. update 2. Restart and everything was working as usual. The i did on air update to 6.1.1-15101 and of course restart. back on line again! then i did the last update to 6.1.1 update 1 and restart. System was back on line. then i did a shutdown after i had setup the wake on lan to the first nick. then i tried wake on line and system came online, logged in and everything was normal again... Now what i can do..... just arching myself to update the production unit... but dunno, all this not working systems made me afraid to do it. Oh again so much thanks go to JUN's If you want my dmesg, ask /wave
  7. DSM 6.x.x Loader

    hmm ,check the last line of new dsm update , is it why we experience failures with installs? Version: 6.1.1-15101-1 (2017/05/02) Important Note The update is expected to be available for all regions within the next few days, although the time of release in each region may vary slightly. This update will restart Synology NAS models supporting SSD cache. Fixed Issues Fixed an issue where domain users/groups might be displayed incorrectly when a file ACL is checked via Samba. Fixed an issue where users might experience failure or receive no response when updating domain data. Fixed an issue where volumes might not function normally when read-write SSD cache is used with advanced iSCSI LUNs. Fixed an issue where encrypted shared folders cannot be unmounted when connections with Samba clients have been established. Fixed an issue where failure of installation or upgrade might occur in Package Center.
  8. DSM 6.x.x Loader

    I used the alpha loader that jun posted, and everything is fine so far, except an issue with bios losing data and time (aka reset) so display again press f1 to continue. That was not happening with 6.02 i had it from day 1 of juns loader, any ideas? Thanks Dinos
  9. DSM 6.x.x Loader

    I am using i3 6320 with passmark score of 6025 at 50 W http://www.cpubenchmark.net/cpu.php?cpu ... 40+3.90GHz and is awesome. I was too considered the 6400t for the low wattage but i afraid it will give a very close score but the clocks are slow. If you get 6400t post your finding, sure it will work , but dunno on performance. My use of the synology is mainly for Emby Server and media files. Hope it helps /wave
  10. DSM 6.x.x Loader

    Hello Guys, I will post my experience with a new motherboard i got and everything worked with the older version of Jun's Loader just by swapping board, and using the same sata port numbers for the disks. The motherboard is Amazing with 8 ports sata and 1151 slot with E3 1200 series Xeon. Its the Asrock C236 WSI , you can take a look here : http://asrockrack.com/general/productde ... C236%20WSI I use the internal USB 3 Port for the jun's loader and 8 barracuda hard disk's all on the C236 on board controller. Both Net card works with the old version of jun's loader, I had just setup link aggregation (teaming) and all works fine. Now I need to find a 4 port sata 3 that works nicely on my config to be able to expand my storage further.. I only post this in hope to help anyone holding back from c232 or c 236 chipsets... Hey JUN! thanks again! /wave
  11. DSM 6.x.x Loader

    Guys! the was "A new loader for latest DSM" is causing frustration, why the "was" like its not working anymore, even if its working with latest update and no 6.1 update is available yet. Best
  12. DSM 6.x.x Loader

    If you cant install, i think you missing the ramdisk from the first page... read again and ig you use the page 10 baremetal, it needs the pached ramdisk, else it fails on the install. /wave
  13. DSM 6.x.x Loader

    @ ferno you can find it in the first post, but to make it simpler for you you should edit following service configs manually, replace "console output" with "console none" after installation ssh as root and edit those configs, did everything with putty as root and with VI edit the config files in usr/share/init if you do "grep -r "^console output$" /usr/ 2> /dev/null" you will find the files that try to console output to serial and generate the errors, you should find those : /usr/share/init/syno_poweroff_task.conf /usr/share/init/burnin_loader.conf /usr/share/init/udevtrigger.conf /usr/share/init/bs-poweroff.conf /usr/share/init/udevd.conf
  14. DSM 6.x.x Loader

    Hey!first post, new to xpenology, and i just had setup dsm 6 with 6 by 4tb hard disks system with Jun's loader! wow man! thank you and all the other guys who keep the project alive! if i was able to setup the system with no experience just by reading the thread and correcting errors like the ramdisk change the shutdown alert and quickconnect... seems stable, so i wonder when we will see a proper thread great job JUN and guys! thanks once again /wave