Jump to content
XPEnology Community

MrHappy

Transition Member
  • Posts

    18
  • Joined

  • Last visited

Recent Profile Visitors

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

MrHappy's Achievements

Newbie

Newbie (1/7)

3

Reputation

  1. Thanks @Peter Suh. This fixed my issue and can now install the latest version (for DS3622xs+ on my Proxmox VM) without any corruption errors.
  2. Added './rploader.sh sataport map now" and tried to install it. Unfortunately it stops at the same points...
  3. Pulling my hair for some days now... And whatever I try I get 'Failed to install DSM. The file is probably corrupted'. I tried to do a new install of DS3622xs+ in a vm on Proxmox using the latest image of pocopico and the following steps: ./rploader.sh update ./rploader.sh fullupgrade After that I went to the webui and clicked the following items:: clean loader full upgrade loader build 3622xsp 7.2.0-64570 That finished successfully and rebooted. After the reboot it detected a new install and asked for which DSM (of the site or downloaded PAT). I tried several all failing with 'Failed to install DSM. The file is probably corrupted'. Various PAT's stopped at different points: From the site directly: failed on 8%. Manually downloaded 64570: failed on 56% Manually downloaded U1: failed on 57% Finally downloaded the PAT referenced from DS3622xs+ config.json (Link to the pat from Synology) SHA256 of downloaded file: 8c6bc56862017881d46b02b164d8ea0094922e5c44c937ecc8504c3c009e8dd4 Which is identical to the sha256 in the config.json What am I missing?
  4. Wouldn´'t the benefit of using a hypervisor be to not be dependent on specific hardware? But I'm running a Dell PowerEdge R720 with a couple of Intel Xeon E5-2697v2 2.7GHz...
  5. I have DS3622xs+ running, but I would like to use the additional features DVA brings with Surveillance Station... Using the same config does not work... (Also updating my DS3622xs+ to the latest DSM fails, so there's something else wrong also)
  6. I'm also trying to install DVA3221 on Proxmox. I'm using the web ui. Everything seems to go fine until I reboot. Then it gives a kernel panic extracting the initramfs, unexpected eof... The same error appears on DVA3219. DVA1622 installs, but does not detect my nic (virtio). Has anyone got DVA3221 installed on Proxmox and could you share your (vm-)config?
  7. I used 0.9.4.9b today to upgrade my 3622XS+ vm to 7.2. The vm runs on Proxmox and worked fine on 7.1U5. The boot disk is on sata, the storage-disks are on virtio scsi. After booting the last few lines showed: [ 94.678707] scsi 1:0:0:1: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5 [ 94.679627] sdh: sdh1 sdh2 sdh3 [ 94.680282] sd 1:0:0:2: [sdh] Attached SCSI disk [ 94.682593] want_idx 1 index 8. delay and reget [ 95.684099] want_idx 1 index 8 ..... [ 108.704116] want_idx 1 index 8. delay and reget [ 109.705114] want_idx 1 index 8 [ 109.706096] sd 1:0:0:1: Attached scsi generic sg8 type 0 [ 109.706247] sd 1:0:0:1: [sdi] 67108864 512-byte logical blocks: (34.4 GB/32.0 GiB) [ 109.706624] sd 1:0:0:1: [sdi] Write Protect is off [ 109.706626] sd 1:0:0:1: [sdi] Mode Sense: 63 00 00 08 [ 109.706716] sd 1:0:0:1: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 109.715812] sdi: sdi1 sdi2 sdi3 [ 109.717431] sd 1:0:0:1: [sdi] Attached SCSI disk [ 109.749675] udevd[4288]: failed to send result of seq 3047 to main daemon: Connection refused After a while the next message appears [ 140.441970] ext2: synoboot2 mounted, process=mantool [ 140.444151] vfat: synoboot2 mounted, process=mantool [ 140.452989] FAT-fs (synoboot2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [ 140.456348] synoboot2 unmounted, process=mantool This makes me think the OS sees the disks, but Syno says 'No drives detected in DS3622XS+'. Is this because the RedPill gui does not let me add virtio-drivers or is there something else the matter?
  8. And if you try DS1621xsp?
  9. SATA gives me errors about unsupported disks... What config do I need to use for drives (on a vm on Proxmox) to have them discovered and not giving errors?
  10. 0.9.4.6 didn't work either. I created a new vm and on that one it didn't detect the disks either. After changing the scsi to sata they were detected. Is scsi no longer supported?
  11. I have a vm on proxmox. Works fine with 7.1 (ds3622xsp) and an old tcrp. After updating dsm doesn't find my nic (although tcrp-friend does) and no disks are found.
  12. It doesn't show anything after that. If it all works you should be able to access the webpage (http://<ip-of-vm>:5000) after a short time (couple of minutes I believe)
  13. The method described by @docop1 worked for me (for DS3622xs+, DS918+ failed to connect to network somehow) on Proxmox.
×
×
  • Create New...