Jump to content
XPEnology Community

alirz1

Member
 View Profile  See their activity

  • Posts

    195

  • Joined

  • Last visited

 Content Type 

Everything posted by alirz1

  1. alirz1

    DSM 6.2 Loader

    alirz1 replied to jun's topic in Loaders

    Hi all. I want to create a duplicate copy of my usb flash that has the jun”s loader on it.. in the past my usb drive died and I had to create a new one but I guess perhaps due to the vid/pid being different, It started my xpenology box as being new and I had do sort of a recover and restore data type of thing etc… if I create a copy of my current usb drive, should I use its vid/pid of the original drive in the cfg file on the new drive to prevent the loader from initializing the xpenology box if I ever have to swap out the usb loader flash drive?
  2. alirz1
    I have only tried ds3615 for now. I can try building for another model.
  3. alirz1
    ok so i rebuilt the loader after adding the vmxnet3 NIC extension. I also setup the serial port connection so i could see what was going on the with teh VM after the loader's" Booting booting" mesage. So this is where my vm seems to be hanging as i see in the serial console, below are the last few lines. See attached txt file for the rest of the full log: [ 11.066021] NET: Registered protocol family 1 [ 11.067442] pci 0000:00:00.0: Limiting direct PCI/PCI transfers [ 11.069501] pci 0000:00:0f.0: Boot video device [ 11.105811] PCI: CLS 32 bytes, default 64 [ 12.921287] Trying to unpack rootfs image as initramfs... [ 13.718257] Freeing initrd memory: 18992k freed [ 13.763415] redpill: module verification failed: signature and/or required key missing - tainting kernel log.txt
  4. alirz1
    Ok, did that but still have same issue. The vm doesn’t seem to be starting the network interface. I can’t find the nas using synology assistant etc. I don’t have acces to the router so can’t check dhcp leases to confirm if it’s getting an iP or not. is there any other way to verify if the vm is fully booting up with the network interface initialized?
  5. alirz1
    Thanks. But I don't see an option in VMware workstation pro to change nic type. Fr vmxnet to e1000.
  6. alirz1
    ok so after bumping the vm memory to 2GB it seems to have worked, the loader was built. Now when i reboot and choose the SATA boot option from the menu, it just sits at "Decompressin linux, ...Parsing ELF...Done" "Booting Kernel". At this point, i cant seem to find the synology in synology assistant, so im not sure if its picking up an IP or not? Are we able to see any logs via some serial console etc? I know in the past with JUN's loader we wouldnt be able to see anything in the vm console after the kernel booting message.. Could this be due to possible incorrect sataport map etc? i have currently set it to 1 and diskid map to "0A00". Note, as mentioned previosuly, this is all being setup in vmware working station. where, duting the tinycore uild process i have an IP etc..
  7. alirz1
    @pocopico so I have the dumbest question. That GitHub url you mention to build the loader. Does that loader need to be built on the bare metal machine that I would be setting my as my xpenology box? If not then how does the loader include the drivers for the bare metal hardware? Thanks.
  8. alirz1
    Memory as in RAM? I have 1gb and 5gb disk space. If you’re saying it needs 2gb ram minimum, I’ll try that. Thanks.
  9. alirz1
    thanks but getting an iP is not my issue. I get the iP fine and ssh to the vm etc.. it’s just that, after the reloaded script downloads the PAT file and starts unpacking it, my vm complete halts. I have allocated 5gb to disk disk, as this is just for testing, I’m guessing 5gb should be enough space.
  10. alirz1
    Anyone tried setting up a vm in VMware workstation? Should that work/ is supported? im trying to setup a dsm 7.0.1 vm, all is good until redpill downloads the PAT file, starts unpacking it. At that point my vim basically stops responding, ping to vm’s iP stops after a minute or so. Perhaps a kernel panic in the background? I have to rest the vm every time. My sataportmap is set to 1, diskidmap set to 00, also tried 0A00, etc… the vm only has two disks. 0:0 is the red pill vmdk. I added second disk at sata 1:0 for data. any idea why it might be freezing? Thanks
  11. alirz1
    So im giving the latest tinycore a try and trying to setup the 7.0.1 dsm using VMware work station in windows. Its all good, untill tinycore downloads the PAT file and starts to unpack it. But it the whole vm jsut freezes there, like it has kernel panicked in the background or something. i've tried starting clean a few times but it fails at this point always. Any ideas if i could be doing something wrong. Just using the basic steps listed on the tinycore github page.
  12. alirz1
    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.7 update 2 - Loader version and model: Jun's Loader v1.03B 3617 - Using custom extra.lzma: No - Installation type: Bare metal Asrock H370M - Additional comment : I did all pre testing in Vm environments and also on my live production baremetal xpenology, with a separate USb and a separate disk drive to make sure my upgrade from jun 1.02b DSM 6.1.7 for my DS3617 would go smooth to 6.2.3 using 1.03b loader. Everything looked normal for days. So i decided to pull the trigger. I upgrade, box boots up fine, goes into dsm 6.2.3, using 1.0.3 stock loader. However i have strange glitches in my gui, my installed packages are not starting. My data shares are not mounting. I can see that in the storage manager the file shares are there, my HDD and volumes are all good!! Its like none of the services are starting!!!! Every page and control panel item i visit and try to change a config. I get error "operation failed. please login to dsm and try again".I thought maybe it was related to 2-step verification somehow, but doesnt look like it.
  13. alirz1
    so F me. I did all pre testing in Vm environments and also on my live production baremetal xpenology, with a separate USb and a separate disk drive to make sure my upgrade from jun 1.02b DSM 6.1.7 for my DS3617 would go smooth to 6.2.3 using 1.03b loader. Everything looked normal for days. So i decided to pull the trigger. I upgrade, box boots up fine, goes into dsm 6.2.3, using 1.0.3 stock loader. However i have strange glitches in my gui, my installed packages are not starting. My data shares are not mounting. I can see that in the storage manager the file shares are there, my HDD and volumes are all good!! Its like none of the services are starting!!!! Every page and control panel item i visit and try to change a config. I get error "operation failed. please login to dsm and try again".I thought maybe its related to 2-step verificaiotn somehow, but doesnt look like it. I assume its not easy to downgrade back to 6.1.7 and keep all settings/data now? any ideas if i can fix the system in its current state.
  14. alirz1
    While not a direct answer to your question. But why not stick with 3617? It has better package DSM packages support from what i know.I've been using it for years.
  15. alirz1
    Question about LAN drivers. The drivers list/excel sheet on the first page shows both Intel 1219V and 1211 supported for DS3615. Shouldnt both work for DS3617 also? I only have one Nic work for my 3617. Ive seen other posts from other people that have the same board as me(Asrock h370m) complaining about only 1 nic working.
  16. alirz1
    Thanks i was able to make it boot. Had to set the USb boot mode to legacy and not UEFI.
  17. alirz1
    was wondering if you ever got the second nic to work also?
  18. alirz1
    Already on latest Bios. FYI. Bios boot is set to be CSM. Which also allows non UEFI only boot.
  19. alirz1
    No, I burnt stock 1.03b downloaded from MEGA, Juns download link. As a test, I burnt stock 1.02b and box boots fine with one. EDIT. extra.lzma is 1.8MB.
  20. alirz1
    I dont know whats going on. But i burnt stock 1.03b loader on a new USB. Updated the grub config. yet, it looks like the box still kernel panics within seconds after booting from the loader. no network, no keyboard lights etc....again, everything works fine with 1.02 loader.
  21. alirz1
    - Outcome of the update: FAILED - DSM version prior update: DSM 6.1.7 UPDATE 2 - CURRENT Loader version and model: JUN'S LOADER v1.02b - DS3617xs..... Trying upgrade using 1.03b with new dsm kernel file - Using custom extra.lzma: YES - Installation type: BAREMETAL - Asrock H370m - NIC: 1 x Giga PHY Intel® I219V, 1 x GigaLAN Intel® I211AT - Additional comments: HANGS SHORTLY AFTER BOOTING. NO NETWORK ON ANY NIC, NO KEYBOARD LIGHTS Hi All, So i currently have a intel i3-8100 processor, Asrock H370m motherboard based DS3617xs xpenology system running Junls 1.02b loader with DSM 6.1.7-15284 Update 2 and the extra ramdisk(some version from 2018) Trying to get it to upgrade to 6.2.2 using the 1.0.3b loader and the extra kernel for 6.2.x. However looks like that even without the disks connected, the system is kernel panicing shortly after the 1.03b loader boot. While i havent checked via serial console, if its indeed a kernel panic. But looks like that is the case, as shortly after the boot the keyboard lights go off. I get no network connection etc.... NOTE: i have already upgraded my second xpenology box that has an older/different hardware successfully to 6.2.2 using the steps on page 1 of this thread, So im famialir with the requirements. This is the Asrock board and its specs.. No extra add on adapters/controllers etc... Any ideas? Is it known to be not compatible. https://www.asrock.com/MB/Intel/H370M-ITXac/index.asp#Specification
  22. alirz1
    Im actually not using my second nic. Im still on dsm 6.1 for my ds3716 based xpenology, where only one of my nic works. The only time my second Nic worked was when i tested the DS918 build with 6.2 and the 1.03 loader.
  23. alirz1
    Sorry i have no experience using MAC OS so cant help you there.
  24. alirz1
    Hi, Well i was testing the DS918+ and your extra ramdisk, and i see a new driver in that one. My post#160: For ds3617, dsm 6.1.x, Please update Intel(R) PRO/1000 Network Driver" driver to 3.4.0.2-NAPI. The current driver in the loader 3.3.4. Due to this one of my nics does not work. The only place i found the new driver is in the extra ramdisk that @ig-88 compiled for DS918+ to use with Jun's 1.0.3a2 loader and dsm 6.2. I test booted with that loader/extra ramdisk and confirmed that both my nics work with that (Intel AT1219 and 1211). Im still puzzled though, why my NIC works with the 918+ loader and your extra ram file but doesnt work under the dsm 3617.
  25. alirz1
    Perhaps your sata port map config is incorrect? Is this a new install or are you changing boards etc?
×
×
  • Create New...