Jump to content
XPEnology Community

fswcr1

Member
  • Posts

    12
  • Joined

  • Last visited

Everything posted by fswcr1

  1. fswcr1

    DSM 6.2 Loader

    Hello! I have problems with bringing xpenology up after reboot or shutdown have been issued. The system works fine. Its when I have the system start up again that it is not able to be found on the network. I have to reinstall and then everything is back to normal. I have seen someone else ask the question but havent seen an answer as to why that would happen. ASUS B250-HDV motherboard i5 processor Barebones install 4x6TB drives Intel Pro Dual gigabit network card DSM 6.2.1 Update 1 Bootloader 1.03b no custom files
  2. fswcr1

    DSM 6.2 Loader

    Oh so maybe onboard NIC even though it is Intel network adapter may not work? Get the vendor and device ID from the onboard NIC and you may find that it is supported. So I would understand if the network card never worked at all with this loader but it does initially. I can install the DSM and get it working. Its when I decide to reboot it for my own reason that it no longer shows up. I then have to reinstall and its good again as long as I dont reboot. Would there really be some issue with the built in Intel Ethernet that would only show when you reboot DSM?
  3. fswcr1

    DSM 6.2 Loader

    Oh so maybe onboard NIC even though it is Intel network adapter may not work?
  4. fswcr1

    DSM 6.2 Loader

    Hello. I moved from 6.1.7 using the older 1.02 loader to the new 6.2.1 using the 1.03b loader. Upgrade went fine and all looks good after. When I reboot the machine, I can no longer find it on the network. I have to reboot again and choose Option#2 ReInstall on the loader, reinstall the DSM 6.2.1 to get it back working again. Is there something I am missing so that I can reboot occasionally when I need to without needing to reinstall DSM? Board: DSM 6.2.1 3615X Asus B250-HDV Intel Gigabit network card 3x6TB drives
  5. fswcr1

    DSM 6.1.x Loader

    Your post count maybe too low to add images? Have you tried adding a disk group and then adding the volume after that? Anyone have this problem? The option to create new volume is greyed out. This is a drive that was a volume2 before with the DSM5.2. I could try formatting the drive in an external and then sticking it in the system but I would lose the data on it. Just wanted to find out if anyone else had this issue? I am sure there is a way to go in CLI and mount or change some setting so storage manager will see this. I figured out the problem. When upgrading from 5.2 to 6.0 and keeping the partition format in tact (ext4), I needed to modify the synoinfo.conf file. Edited /etc.defaults/synoinfo.conf Changed "supportraidgroup=yes" to "support_syno_hybrid_raid=yes". This allowed me to create a new volume with my 8TB drive.
  6. fswcr1

    DSM 6.1.x Loader

    Your post count maybe too low to add images? Have you tried adding a disk group and then adding the volume after that? Anyone have this problem? The option to create new volume is greyed out. This is a drive that was a volume2 before with the DSM5.2. I could try formatting the drive in an external and then sticking it in the system but I would lose the data on it. Just wanted to find out if anyone else had this issue? I am sure there is a way to go in CLI and mount or change some setting so storage manager will see this.
  7. fswcr1

    DSM 6.1.x Loader

    I should have posted my motherboard specs. I have a GA-B150M-D3H. I dont think there are two separate SATA controllers? If there is, then maybe my problem is the SataPortMap=6?
  8. fswcr1

    DSM 6.1.x Loader

    I checked but I do not have an option to add disk group. What is the minimum posts I have to have in order to attach images?
  9. fswcr1

    DSM 6.1.x Loader

    I wanted to post some pictures but I get the error that this board has exceeded its quota for attachments. So my system sees all the disks in Storage Manager. The 8TB drive is initialized and in an unused state. When I go to create a volume, the "Create" is greyed out not letting me create a new volume and add the 8TB drive to the system. Otherwise, everything else works great!
  10. fswcr1

    DSM 6.1.x Loader

    Hello! I have DSM6.0.2 with the updates working on my bare metal installation. I have 4 disks (Raid5), one SSD 128GB (SSD Cache), and one 8TB which was just for backup purpose. In the grub file, I put 6 drives for sataportmap. I see all the drives but can not add the 8TB as a separate volume (Volume 2). When I go to the storage manager, the "Create" under volume is greyed out. Is there something I am missing? I am not sure which ram version I am using in the boot disk.
  11. fswcr1

    Working DSM 6

    Since I cant upload, I wanted to state the DSM version I am running. I installed with "DSM_DS3615xs_7393.pat" file which gives you DSM 6.0.1x7393. I then performed update to DSM 6.0.1x7393 Update 2. I dont seem to be able to move to 6.0.2x8451 versions of DSM and that is probably due to the boot disc.
  12. fswcr1

    Working DSM 6

    Hello! This is my first post. I want to thank Oktisme and others that have contributed. I hope this helps anyone that wants to move away from a VM and onto a stand-a-lone system. I dont seem to be able to upload any photos or ISO file to the board. Maybe you can PM and I can send it through Gmail. I was able to get DSM6 working on an Intel Nuc (D34010WYK). Here are the steps I followed: 1) Use Oktisme xpen boot disc and start in "install" mode. 2) Use "Synology Assistant" to find the device and open the web gui 3) Clean install using the "DSM_DS3615xs_7393.pat" file (The migration part has never worked for me from any older versions of DSM) Some modifications I made to get this to work without keyboard needed on the device: I modified the boot disc so that it always selects "Install" mode. I used an ISO image editor and modified the "ISOLINUX.CFG" file. If you want to use "btrfs" format for your volume, you will notice it will say "crashed". I created an auto-mount script that gets launched at bootup to fix this issue. Here is the code for the script: #!/bin/sh mount /dev/vg1000/lv /volume1 I have not yet upgraded my current server to the newest version of DSM yet because I really dont want to destroy 8TB of data on a RAID5. I have played with the Intel NUC from the first Xpenology release to Oktisme's version and havent seen a degraded or crashed volume yet. That doesnt mean it wont happen though. My operational server is a GIGABYTE GA-B150M-D3H GSM, i5 processor, 8GB of RAM, 4x4TB drives, running 5.2x5644 stable. Anyone installed on a GIGABYTE motherboard yet?
×
×
  • Create New...