karkulka

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About karkulka

  • Rank
    Newbie
  1. Hello guys, recently i had problems expanding the storage so I thought i would share the steps how i solved it. For some it might be too detailed but for noobs like me it might be usefull machine: HP Gen8 Pentium G1610T, baremetal. Originaly 3x 2TB drives (WD Red), SHR single array with single volume I was really running out of space and with only 2% free left i figured I would just drop in another 4TB disk. I know that according the syno raid calculator there will be 2TB wasted, but in future i will echange one 2TB for 4TB and use all the space... Anyway, after inserting the new disk and booting the machine I expanded the raid group with no problem. Here i thought the hard part is over, but boy how i was mistaken. Even though raid array expanded to 5,5TB, the volume refused to expand with "Volume failed to expand" message and no better info in the logs, staying at 3,5TB. I thought there might be problem with only 20GB of free space, so I erased some stuff and made cca 500GB of free space, but no improvment and still unable to expand the volume. Turning the services in gui and restarting also didn't help. Long story short here are the steps how I solved it: 1) Login to machine and turn off all the services in GUI except SSH 2) Login to SSH as an admin user (you can’t really use root on DSM6 anymore!) sudo syno_poweroff_task -d -d flag is important as it will keep the SSH enabled. It ussualy terminated my ssh session (even thou many guides says it doesn't), so after that just open new one and login as admin. 3) If you run mount or df now, you will see the volume is still mounted, this is because your SSH login is holding it open example: note the /dev/vg1000/lv adress is the /volume1, I will use it in a moment 4) So lets unmount the volume. sudo umount --lazy /volume1 NOTE: the volume location/adress might be different depending on your machine/setup, just check your df output 5) Close your SSH session – this will allow the lazy unmount to take place 6) Login to SSH as an admin user again – it will complain it can’t mount your user home folder – which is fine, we don’t need it 7) Check vgdisplay - it will show you everything regarding the volumes (physical / logical) sudo vgdisplay -v In my case the LV was already enlarged to 5,44TB and VG was also 5,44TB. Therefore expanding the storage through GUI made it this far. Only thing I need is to resize the filesystem on top of those. 8) Check the fs for errors sudo e2fsck -f /dev/vg1000/lv note: I am not sure if that is mandatory, but it doesn't hurt to check. It takes some time to execute so don't be alarmed note2: the adress /dev/vg1000/lv - is that output from df in step 3). It might be different for you 9) Resize the fs sudo resize2fs /dev/vg1000/lv Again it will take some time, but once completed i had finaly expanded the volume. 10) Final step is to reboot sudo reboot Now you just have to turn on all the services in the GUI you turned off in step 1) Its a pitty that GUI doesn't tell you what is wrong so i hope this will help somebody in the same situation and save him long hours on research. I have noticed similar guides here on forum, but all of them were for VM like ESXI and i am not sure how much different from baremetal that is.
  2. - Outcome of the update: SUCCESSFUL after reinstall - DSM version prior update: DSM 6.1.6-15266 Update 1 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: Baremetal - HP Gen8 - Additional comments: REBOOT REQUIRED - After reboot it didn't come up on network, had to manually restart a than had to reinstall. After that everything OK.
  3. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.6-15266 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Microserver G8 - Additional comments: NO REBOOT REQUIRED
  4. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5-15254 Update 1 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Microserver G8 - Additional comments: REBOOT REQUIRED
  5. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5-15254 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Baremetal (HPE Microserver Gen8) - Additional comments: No reboot required
  6. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 - Update 2 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Baremetal (HPE Microserver Gen8) - Additional comments: Requires reboot
  7. Yes, i have heard about it, but this is the first time I encountered it myself. Will see if it is one-time thing or not... BTW I am using Jun's 1.02b loader if anyone concerns.
  8. Hey there, HP Gen 8 barematel, was on 6.1.2-15132. 1) Updated to 6.1.3-15152 through auto-update, restarted and everything came up just fine 2) Updated to 6.1.3-15152 U4 through auto-update, restarted and Ilo started but syno-soft didn't. Had to hard-reset manualy, but then everything came up normaly.
  9. Maybe check your router. The one from ISP doesn't tend to be any good. I don't have realtek for some time so i don't know all the functions of ti. But i have bad experience with Killer NIC in my notebook. Trying to be "smart" driver has to be un-smarted
  10. Hello there, I want to share my experience with migration to latest DSM. I know the thread title clearly says 5.2 to 6.0.2 but i hope it is not a problem if i share my 5.2 to 6.1.2 experience. I run HP ProLiant Gen8 (G1610) box with 3xHDD, it was DSM 5.2 baremetal. Downloaded Jun's loader 1.02b (kept original Extra.lzma ramdisk). Modified grub.cfg with SN and mac1+mac2 which i used on DSM 5.2 and of course corrected VID and PID. I never reflashed the NIC, so the MAC addresses are true to factory HW setup. Just to be sure i changed the manual IP to automatic IP from DHCP in DSM - no idead if it is neccessary, but it couldn't do any harm right? Turned off the server, swapped the USB stick, checked correct setup in BIOS (AHCI, network boot off,...), restart. Choosed first option in Jun's loader and back to pc. NAS went up on network just fine, choose migrate, provided the DSM 6.1.2-15132 .pat file. It showed error13 "file corrupted". After intial WTF moment i found the file was downloaded incomplete - MD5 checksum didn't matched and file was little bit smaller than it should be (saw some posts about this error earlier here where the guy was sure to have correct vid/pid so maybe this might be the issue). After repeated download the file was OK. I must say that synology server was really slow and the speed was very unstable, guess that's why the .pat file was incomplete at the first time. Anyway, this time the migration went fine. After restart it took some time till the NAS come up in the network and some more time till i was able log in (login screen told me to wait as the database is rebuilding, whatever it means). Windows pcs couldn't acces mapped drives over SMB after migration. Reseting password (seting the same) did the trick and pcs connected to mapped drives just fine. I don't have mac or linux pc so i couldn't test if it's only windows/SMB problem. I need to run more tests to be sure everything is OK, but so far everything seems to be running nicely. However it is less then 24hours since i migrated so i am little caucious about making happy statement. Noticed there is already update 1, but i'll wait a little while till i do it. Last but not least i have to THANK very much to the devs, admins, mods and all users for hard work on loaders, tutorials and comments.