• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About romansoft

  • Rank

Recent Profile Visitors

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

  1. I suspect that, in my case, the problem's root cause is some dynamic parameter which may be changing between boots (Xpenology and/or Proxmox reboots), probably due to some recent change in Proxmox, and which finally lead to DSM "detecting" that the hw has changed (but then I cannot explain why a recovered backup does work; it shouldn't either). In your experience, which kind of hw changes do you think DSM could be detecting? See the (Proxmox) config I previosly posted (1st post in this thread). Re @haydibe's config, it seems simplest than mine but he took a different ap
  2. Hi all, DSM gets "continually broken" (I mean, I fix it but then it gets broken again) after a Proxmox 6 to 7 upgrade. Jun's loader shows (serial terminal): "lz failed 9 alloc failed Cannot load /boot/zImage" But please, let me first explain all details and read until the end because the situation is very strange... I'm using JUN'S LOADER v1.03b - DS3617xs in a Proxmox VM (on HP Gen8), with DSM 6.2.3-25426. I've been using this config for months without any problem on Proxmox **6.x** (this seems relevant). The other day I decided to upgr
  3. @IG-88 I didn't find any useful info in provided link but thank you anyway for trying to help. Finally, after some research, I managed to get a similar config *working* (it was a little bit tricky). 1/ I guessed the kernel panic was due to some USB driver problem (related to my USB stick being loaded) so I simply changed the synoboot device from the USB stick to an emulated USB-disk (qemu storage disk). 2/ Also, in order to install/upgrade DSM (avoiding the infamous "error 13"), I had to set proper vid/pid in synoboot.img (grub.cfg), which in case of qemu storage
  4. Hi, I booted from loader 1.03b-ds3617xs, entered Syno's web-GUI and chose to install latest DSM (6.2.2-24922-4). Then rebooted and now I always get a Kernel panic when booting. Proxmox's host is Ivy Bridge: CPU model name : Intel(R) Xeon(R) CPU E3-1265L V2 @ 2.50GHz This is my Proxmox's config, which basically includes: e1000e hack Since Proxmox may only boot from USB if using UEFI and 1.03b doesn't support UEFI, I selected Seabios but did another hack: booting from CD and then chain-loads to USB. 1.03b loader is embeded in a phys
  5. I found a solution which permits me to boot my USB stick Simply I created a CD image (.iso) with plop ( with the sole funtion of booting USB (similar to "chainloading" with grub2). I've attached the .iso here (just in case somebody needs it; happens that it also will work -not tested, though- even if your BIOS doesn't support USB boot at all -old BIOSes-). Now simply add a CDROM device to your Proxmox VM and select this .iso as image. Finally, configure: Options -> Boot order -> CDROM. You are
  6. Loader version and type: 1.03b / 3617XS DSM version in use (including critical update): None (kernel crash when booting from loader so I cannot install DSM) Using custom modules/ramdisk? If yes which one?: None Hardware details: Proxmox on Hp Gen8. Problem: 1.03b loader fails to boot (kernel crash) when OVMF (UEFI) bios is selected. It works only when SeaBIOS is selected (which is Proxmox's default but it lacks features). Detailed info & logs in the following post:
  7. I've been iddle some time but I'm coming back with some responses I discovered by researching this a little bit. 1/ In order to have a *full* serial console, you need to uncomment/comment these lines in grub.cfg: set extra_args_3617='earlycon=uart8250,io,0x3f8,115200n8 earlyprintk loglevel=15' #set extra_args_3617='' Then you can observe the complete boot process with a simple "qm terminal <vmid>". 2/ When doing so, I discovered what was happening: [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tain
  8. Thanks. Basically the difference with my setup is that your bootdisk is sata0 instead of usb. It sounds weird that loader may not work propperly if run from usb? Or maybe is known behaviour for 1.03b? Another point: simply booting 1.02b in proxmox, showed menu in serial console. But that doesn't happen with 1.03b. Shouldn't be the same?!? Cheers, -r
  9. My VM (Proxmox)'s disks are already SATA (physical disks being passed-thru). Boot/loader is USB-stick. Could you paste your current config (or screenshot)? Thx.
  10. So are you confirming Proxmox's serial console works for you with 1.03b? (it didn't work for me). My VM already has serial console defined (so your 1st cmd isn't necessary). Could you run a "qm terminal 101" and tell me if that works for you? I think it should be equivalent to socat cmd. For me, it doesn't work either "qm terminal" nor socat, with 1.03b (it works if I boot with 1.02b, as I already commented in my post). Cheers, -r
  11. Hi, I have DSM 6.1 (1.02b loader) on HP Gen8. I'm using an usb stick (with synoboot.img burnt), which can work both on baremetal and Proxmox so I can switch between starting DSM on HP Gen8 without any virtualization layer, or starting DSM from Proxmox (running over HP Gen8). I'd recommend this environment so if your proxmox fails, you can pick up your phisical disks (I'm currently passing them thru to proxmox) and the usb stick and start directly in the server (even another new server!). What's the procedure to update to DSM 6.2? I thought that new 1.03b loader would su
  12. And you're probably right. This is specially true for freenas/zfs (where low-level optimizations are done by SO; hypervisor may affect). In case of xpenology, well, it's a simple Linux with software raid (then lvm + btrfs). If you monitor (smart) disks health from outside VM, you're done. Cheers, -r Enviado desde mi iPhone utilizando Tapatalk
  13. Please, open a new thread for installation/upgrade issues, This thread was supposed to be related to *PERFORMANCE* === Btw, quick responses/ideas: 1/ you can import Jun's ovf first on Vmware Workstation (a lot more flexible than ESXi) on your laptop, play on that (change VM compatibility, etc), and finally "upload" to esxi directly from vmware wks (there's an option for that). This way you will get .vmdk only file "translated" to vmdk + flat-vmdk files (which ESXi 6.5 uses). 2/ For migration (DSM 6.0.2 -> 6.1), once you have full DSM 6.1 vm uploaded to ESXi 6.5, then pick up 1st d
  14. Hi, I have a HP Gen8 Microserver with upgraded CPU&RAM (Xeon + 16GB RAM), running ESXi 6.5 so I installed Xpenology/DSM 6.1 (yes, new version) in a VM (with Jun's 1.02a loader). I've attached 3 WD Red disks, in *AHCI* mode, and I've configured them in the VM as RDM disks (I don't have extra sata card in order to use VTd/Passthrough). After solving a first huge performance problem (horrible 2 MB/s speed!!!), by disabling Vmware AHCI driver and enabling legacy one (full story here: ... wahci.html), these are the current speeds I'm getting *
  15. Bingo! Thanks a lot, billat29. Cheers, -r