Jump to content
XPEnology Community

Bose321

Member
  • Posts

    47
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Bose321's Achievements

Junior Member

Junior Member (2/7)

0

Reputation

  1. Just tried to update from 69057 to .1 version but it doesn't seem to be booting anymore. It is looping with these messages: I tried to boot into the loader and run my.sh postupdate but it didn't do anything. What else can I try? Just rebuilt the loader. Seems to work again. I thought this loader eliminated the need of rebuilding loaders the whole time and having to mess around?
  2. Unfortunately codecpatch doesn't run on an updated system (Update 2), the amepatch did work, but only shows HEVC on my DS3617xs. Is this to be expected? I only need it for my Synology Photos.
  3. I just tried to update from 7.1.1-42962 U1 to U3. Now my machine will not start. It's in a recovery loop. I tried to run the postupdate command when I go in the loader from GRUB, but that gives kernel panic errors. What has happened? How can I fix this? Thanks in advance! I'm on loader 0.9.3.0. I tried to upgrade to 0.9.4.0 but that didn't help. Also, what's weird, when I do the postupdate command it says the version is U2. Never mind, got it working follow this post:
  4. Sadly I can't get the 3622 working on unraid as the internet is then broken with whatever adapter I try to use (e1000, e1000e, virtio)
  5. I've added these to my Unraid setup, and everything works great, except for the shutdown/reboot commands etc. They're not doing anything I'm afraid. Any idea what's missing here?
  6. Can anyone help me getting the shutdown and reboot commands to work on Unraid? (qemu I believe). I've tried the acpi addon but that didn't help. I'm still on 0.4.6 so I'm not sure what has changed and if it's worth upgrading? I'm running the DS3617xs since that's the only one that wanted to boot at the time.
  7. Maybe it matters which build is chosen? I'm on a 3617 and it doesn't work on Unraid.
  8. I've rebuild my image with the virtio driver on the DS3617xs. It's indeed MUCH faster then the e1000 and e1000e were for me on Unraid. I already was thinking my complete NAS was sluggish, but it was just the driver. DS Photos was like watching a 56k modem loading, now it's good again. Only thing left that's not working yet is the power controls from Unraid. I thought I add the acpid ext, but it's not for the DS3617xs on 7.1.
  9. Does this also work for Unraid? I have made a build but the shutdown commands do not work. Also Virtio and Virtio-net drivers do not work for ethernet. They did before without extensions strange enough. Now using e1000e but the speed reported in DSM is way off, it always reports 500mb/s or 15gb/s or crazy speeds like that.
  10. Anyone else with wrong speeds reporting in DSM? I've got a 3617xs on Unraid but it says the upload and download are like 5gb/s. I'm using e1000e as ethernet.
  11. It's available for 7.1.0-42661. I just patched my DS3617xs.
  12. After some messing around I finally got it working myself with the SATA settings. I was wondering, is it possible for my Unraid to send the shutdown command? Right now it does not listen to that. Am I missing extensions?
  13. Can someone please help me get my Xpenology working...? On Unraid with just one virtual disk and booting as sata from the loader. Tried to create 2 SATA controllers. Using index 00 and map 66 now just to see if that 'works'. It does see my disk but I am not sure how to set the values correctly to get it installed. This is my fdisk: SynologyNAS> fdisk -l Disk /dev/synoboot: 1024 MB, 1073741824 bytes, 2097152 sectors 130 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/synoboot1 * 0,32,33 6,62,56 2048 100351 98304 48.0M 83 Linux /dev/synoboot2 6,62,57 15,205,62 100352 253951 153600 75.0M 83 Linux /dev/synoboot3 15,205,63 130,138,8 253952 2097151 1843200 900M 83 Linux Disk /dev/sda: 200 GB, 214748364800 bytes, 419430400 sectors 26108 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sda1 0,32,33 310,37,47 2048 4982527 4980480 2431M fd Linux raid autodetect /dev/sda2 310,37,48 571,58,63 4982528 9176831 4194304 2048M fd Linux raid autodetect Disk /dev/md0: 2431 MB, 2549940224 bytes, 4980352 sectors 622544 cylinders, 2 heads, 4 sectors/track Units: sectors of 1 * 512 = 512 bytes Disk /dev/md0 doesn't contain a valid partition table Disk /dev/md1: 2047 MB, 2147418112 bytes, 4194176 sectors 524272 cylinders, 2 heads, 4 sectors/track Units: sectors of 1 * 512 = 512 bytes Disk /dev/md1 doesn't contain a valid partition table What can I do to get it working? Some help would be great! Would the 'shutdown' command also work from Unraid? I now have to force stop it. Or is that the Virtio problem others mentioned? Tried to build the 3622xs+ now, but that doesn't see my ethernet. So far only the 3617 works in that regard, but it doesn't install. Now even the 3617 doesn't see the ethernet adapter...
  14. Booting as SATA now for the loader, and using 01 and 6, that boots and installs, but it keeps saying I've changed disks and wants to restore/migrate in an endless loop. This is with 02 and 6: DiskStation> fdisk -l Disk /dev/synoboot: 1024 MB, 1073741824 bytes, 2097152 sectors 130 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/synoboot1 * 0,32,33 6,62,56 2048 100351 98304 48.0M 83 Linux /dev/synoboot2 6,62,57 15,205,62 100352 253951 153600 75.0M 83 Linux /dev/synoboot3 15,205,63 130,138,8 253952 2097151 1843200 900M 83 Linux Disk /dev/sdd: 200 GB, 214748364800 bytes, 419430400 sectors 26108 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Disk /dev/sdd doesn't contain a valid partition table During installation it says data on 4 disks will be erased, but I can't find the right index... And this is my Unraid Qemu setup for disks <disk type='file' device='disk'> <driver name='qemu' type='vmdk' cache='writeback'/> <source file='/mnt/user/domains/dsm/tinycore-redpill.v0.4.6.vmdk' index='2'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/dsm/vdisk2.img' index='1'/> <backingStore/> <target dev='hdd' bus='sata'/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk>
  15. Can someone help me with disk mapping? I now have index 00 and map to 6. I've got one virtual disk in Qemu and the loader as USB. When I do fdisk -l in DSM I get this: DiskStation> fdisk -l Disk /dev/sdd: 200 GB, 214748364800 bytes, 419430400 sectors 26108 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sdd1 0,32,33 310,37,47 2048 4982527 4980480 2431M fd Linux raid autodetect /dev/sdd2 310,37,48 571,58,63 4982528 9176831 4194304 2048M fd Linux raid autodetect Disk /dev/md0: 2431 MB, 2549940224 bytes, 4980352 sectors 622544 cylinders, 2 heads, 4 sectors/track Units: sectors of 1 * 512 = 512 bytes Disk /dev/md0 doesn't contain a valid partition table Disk /dev/md1: 2047 MB, 2147418112 bytes, 4194176 sectors 524272 cylinders, 2 heads, 4 sectors/track Units: sectors of 1 * 512 = 512 bytes Disk /dev/md1 doesn't contain a valid partition table The 200GB /dev/sdd in this case is the right disk. I assumed it would be 00 and 1, but that doesn't work.
×
×
  • Create New...