Recommended Posts

Probably I made all I want.

I've installed ESXi 5.5 on HP Microserver Gen7 on my 40 Gb SSD. After that I create virtualmachine with XPEnology using converted gnoboot-alpha10.5-ext2.img into VMDK (converted VMDK you can download using next link http://yadi.sk/d/oumBLqLIMvzAF).

I've created VM with next preferences:

CPU - 2

Memory - 4Gb

SCSI Controller 0 - LSI Logic Parallel

Network adapter - VM Network (E1000)

Hard Disk 1 - 32 Mb (Converted IMG to VMDK) - IDE (0:0)

Hard Disk 2 - 5 Gb (For installing XPEnology) - SCSI (0:0)

After that I started VM, installed XPEnology and shutdown it.

The most interesting part :grin:

If you want to have good enough speed of your NAS disks we should try Mapped RAW Lun type connection if Disks (RDM).

I've got 3x2Tb WD Red disks and we will use them as storage disks in XPEnology. Before using them into RDM lets delete all partitions from disks.

To made this we should list all connected disks to system using this command on ESXi server via ssh:

ls -l /vmfs/devices/disks/

Finally we have got id's of disks, that will be used in RAID on XPEnology. Lets delete all partitions on disks (for example):

fdisk /vmfs/devices/disks/t10.ATA_____Hitachi_HDS721010CLA332_______________________JP2950HZ0E47HC

Press 'O' to create new partition table and 'W" to apply changes.

Repeat this article on another disks. Do not touch system disk if you dont want to have some troubles :wink:

Lets move to directory with VM, which will be connected with RDM disks. In this direcrory will be created VMDK files of these disks.

cd /vmfs/volumes//

In step before we found id's of disks that will be used in RDM (t10.ATA_____Hitachi_HDS721010CLA332_______________________JP2950HZ0E47HC etc.)

Let's create RDM VMDK file:

vmkfstools -r /vmfs/devices/disks/ NAS1.vmdk

for example:

vmkfstools -r /vmfs/devices/disks/t10.ATA_____Hitachi_HDS721010CLA332_______________________JP2950HZ0E47HC NAS1.vmdk

In VmWare client add disks to virtual machine as an existent virtual disk.

In RAID-0 of 2 disks I've got over 105 Mbps in gigabyte link. Now I'm building RAID-5 with 3x2Tb disks. About results I will get updated information.

 

Information about RDM was found here: http://chmv.allnetic.com/article/vmware ... a-kak-rdm/ (Russian Language :grin: ).

Thanks for your attention.

Link to post
Share on other sites
Dark Alex,

 

I don't know How I do.

 

Can you explain to me please ?

 

Tkan you

Jérôme

 

You should be able to set that in your BIOS settings.

BIOS Setup -> Boot options and search for something like Legacy Boot or MBR instead of EFI

 

 

Hi,

 

Thank you, the USB key boots now !

 

But I have this message now: "fixing recursive fault but reboot is needed"

What do I do ?

 

With synoboot, it's working. I can install DSM 4.3 or 5.0 !

 

Jerome

Link to post
Share on other sites
Hi,

 

Are you using ESXi5? are you able to see SMART status in your DSM?

 

I'm using ESXi 5.5. I'm able to run and schedule SMART tests for the disks from the DSM web GUI. The disks' serial numbers also display within DSM. However, the temperature is shown as 0° C / 32° F what leads some nasty scemd.log entries every two seconds. My solution was just to delete scemd.log which prevents logging until the next reboot (or probably log rotation...). I also might just link scemd.log to /dev/null.

 

bye,

Darky

 

I were only able to manual run smartctl under ssh. Could you please post your RDM setting and SCSI adaptor as well as SCSI address for our reference, please?

Thanks.

Link to post
Share on other sites
I can't seem to get PLEX to work properly.

Any of you guys have the same prob?

 

Cheers and thanks!

Hello!

What kind of problems with Plex on XPEnology are you have?

I'm using latest version of XPEnology DS3612xs on HP MicroServer G7 - all right.

Thanks!

Link to post
Share on other sites
Hi,

 

Are you using ESXi5? are you able to see SMART status in your DSM?

 

I'm using ESXi 5.5. I'm able to run and schedule SMART tests for the disks from the DSM web GUI. The disks' serial numbers also display within DSM. However, the temperature is shown as 0° C / 32° F what leads some nasty scemd.log entries every two seconds. My solution was just to delete scemd.log which prevents logging until the next reboot (or probably log rotation...). I also might just link scemd.log to /dev/null.

 

bye,

Darky

 

Hiya

 

Sorry to hijack the thread but where is this log file?

 

Got the same problem on my ESXi 5.5 installed with DSM 5.0 update 2.

More than that when I reboot I get a warming about the hard drive temps.

Figured I can find this out and maintain it from ESXi but would like to turn off the log dumping in DSM

 

Thanks

Link to post
Share on other sites

Hi,

 

I were only able to manual run smartctl under ssh. Could you please post your RDM setting and SCSI adaptor as well as SCSI address for our reference, please?

Thanks.

 

 

I'll just dump the .vmx file for you (fyi: the ISO-image belongs to the plpt boot loader which then boots a mapped USB-thumb-drive with gnoboot. I did this just for testing some stuff usually I go with the gnoboot vmdk approach).

 

I also deleted my CPU-IDs from the config. The Virtual SCSI-HBA is the LSI SAS (see config for details), the Physical SAS-HBA is the LSI 9240-8i with stock ROM including Raid5-Support, although no Raids are defined.

 

.encoding = "UTF-8"
config.version = "8"
virtualHW.version = "8"
nvram = "DARK-NAS2.nvram"
pciBridge0.present = "TRUE"
svga.present = "TRUE"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
vmci0.present = "TRUE"
hpet0.present = "TRUE"
displayName = "DARK-NAS2"
extendedConfigFile = "DARK-NAS2.vmxf"
virtualHW.productCompatibility = "hosted"
floppy0.present = "FALSE"
numvcpus = "8"
cpuid.coresPerSocket = "8"
memSize = "4096"
sched.cpu.units = "mhz"
powerType.powerOff = "soft"
powerType.suspend = "hard"
powerType.reset = "soft"
ethernet0.virtualDev = "e1000"
ethernet0.networkName = "VM Network"
ethernet0.addressType = "generated"
ethernet0.present = "TRUE"
guestOS = "ubuntu-64"
toolScripts.afterPowerOn = "TRUE"
toolScripts.afterResume = "TRUE"
toolScripts.beforeSuspend = "TRUE"
toolScripts.beforePowerOff = "TRUE"
uuid.bios = "56 4d a2 c8 42 80 fb 23-7a 78 f3 b3 38 ad d4 20"
uuid.location = "56 4d a2 c8 42 80 fb 23-7a 78 f3 b3 38 ad d4 20"
vc.uuid = "52 54 05 73 1b ad 11 cc-8e 2b cb d2 c3 37 a0 57"
chipset.onlineStandby = "FALSE"
sched.cpu.min = "0"
sched.cpu.shares = "normal"
sched.mem.min = "0"
sched.mem.minSize = "0"
sched.mem.shares = "normal"
sched.swap.derivedName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/DARK-NAS2/DARK-NAS2-8686319e.vswp"
replay.supported = "FALSE"
replay.filename = ""
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
ethernet0.pciSlotNumber = "32"
vmci0.pciSlotNumber = "33"
ethernet0.generatedAddress = "00:0c:29:ad:d4:20"
ethernet0.generatedAddressOffset = "0"
vmci0.id = "950916128"
hostCPUID.0 = ""
hostCPUID.1 = ""
hostCPUID.80000001 = ""
guestCPUID.0 = ""
guestCPUID.1 = ""
guestCPUID.80000001 = ""
userCPUID.0 = ""
userCPUID.1 = ""
userCPUID.80000001 = ""
evcCompatibilityMode = "FALSE"
vmotion.checkpointFBSize = "4194304"
cleanShutdown = "FALSE"
softPowerOff = "FALSE"
tools.remindInstall = "TRUE"
tools.syncTime = "FALSE"
scsi0.virtualDev = "lsisas1068"
scsi0.present = "TRUE"
scsi0:0.deviceType = "scsi-hardDisk"
scsi0:0.fileName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/RDM/SAS-Disk00.vmdk"
scsi0:0.mode = "independent-persistent"
scsi0:0.present = "TRUE"
scsi0:1.deviceType = "scsi-hardDisk"
scsi0:1.fileName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/RDM/SAS-Disk01.vmdk"
scsi0:1.mode = "independent-persistent"
scsi0:1.present = "TRUE"
scsi0:2.deviceType = "scsi-hardDisk"
scsi0:2.fileName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/RDM/SAS-Disk02.vmdk"
scsi0:2.mode = "independent-persistent"
scsi0:2.present = "TRUE"
scsi0:3.deviceType = "scsi-hardDisk"
scsi0:3.fileName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/RDM/SAS-Disk03.vmdk"
scsi0:3.mode = "independent-persistent"
scsi0:3.present = "TRUE"
scsi0:4.deviceType = "scsi-hardDisk"
scsi0:4.fileName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/RDM/SAS-Disk04.vmdk"
scsi0:4.mode = "independent-persistent"
scsi0:4.present = "TRUE"
scsi0:5.deviceType = "scsi-hardDisk"
scsi0:5.fileName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/RDM/SAS-Disk05.vmdk"
scsi0:5.mode = "independent-persistent"
scsi0:5.present = "TRUE"
scsi0:0.redo = ""
scsi0:1.redo = ""
scsi0:2.redo = ""
scsi0:3.redo = ""
scsi0:4.redo = ""
scsi0:5.redo = ""
scsi0.pciSlotNumber = "160"
scsi0.sasWWID = "50 05 05 68 42 80 fb 20"
usb.present = "TRUE"
ehci.present = "TRUE"
usb.autoConnect.device0 = "path:1/0/1/1 version:2"
usb.pciSlotNumber = "34"
ehci.pciSlotNumber = "35"
usb:1.speed = "2"
usb:1.present = "TRUE"
usb:1.deviceType = "hub"
usb:1.port = "1"
usb:1.parent = "-1"
ide0:0.deviceType = "cdrom-image"
ide0:0.fileName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/ISOs/plpbt.iso"
ide0:0.present = "TRUE"
usb:0.present = "TRUE"
usb:0.deviceType = "hid"
usb:0.port = "0"
usb:0.parent = "-1"
ide0:0.allowGuestConnectionControl = "TRUE"
toolsInstallManager.updateCounter = "1"

 

RDMP vmdk (used the -z switch when creating the RDMP)

# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=28a0f813
parentCID=ffffffff
isNativeSnapshot="no"
createType="vmfsPassthroughRawDeviceMap"

# Extent description
RW 7814037168 VMFSRDM "SAS-Disk00-rdmp.vmdk"

# The Disk Data Base
#DDB

ddb.adapterType = "lsilogic"
ddb.geometry.cylinders = "486401"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.longContentID = "323bbdda29c2ac0d5d1a90a828a0f813"
ddb.toolsVersion = "0"
ddb.uuid = "60 00 C2 9b e9 58 e5 17-a3 04 a0 93 23 fa 6f e8"
ddb.virtualHWVersion = "10"

 

bye,

Darky

Link to post
Share on other sites
I can't seem to get PLEX to work properly.

Any of you guys have the same prob?

 

Cheers and thanks!

Hello!

What kind of problems with Plex on XPEnology are you have?

I'm using latest version of XPEnology DS3612xs on HP MicroServer G7 - all right.

Thanks!

 

Hi Alex 007.

 

DS413 - Plex WORKING

Trantor 4.3 - Plex WORKING

gnuBOOT 10.5 - Plex NOT working, I Can't find any media files in my folders which contains all my movies/tv series.

 

Maybe I have to open some new ports on my router even if I'm only on LAN?

 

Greetings!

Link to post
Share on other sites

Some more info on the SMART temperature Issue. Probably it's a controller firmware thing...

 

If I enter the mangement BIOS (latest version btw) of the RAID-Controller, the drives' temperatures are also listed as 0°. Also the LSI cmd-line-tool storcli lists the temperature as 0°. Thus the DSM will also read the temp as 0°. smartctl probably uses a different way to access the temperature value, as it is displayed correctly at 38 to 40° depending on the disk load etc. Maybe there is a SAS way to dtermine the temp and another, more like SATA way to dertmine the temp.

 

I will mail the LSI support why the temp reading is 0°

 

I will also collect some old SAS drives @work and test them if they show a temperature reading.

 

bye

Darky

Link to post
Share on other sites
Hi gnoboot,

 

Thank you very much!! I have tried to use the gnoboot-alpha 10.4, I can install my TV usb...

 

[  548.508112] usb 2-1: new high-speed USB device number 4 using ehci_hcd
[  548.908546] dvb-usb: found a 'Conexant DMB-TH Stick' in warm state.
[  549.249405] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[  549.249602] DVB: registering new adapter (Conexant DMB-TH Stick)
[  551.459336] usb 2-1: DVB: registering adapter 0 frontend 0 (Legend Silicon LGS8913/LGS8GXX DMB-TH)...
[  551.459576] MXL5005S: Attached at address 0x63
[  551.460018] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:13.2/usb2/2-1/input/input4
[  551.460025] dvb-usb: schedule remote query interval to 100 msecs.
[  551.460244] dvb-usb: Conexant DMB-TH Stick successfully initialized and connected.
[  551.461146] usbcore: registered new interface driver dvb_usb_cxusb

 

BTW, I have clicked the ADs to support development. :mrgreen:

 

Hi, I have just updated my DSM from 4.3-3810 to 5.0-4438 using gnoboot-alpha 10.5 in my N54l . I then plugged in my Contex DTV-01 USB stick (with "LGS8GL5" chipset) but the device manager can't detect the USB stick (It can be detected while I was using DSM 4.3-3810). Can anyone help me with this issue?

Link to post
Share on other sites
Hi gnoboot,

 

Thank you very much!! I have tried to use the gnoboot-alpha 10.4, I can install my TV usb...

 

[  548.508112] usb 2-1: new high-speed USB device number 4 using ehci_hcd
[  548.908546] dvb-usb: found a 'Conexant DMB-TH Stick' in warm state.
[  549.249405] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[  549.249602] DVB: registering new adapter (Conexant DMB-TH Stick)
[  551.459336] usb 2-1: DVB: registering adapter 0 frontend 0 (Legend Silicon LGS8913/LGS8GXX DMB-TH)...
[  551.459576] MXL5005S: Attached at address 0x63
[  551.460018] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:13.2/usb2/2-1/input/input4
[  551.460025] dvb-usb: schedule remote query interval to 100 msecs.
[  551.460244] dvb-usb: Conexant DMB-TH Stick successfully initialized and connected.
[  551.461146] usbcore: registered new interface driver dvb_usb_cxusb

 

BTW, I have clicked the ADs to support development. :mrgreen:

 

Hi, I have just updated my DSM from 4.3-3810 to 5.0-4438 using gnoboot-alpha 10.5 in my N54l . I then plugged in my Contex DTV-01 USB stick (with "LGS8GL5" chipset) but the device manager can't detect the USB stick (It can be detected while I was using DSM 4.3-3810). Can anyone help me with this issue?

 

How did you go about upgrading your N54L and were you able to retain the data?

 

I am guessing that I would need to get the new DSM 5 with the 10.5 gnoboot (been reading all kinds of nonsense about passwords and difficulty in obtaining it) and shut down my N54L and take out the USB flash it with the new DSM 5 with gnoboot 10.5 and then turn it back up and finish the upgrade by pointing the assistant to the new pat file or whatever?

 

I was all gungho on getting my synology box upgraded, but after just readng Plex isnt working, that is not going to work for me lol.

Link to post
Share on other sites

I usually try to handle my own problems but this has been kicking my butt all day.

 

I've finally decided to update my box but now I can't even load the the dang .pat file. Synology Assistant sees the NAS, and I'm able to ping it but when I try to reach the Web Assistant, it is telling me that connection failed and I need to check my settings. I've opened up the firewall and nothing. I've used the 10.3 custom esxi and 10.5 and both are giving me the same issue. My setup is below

 

4 Cores

4GB RAM

10.3/10.5 VDMK with 8GB second drive (VM Paravirtual)

LSI 1068E IT Mode passthrough with 4 drives attached.

 

I've searched and came up empty. I was wondering if anyone has ran into this issue and if you have, what did you do to fix it.

Link to post
Share on other sites

Thanks for your information, but I cannot get it to work, most likely that I was using Intel ICH SATA instead of your LSI.

 

Hi,

 

I were only able to manual run smartctl under ssh. Could you please post your RDM setting and SCSI adaptor as well as SCSI address for our reference, please?

Thanks.

 

 

I'll just dump the .vmx file for you (fyi: the ISO-image belongs to the plpt boot loader which then boots a mapped USB-thumb-drive with gnoboot. I did this just for testing some stuff usually I go with the gnoboot vmdk approach).

 

I also deleted my CPU-IDs from the config. The Virtual SCSI-HBA is the LSI SAS (see config for details), the Physical SAS-HBA is the LSI 9240-8i with stock ROM including Raid5-Support, although no Raids are defined.

 

.encoding = "UTF-8"
config.version = "8"
virtualHW.version = "8"
nvram = "DARK-NAS2.nvram"
pciBridge0.present = "TRUE"
svga.present = "TRUE"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
vmci0.present = "TRUE"
hpet0.present = "TRUE"
displayName = "DARK-NAS2"
extendedConfigFile = "DARK-NAS2.vmxf"
virtualHW.productCompatibility = "hosted"
floppy0.present = "FALSE"
numvcpus = "8"
cpuid.coresPerSocket = "8"
memSize = "4096"
sched.cpu.units = "mhz"
powerType.powerOff = "soft"
powerType.suspend = "hard"
powerType.reset = "soft"
ethernet0.virtualDev = "e1000"
ethernet0.networkName = "VM Network"
ethernet0.addressType = "generated"
ethernet0.present = "TRUE"
guestOS = "ubuntu-64"
toolScripts.afterPowerOn = "TRUE"
toolScripts.afterResume = "TRUE"
toolScripts.beforeSuspend = "TRUE"
toolScripts.beforePowerOff = "TRUE"
uuid.bios = "56 4d a2 c8 42 80 fb 23-7a 78 f3 b3 38 ad d4 20"
uuid.location = "56 4d a2 c8 42 80 fb 23-7a 78 f3 b3 38 ad d4 20"
vc.uuid = "52 54 05 73 1b ad 11 cc-8e 2b cb d2 c3 37 a0 57"
chipset.onlineStandby = "FALSE"
sched.cpu.min = "0"
sched.cpu.shares = "normal"
sched.mem.min = "0"
sched.mem.minSize = "0"
sched.mem.shares = "normal"
sched.swap.derivedName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/DARK-NAS2/DARK-NAS2-8686319e.vswp"
replay.supported = "FALSE"
replay.filename = ""
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
ethernet0.pciSlotNumber = "32"
vmci0.pciSlotNumber = "33"
ethernet0.generatedAddress = "00:0c:29:ad:d4:20"
ethernet0.generatedAddressOffset = "0"
vmci0.id = "950916128"
hostCPUID.0 = ""
hostCPUID.1 = ""
hostCPUID.80000001 = ""
guestCPUID.0 = ""
guestCPUID.1 = ""
guestCPUID.80000001 = ""
userCPUID.0 = ""
userCPUID.1 = ""
userCPUID.80000001 = ""
evcCompatibilityMode = "FALSE"
vmotion.checkpointFBSize = "4194304"
cleanShutdown = "FALSE"
softPowerOff = "FALSE"
tools.remindInstall = "TRUE"
tools.syncTime = "FALSE"
scsi0.virtualDev = "lsisas1068"
scsi0.present = "TRUE"
scsi0:0.deviceType = "scsi-hardDisk"
scsi0:0.fileName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/RDM/SAS-Disk00.vmdk"
scsi0:0.mode = "independent-persistent"
scsi0:0.present = "TRUE"
scsi0:1.deviceType = "scsi-hardDisk"
scsi0:1.fileName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/RDM/SAS-Disk01.vmdk"
scsi0:1.mode = "independent-persistent"
scsi0:1.present = "TRUE"
scsi0:2.deviceType = "scsi-hardDisk"
scsi0:2.fileName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/RDM/SAS-Disk02.vmdk"
scsi0:2.mode = "independent-persistent"
scsi0:2.present = "TRUE"
scsi0:3.deviceType = "scsi-hardDisk"
scsi0:3.fileName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/RDM/SAS-Disk03.vmdk"
scsi0:3.mode = "independent-persistent"
scsi0:3.present = "TRUE"
scsi0:4.deviceType = "scsi-hardDisk"
scsi0:4.fileName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/RDM/SAS-Disk04.vmdk"
scsi0:4.mode = "independent-persistent"
scsi0:4.present = "TRUE"
scsi0:5.deviceType = "scsi-hardDisk"
scsi0:5.fileName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/RDM/SAS-Disk05.vmdk"
scsi0:5.mode = "independent-persistent"
scsi0:5.present = "TRUE"
scsi0:0.redo = ""
scsi0:1.redo = ""
scsi0:2.redo = ""
scsi0:3.redo = ""
scsi0:4.redo = ""
scsi0:5.redo = ""
scsi0.pciSlotNumber = "160"
scsi0.sasWWID = "50 05 05 68 42 80 fb 20"
usb.present = "TRUE"
ehci.present = "TRUE"
usb.autoConnect.device0 = "path:1/0/1/1 version:2"
usb.pciSlotNumber = "34"
ehci.pciSlotNumber = "35"
usb:1.speed = "2"
usb:1.present = "TRUE"
usb:1.deviceType = "hub"
usb:1.port = "1"
usb:1.parent = "-1"
ide0:0.deviceType = "cdrom-image"
ide0:0.fileName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/ISOs/plpbt.iso"
ide0:0.present = "TRUE"
usb:0.present = "TRUE"
usb:0.deviceType = "hid"
usb:0.port = "0"
usb:0.parent = "-1"
ide0:0.allowGuestConnectionControl = "TRUE"
toolsInstallManager.updateCounter = "1"

 

RDMP vmdk (used the -z switch when creating the RDMP)

# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=28a0f813
parentCID=ffffffff
isNativeSnapshot="no"
createType="vmfsPassthroughRawDeviceMap"

# Extent description
RW 7814037168 VMFSRDM "SAS-Disk00-rdmp.vmdk"

# The Disk Data Base
#DDB

ddb.adapterType = "lsilogic"
ddb.geometry.cylinders = "486401"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.longContentID = "323bbdda29c2ac0d5d1a90a828a0f813"
ddb.toolsVersion = "0"
ddb.uuid = "60 00 C2 9b e9 58 e5 17-a3 04 a0 93 23 fa 6f e8"
ddb.virtualHWVersion = "10"

 

bye,

Darky

Link to post
Share on other sites

Hi,

i have readden on the top of the topic, what if i updated dsm 4.3 to dsm 5 with gnoboot, it will erase data.

 

it just with dsm 5 beta or dsm 5 in all case ?

 

i have trantor 4.3 beta 6 and i want to upgrade to dsm 5 (for many driver reason)

 

can someone confirm, data erase it's only when migrate in beta ?

 

thx :--)

Link to post
Share on other sites

Hi, I'm trying to het this to work on an relatively old HP DC7900 (Intel Core2duo) but I can't get the usb stick to boot. It's keep getting stuck before loading grub. Just a flashing cursor on the top left of the screen.

I created the usb stick using dd with the ext2 img file. The stick does boot in a laptop (although it strands in a kernel error, but grub works) , so i guess the flashing of the usb stick was succesfull, booting other usb sticks (live ubuntu for example) on the same pc is no problem at all.

 

Any ideas what i can do to make this usb stick bootable?

Link to post
Share on other sites
Hi, I'm trying to het this to work on an relatively old HP DC7900 (Intel Core2duo) but I can't get the usb stick to boot. It's keep getting stuck before loading grub. Just a flashing cursor on the top left of the screen.

I created the usb stick using dd with the ext2 img file. The stick does boot in a laptop (although it strands in a kernel error, but grub works) , so i guess the flashing of the usb stick was succesfull, booting other usb sticks (live ubuntu for example) on the same pc is no problem at all.

 

Any ideas what i can do to make this usb stick bootable?

 

try win32diskimager for windows

insert into another port

try a different flash drive

Link to post
Share on other sites
Hi gnoboot,

 

Thank you very much!! I have tried to use the gnoboot-alpha 10.4, I can install my TV usb...

 

[  548.508112] usb 2-1: new high-speed USB device number 4 using ehci_hcd
[  548.908546] dvb-usb: found a 'Conexant DMB-TH Stick' in warm state.
[  549.249405] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[  549.249602] DVB: registering new adapter (Conexant DMB-TH Stick)
[  551.459336] usb 2-1: DVB: registering adapter 0 frontend 0 (Legend Silicon LGS8913/LGS8GXX DMB-TH)...
[  551.459576] MXL5005S: Attached at address 0x63
[  551.460018] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:13.2/usb2/2-1/input/input4
[  551.460025] dvb-usb: schedule remote query interval to 100 msecs.
[  551.460244] dvb-usb: Conexant DMB-TH Stick successfully initialized and connected.
[  551.461146] usbcore: registered new interface driver dvb_usb_cxusb

 

BTW, I have clicked the ADs to support development. :mrgreen:

 

Hi, I have just updated my DSM from 4.3-3810 to 5.0-4438 using gnoboot-alpha 10.5 in my N54l . I then plugged in my Contex DTV-01 USB stick (with "LGS8GL5" chipset) but the device manager can't detect the USB stick (It can be detected while I was using DSM 4.3-3810). Can anyone help me with this issue?

 

How did you go about upgrading your N54L and were you able to retain the data?

 

I am guessing that I would need to get the new DSM 5 with the 10.5 gnoboot (been reading all kinds of nonsense about passwords and difficulty in obtaining it) and shut down my N54L and take out the USB flash it with the new DSM 5 with gnoboot 10.5 and then turn it back up and finish the upgrade by pointing the assistant to the new pat file or whatever?

 

I was all gungho on getting my synology box upgraded, but after just readng Plex isnt working, that is not going to work for me lol.

 

I just followed the steps from: http://cyanlabs.co.uk/news/install-xpen ... mment-4259 to do the upgrade.

 

All data is remain as 4.3, everything is running smooth except the Contex DTV-01 USB stick which cannot be detected even if I am now using gnoboot 10.4 version for boot up of DSM 5.0-4458 Update 2.

As I said, the Contex DTV-01 USB stick can be detected and was working fine when I was using the DSM 4.3-3810 (I was using gnoboot 3 as boot up when I was using DSM 4.3-3810)

 

BTW, can anyone tell me the steps to manually install the driver for this USB stick Contex DTV-01 USB stick for gnoboot 10.4/10.5?

Link to post
Share on other sites
Thanks for your reply.

 

I've tried 3 different usb sticks (different types and sizes).

Also tried win3diskimager for windows and tried dd on osx. All the same problem. Grub is not loading.

I've been having the same problem with an Intel DQ35MPE motherboard and have asked the same question in the forums. No one has responded with a solution. I've never had this issue with Trantor's builds.

Link to post
Share on other sites
Thanks for your reply.

 

I've tried 3 different usb sticks (different types and sizes).

Also tried win3diskimager for windows and tried dd on osx. All the same problem. Grub is not loading.

 

disable option in the BIOS "Data Execution Prevention"

http://www.msfn.org/board/topic/111181-problems-boot…winpe2-usb-stick/

 

Total 4 options:

1. Turn off "Data Execution Prevention"

2. Install boot loader on PBR

3. Update BIOS

4. Format with a tick "Force use of LBA calls"

 

Failed to load the flash drive through reformatting program RMPrepUSB v2.1.648 with a tick "Force use of LBA calls".

Grub4DOS also put through it, the installer sets of Alkid from 30.03.2012 refused to work with non-standard format disc.

http://reboot.pro/topic/12266-usb-imagi ... ce-rmprep/

Link to post
Share on other sites
Hi gnoboot,

 

Thank you very much!! I have tried to use the gnoboot-alpha 10.4, I can install my TV usb...

 

[  548.508112] usb 2-1: new high-speed USB device number 4 using ehci_hcd
[  548.908546] dvb-usb: found a 'Conexant DMB-TH Stick' in warm state.
[  549.249405] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[  549.249602] DVB: registering new adapter (Conexant DMB-TH Stick)
[  551.459336] usb 2-1: DVB: registering adapter 0 frontend 0 (Legend Silicon LGS8913/LGS8GXX DMB-TH)...
[  551.459576] MXL5005S: Attached at address 0x63
[  551.460018] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:13.2/usb2/2-1/input/input4
[  551.460025] dvb-usb: schedule remote query interval to 100 msecs.
[  551.460244] dvb-usb: Conexant DMB-TH Stick successfully initialized and connected.
[  551.461146] usbcore: registered new interface driver dvb_usb_cxusb

 

BTW, I have clicked the ADs to support development. :mrgreen:

 

Hi, I have just updated my DSM from 4.3-3810 to 5.0-4438 using gnoboot-alpha 10.5 in my N54l . I then plugged in my Contex DTV-01 USB stick (with "LGS8GL5" chipset) but the device manager can't detect the USB stick (It can be detected while I was using DSM 4.3-3810). Can anyone help me with this issue?

 

Below is the dmesg information after i plugged in the Contex DTV-01 USB stick but the DSM Panel still doesn't show any external usb device is connected:

 

[ 525.247101] usbcore: deregistering interface driver dvb_usb_cxusb

[ 528.348829] dsmnotify.cgi[6374]: segfault at 0 ip 000000000804ccb8 sp 00000000ffe65c30 error 6

[ 528.797115] usb 1-3: new high-speed USB device number 4 using ehci_hcd

[ 529.203259] dvb_usb_cxusb: probe of 1-3:1.0 failed with error -22

[ 529.203383] usbcore: registered new interface driver dvb_usb_cxusb

Link to post
Share on other sites

@Grinroth and others not booting GRUB:

 

The problem was in the old bios of the HP computer (and probably others) apparantly:

 

Solved by using these steps:

 

1) mount the .img (vfat if you're using windows) image

2) use RMprep to prepare the USB stick Fat32 with 2nd partition (USB HDD option) and install Grub4DOS on it. Let it install to MBR and(!) PBR.

3) copy all files and directories from the mounted image into the USB stick

4) open the computer case and UNPLUG the DVD - CD ROM drive (!) without this action the kernel will freak out on ata_piix (!)

5) close the case (duh) set bios to boot from USB, boot from stick and select GNOboot.me at first. Install synology with assistant. Boot alpha at reboot (automatic, so no worry)

 

done. Some bios roms don't like the USB boot when written directly from the img. This way the bios from HP will boot the zImage, so the Synology DSM can be installed. meh.

Link to post
Share on other sites

Are there any known problems with the VPN Server package in gnoBoot DSM 5.0? I migrated from a trantor 4.3 build and initially the VPN Server package was causing system hangs that stopped me from using Package Center. I had to SSH in and kill the VPN processes before uninstalling the package. I reinstalled the package and can get PPTP working, but L2TP frequently causes systems hangs. Sometimes i can enable L2TP but other times if i make changes to the L2TP settings or try and disable it , i just get 'Operation cannot be performed error'. If i reboot, at this point then the DSM doesn't properly startup and wont let me login until i SSH and kill the VPN processes. Any ideas what is causing this?

 

I just tried to enable L2TP. It thought about it for about a minute before saying 'Operation cannot be performed'.

/var/log/messages shows the following:

 

DiskStation> tail messages

Apr 23 23:13:57 DiskStation kernel: [ 2628.396776] [] ? cstar_dispatch+0x7/0x32

Apr 23 23:13:57 DiskStation kernel: [ 2628.396776] Code: <3b> 02 76 02 0f 0b ff c8 48 98 48 8b 54 c2 18 31 c0 48 85 d2 75 02

Apr 23 23:13:57 DiskStation kernel: [ 2628.396776] RIP [] xfrm6_tunnel_net_init+0x11/0x66 [xfrm6_tunnel]

Apr 23 23:13:57 DiskStation kernel: [ 2628.396776] RSP

Apr 23 23:13:57 DiskStation kernel: [ 2628.396776] CR2: 0000000000000000

Apr 23 23:13:57 DiskStation kernel: [ 2629.734234] ---[ end trace 26773a7ecb2ab0a5 ]---

Apr 23 23:13:57 DiskStation synomoduletool: iptables_mod_insert.c:142 /sbin/insmod /lib/modules/xfrm6_tunnel.ko failed![0x2A00 iptables_mod_insert.c:141]

Apr 23 23:13:57 DiskStation synomoduletool: iptables_mod_insert.c:156 Insert module (xfrm6_tunnel.ko) fail![0x2A00 iptables_mod_insert.c:141]

Apr 23 23:13:57 DiskStation synomoduletool: iptables_mod_insert.c:263 Insert module (xfrm6_tunnel.ko) fail![0x2A00 iptables_mod_insert.c:141]

Apr 23 23:13:57 DiskStation synomoduletool: iptables_mod_insert.c:290 Insert module fail![0x2A00 iptables_mod_insert.c:141]

 

 

Sometimes i see the following when i try and disable then enable it:

 

Apr 23 23:34:50 DiskStation ipsec_setup: ...Openswan IPsec stopped

Apr 23 23:36:00 DiskStation kernel: [ 3952.967066] ipcomp6: gave up waiting for init of module xfrm6_tunnel.

Apr 23 23:36:00 DiskStation kernel: [ 3952.990325] ipcomp6: Unknown symbol xfrm6_tunnel_alloc_spi (err -16)

 

i see this if i try to stop the VPN Server package:

Apr 23 23:46:41 DiskStation ipsec_setup: Stopping Openswan IPsec...

Apr 23 23:46:41 DiskStation ipsec_setup: rmmod: can't unload 'xfrm6_tunnel': Device or resource busy

Edited by Guest
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.