Jump to content
XPEnology Community

error403

Member
 View Profile  See their activity

  • Posts

    81

  • Joined

  • Last visited

 Content Type 

Posts posted by error403

    Update to DSM 6.1.6-15266 semi-bricked my box

    in DSM 6.x

    Posted

    I was on latest previous version before.
    Got it up and running again!!

    What I did:

     

    -flashed bootloader for 3615XS to USB, was on 3617XS but I was under the impression that people here prefer 3615XS

    -entered MAC address and USB IDs into grub.cfg (previously I forgot about MAC, only entered USB, harmful?)
    -booted, DSM said I could migrate

    -did migrate, worked flawlessly

     

    Thank you anyway, also I didn't know kernel modules could be compiled by users for this kernel.

    Update to DSM 6.1.6-15266 semi-bricked my box

    in DSM 6.x

    Posted

    Hi,

     

    after installing DSM 6.1.6-15266 (which should be safe) my server does start up, but doesn't show up on the network. My HDDs are actively doing something..

    Baremetal, EP45-DS3L, 8GB RAM.

     

    find.synology.com wouldn't find it. Can't ping. Can't ssh. IP static, so no new IP. What can I do?

    DSM 6.1.x Loader

    in Loaders

    Posted

    Jun 1.02b seems to work fine on my old ASUS e2km1l-deluxe AMD-based machine. Are there problems to expect from running on AMD platform, or would I've hit those problem already during install if existent?

    IP 169

    in General Questions

    Posted

    Definitely true, but I encountered a strange behavior lately where I set my machine to correct parameters on ESXi 6.5 recently, and it wouldn't save my changes (it defaulted to SATA instead of SCSI for the virtual HDDs).

    Once I deleted the machine and started from scratch it worked, but this is something you wouldn't think of. Since I set the correct parameters and clicked "save" I assumed it would do so..

    IP problem

    in DSM 6.x

    Posted

    Thank you, but it did quite nothing, especially the arp command.

    I am however able to right-click on the DSM in Assistant and actually access it, but several other errors happen then and I'm again not able to get my existing installation to work (DSM 6.1).

     

    In the long run, I ended up ordering a 916+. XPEnology is nice but it's always a bit risky and often takes a lot of time..

     

    Edit:

    Anyway, now when booting in ESXi DSM does show up on my network, but goes to recovery as my drives are from an older installation. Recovery seems to go well, but after a very short recovery the NAS reboots and again shows the recovery dialog.

     

    Loader image is set to persistent. DSM 6.1 +Jun 1.02 alpha

    Ideas? So I can run the server until my NAS arrives?

     

    Edit2:

     

    Works now, see

    viewtopic.php?f=2&t=30270

    IP problem

    in DSM 6.x

    Posted

    I'm having a major IP problem. Because of other problems with 6.1 I tried to do a clean install of 6.0.2. However, in VMWare DSM seems to drop the IP address as Syno Assistant at first shows a valid one followed by a 169.

    I didn't change anything on my network. It happens on my ESXi host, my Mac (VMWare Fusion) and PC (VMWare Workstation). It also happens on all Jun loaders (all versions).

     

    Once I boot into Baremetal modes it magically works. But that messes with my SATA PCIe card, so this is a no-go..

     

    Any ideas?

    DSM 6.1.x Loader

    in Loaders

    Posted

    Similar here:

    Fresh install- weird IP address/shows "not installed" in Syno Assistant

    Migration from 6.0- whole system disappears after reboot

     

    Both work with baremetal option in grub, but it messes with my SATA card and volumes.

    DSM 6.1.x Loader

    in Loaders

    Posted · Edited by Guest

    Hi there,

     

    I did a clean installation of 6.1 on ESXi 6.5. When I boot with any baremetal option in GRUB (Jun 1.02 alpha) it works (kinda, messes up my SATA card).

    But when I boot with the ESXi option like I'm supposed to do the system shows up in Syno Assistant with an 169.254.0.92 IP and the status of "not installed". Obviously I can't reach it, I wonder how it even manages to show up with that IP.

     

    IP set to static btw.

     

    Help..?

    Tutorial: Install/Migrate DSM 5.2 to 6.0.2 (Jun's loader)

    in Tutorials and Guides

    Posted

    I have a Gen7 N54L and it runs happily on DSM 6.0.2-8451 update 7 thanks to this thread.

    Emboldened by Vodka2014 (thanks!) I tried to update to Update 8 but although it runs to completion at 100% it then comes up with a 'Failed to update the file. The file is probably corrupt.' message and reverts to update 7.

    I'm not going to loose any sleep over this update, but I hope the information is of some help at least!

     

    Same here. Any solutions yet?

    Why bother VMware ESXi?

    in General Questions

    Posted

    You also can migrate to a new server quite easily.

    Also, my server is way too powerful to "waste" those resources to DSM. It runs other VMs (Windows, Linux) when I need those OS too.

    Also, you can install Debian as a second server os for tasks DSM cannot do on the same physical machine.

    Also, depending on your configuration, you can do snapshots. If one update kills your DSM, you just revert.

    DSM only sees 2 HDDs

    in DSM 6.x

    Posted

    Thank you, I was thinking of a limit already too. I once saw a post here to bypass a limit of max. drives but I failed to find it again.

     

    Actually no, I didn't try bare metal, but I did a passthru to an Ubuntu VM and all four drives appeared correctly. So passthru works correctly.

    Also I already removed a virtual SATA controller, which I curiously had in my VM, but still I get those high numbers.

     

    My mainboard has six onboard SATA ports but I need them to boot ESXi. So I cannot disable them. But they shouldn't cause any harm, since the VM will not see them at all.

     

    Edit:

     

    How embarassing. I made a terrible mistake. For some reason I accidentally booted with the wrong GRUB entry. Booted the "ESXi" entry and it worked just fine. Quite a few packages were messed up afterwards, but it was easy to fix. Now the passthru HDDs show up as 1-4.

    DSM only sees 2 HDDs

    in DSM 6.x

    Posted

    I added the controller to a Ubuntu VM, all the HDDs appeared over there so I assume it's a configuration thing (ESXi). Those HDDS conencted via passthru controller appear as disk 33 and 34. Why the high number? I don't get it.

     

    Edit:

    fdisk -l via ssh

     

    Disk /dev/sdae: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors

    Units: sectors of 1 * 512 = 512 bytes

    Sector size (logical/physical): 512 bytes / 4096 bytes

    I/O size (minimum/optimal): 4096 bytes / 4096 bytes

    Disklabel type: gpt

    Disk identifier: C4AC9689-82F7-48DF-A722-6E4F2BA4BFD9

     

    Device Start End Sectors Size Type

    /dev/sdae1 2048 4982527 4980480 2.4G Linux RAID

    /dev/sdae2 4982528 9176831 4194304 2G Linux RAID

    /dev/sdae5 9453280 7813830239 7804376960 3.6T Linux RAID

     

     

    Disk /dev/sdaf: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors

    Units: sectors of 1 * 512 = 512 bytes

    Sector size (logical/physical): 512 bytes / 4096 bytes

    I/O size (minimum/optimal): 4096 bytes / 4096 bytes

    Disklabel type: dos

    Disk identifier: 0x000e416c

     

    Device Boot Start End Sectors Size Id Type

    /dev/sdaf1 2048 4982527 4980480 2.4G fd Linux raid autodetect

    /dev/sdaf2 4982528 9176831 4194304 2G fd Linux raid autodetect

    /dev/sdaf3 9437184 3907015007 3897577824 1.8T f W95 Ext'd (LBA)

    /dev/sdaf5 9453280 3906822239 3897368960 1.8T fd Linux raid autodetect

     

     

    Disk /dev/sdag: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors

    Units: sectors of 1 * 512 = 512 bytes

    Sector size (logical/physical): 512 bytes / 4096 bytes

    I/O size (minimum/optimal): 4096 bytes / 4096 bytes

    Disklabel type: gpt

    Disk identifier: 8948DDCC-100D-49D5-B509-50B0D01152C3

     

    Device Start End Sectors Size Type

    /dev/sdag1 2048 4982527 4980480 2.4G Linux RAID

    /dev/sdag2 4982528 9176831 4194304 2G Linux RAID

    /dev/sdag5 9453280 7813830239 7804376960 3.6T Linux RAID

     

     

    Disk /dev/sdah: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors

    Units: sectors of 1 * 512 = 512 bytes

    Sector size (logical/physical): 512 bytes / 512 bytes

    I/O size (minimum/optimal): 512 bytes / 512 bytes

    Disklabel type: dos

    Disk identifier: 0xd4c8d41d

     

    Device Boot Start End Sectors Size Id Type

    /dev/sdah1 2048 4982527 4980480 2.4G fd Linux raid autodetect

    /dev/sdah2 4982528 9176831 4194304 2G fd Linux raid autodetect

    /dev/sdah3 9437184 1953320351 1943883168 926.9G fd Linux raid autodetect

     

     

    Disk /dev/md0: 2.4 GiB, 2549940224 bytes, 4980352 sectors

    Units: sectors of 1 * 512 = 512 bytes

    Sector size (logical/physical): 512 bytes / 4096 bytes

    I/O size (minimum/optimal): 4096 bytes / 4096 bytes

     

     

    Disk /dev/md1: 2 GiB, 2147418112 bytes, 4194176 sectors

    Units: sectors of 1 * 512 = 512 bytes

    Sector size (logical/physical): 512 bytes / 4096 bytes

    I/O size (minimum/optimal): 4096 bytes / 4096 bytes

     

     

    Disk /dev/zram0: 2.3 GiB, 2491416576 bytes, 608256 sectors

    Units: sectors of 1 * 4096 = 4096 bytes

    Sector size (logical/physical): 4096 bytes / 4096 bytes

    I/O size (minimum/optimal): 4096 bytes / 4096 bytes

     

     

    Disk /dev/md5: 926.9 GiB, 995267117056 bytes, 1943881088 sectors

    Units: sectors of 1 * 512 = 512 bytes

    Sector size (logical/physical): 512 bytes / 512 bytes

    I/O size (minimum/optimal): 512 bytes / 512 bytes

     

     

    Disk /dev/md4: 3.6 TiB, 3995839954944 bytes, 7804374912 sectors

    Units: sectors of 1 * 512 = 512 bytes

    Sector size (logical/physical): 512 bytes / 4096 bytes

    I/O size (minimum/optimal): 4096 bytes / 4096 bytes

     

     

    Disk /dev/mapper/vg1000-lv: 3.6 TiB, 3995837923328 bytes, 7804370944 sectors

    Units: sectors of 1 * 512 = 512 bytes

    Sector size (logical/physical): 512 bytes / 4096 bytes

    I/O size (minimum/optimal): 4096 bytes / 4096 bytes

     

    They are all there, some of them just don't seem to get mounted. Any ideas?

    DSM only sees 2 HDDs

    in DSM 6.x

    Posted

    Except "space" there's nothing I can press during the card's BIOS, and space continues the boot sequence. All the drives appear on the card's BIOS screen. It's set to passthru AHCI and detects them all correctly.

    DSM only sees 2 HDDs

    in DSM 6.x

    Posted · Edited by Guest

    Hi,

     

    I configured my ESXi 6.5 running on a Gigabyte GA-970A-UD3P to pass my Marvell 9215 through to the XPEnology VM. It kinda works, but only two HDDs out of four are being recognised. I swapped the ports and cables, and then the other HDDs are being recognised. So I'm afraid only two ports are working. Are there any known limitations or other known problems?

    hardware upgrade ESXi

    in Archives

    Posted

    Thank you, I just found out the AMD FX based systems will fit my needs as they support IOMMU. For mainboard I'll go with ga-970a-ud3p As it seems to work just fine with ESXi. Still some planning to do though..

    hardware upgrade ESXi

    in Archives

    Posted

    Hi,

     

    currently I'm running Debian latest with VMWare Workstation powering DSM 6. I'd like to switch to ESXi and pass a PCIe SATA card through to DSM. So I'm looking for new hw.

     

    It doesn't need to be of highest performance. Realtime transcoding of a 1080p stream (min. 1) would be nice though. But even my old Core2Quad desktop can do that, so..

     

    Could someone recommend a mainboard to me supporting VT-d and working with this kind of project? Also, can you recommend me a SATA card? For CPU I'd guess I'd go with an i5.

    Maybe two PCIe slots capable of being passed through to a VM would be nice, so I could install a second VM for gaming (Windows VM w/ real GPU).

     

    Of course it's also about the budget.

     

    Thank you!

×
×
  • Create New...