bibicu
-
Posts
12 -
Joined
-
Last visited
Posts posted by bibicu
-
-
I had the same error with only one disk (just not on original hw, but in a VM)
After some time when everything worked fine, my volume crashed and I started to get checksum errors in files.
HDD SMART was healthy though, only CRC32 count had increased by 2.
I mounted the HDD in my old DSM 6.2 virtual machine and suddenly everything works fine, no more errors.
I did a scrub and all files are fine.
I dumped DSM7 and went back to DSM6.2
-
1
-
-
Thank you for a great tutorial.
I have successfully installed DSM7 on esxi 6.7, with SATA passthrough, and it works fine.
I have a few questions though:
1. When creating the VM for DSM7, should we choose BIOS or UEFI firmware in VM Options? Does TCRP support UEFI boot ? I used BIOS but I prefer UEFI b/c it supports booting from USB sticks and I can run memtest in VM.
2. When booting, tcrp (I assume) shows this message:
fdisk: device has more than 2^32 sectors, can't use all of them
I have a 4TB Wd Red and it works fine in VM, but should I be worried about the message?
Thank you !
-
@reworks Good to know that you can see Health info in 6.2.1 !
Which loader (1.03b or 1.04b) and model (ds918+ or ds3615x) are you on ?
Thank you
-
Please, can someone more knowledgeable than me explain what is the meaning of these ofoption in grub.cfg:
sata_uid=1
sata_pcislot=5
synoboot_satadom=1
Maybe @jun
I searched this forum and could not find an explanation.
Thank you !
-
@reworks:
after many many hours spent trying stuff, I came to conclusion that HW transcoding only works in 6.2.1 with the original extra.lzma.
In 6.2.2 it does not work. We may need to wait for Synology to release a Gemini Lake box to grab a newer i915 driver.
@reworks: do you see Health disk information for the disks in STorage manager?
I can't see (Access error) it with DS918
-
Can someone be so kind and confirm if HW transcoding is still enabled on J4105/j5005 with DSM 6.2.2, Jun 1.04b and DS918+ ?
Just check if there is something in /dev/dri
For me, the i915 driver crashes during the boot so I had to use real3x extra.lzma which removes it, but then I don't have hw transcoding.
@Olegin does not specify which version of DSM he was testing with, but I suspect it was an earlier version of DSM.
Thank you
-
I ran an iperf3 between SYnology VM (using E1000e) and another Linux VM on the same host and I got 10Gbps transfer speeds.
The internal Esxi virtual switch operates at 10Gbps
-
@Rowdy I was about to post that this error:
NMI watchdog: BUG: soft lockup - CPU#0 stuck for 41s! [insmod:6325]
Is because to i915.ko driver crashing.
I had the same problem and I had to use a minimal extra.lzma (which does not contain i915) for it to work.
I am curious if you have HW encoding active (I would guess you do not)
Can you please check if /dev/dri folder exists and there is something in it?
Regards
-
9 hours ago, bibicu said:
I have the same problem and I spent the past week trying all sorts of things.
I just can't see the Health info with Jun 1.04 loader and DS918+. I am passing the Intel SATA controller to Synology VM.
I went so far to create another VM, using Jun 1.03b loader and DS3615xs, passing through the same SATA controller and having the same HDD.
So, two VMs, one can see Health info, one cannot. Both running DSM 622-24922.
Any suggestions would be much appreciated !
I forgot to tell: in the DS3615xs / 1.03b machine I can see the Helath info.
In the DS(18+ / 1.04 I cannot
-
I have the same problem and I spent the past week trying all sorts of things.
I just can't see the Health info with Jun 1.04 loader and DS918+. I am passing the Intel SATA controller to Synology VM.
I went so far to create another VM, using Jun 1.03b loader and DS3615xs, passing through the same SATA controller and having the same HDD.
So, two VMs, one can see Health info, one cannot. Both running DSM 622-24922.
Any suggestions would be much appreciated !
-
Hi all !
First of all, thank you developers for the wonderful work on Xpenology project !
Does anyone know why the SATA disks show up as SCSI in DSM virtualized ? This will generate errors in the interface when I check the Health of the disks.
I am running DSM 6.2.2, Jun 1.04b, DS918+, in Esxi 6.7 on Asrock J4105-ITX board.
I have 3 disks in my VM:
1. the synoboot image (/dev/hda)
2. a virtual disk on SATA1:0
3. a Hitachi hdd on a SATA controller, using PCI Passthrough.
synodisk --enum
************ Disk Info ***************
>> Disk id: 1
>> Slot id: -1
>> Disk path: /dev/sda
>> Disk model: Virtual SATA Hard Drive
>> Total capacity: 0.05 GB
>> Tempeture: -1 C
************ Disk Info ***************
>> Disk id: 2
>> Slot id: -1
>> Disk path: /dev/sdb
>> Disk model: Virtual SATA Hard Drive
>> Total capacity: 16.00 GB
>> Tempeture: -1 C
************ Disk Info ***************
>> Disk id: 4
>> Slot id: -1
>> Disk path: /dev/sdd
>> Disk model: HTS545050B9A300
>> Total capacity: 465.76 GB
>> Tempeture: 29 Csmartctl --scan
/dev/hda -d ata # /dev/hda, ATA device
/dev/sdb -d scsi # /dev/sdb, SCSI device
/dev/sdd -d scsi # /dev/sdd, SCSI deviceAs you can see the HDD is seen as SCSI.
udevadm info --query=property --name /dev/sdd
DEVNAME=/dev/sdd
DEVPATH=/devices/pci0000:00/0000:00:17.0/0000:13:00.0/ata4/host3/target3:0:0/3:0:0:0/block/sdd
DEVTYPE=disk
ID_PART_TABLE_TYPE=gpt
MAJOR=8
MINOR=48
PHYSDEVBUS=scsi
PHYSDEVDRIVER=sd
PHYSDEVPATH=/devices/pci0000:00/0000:00:17.0/0000:13:00.0/ata4/host3/target3:0:0/3:0:0:0
SUBSYSTEM=block
SYNO_DEV_DISKPORTTYPE=SATA
SYNO_INFO_PLATFORM_NAME=apollolake
SYNO_KERNEL_VERSION=4.4
USEC_INITIALIZED=779574So all disks, even though are on SATA controllers show up as SCSI and smartctl fails for them.
If I try to get SMART info, I get an error:
smartctl -a /dev/sdd
SMART support is: Unavailable - device lacks SMART capability.
But if I add -d ata, it works.
SMART support is: Available - device has SMART capability.
Anyone can shed some light how to make the disk be seen as SATA instead of SCSI?
Thank you !
DSM 7 on DS918+, healthy drives but crashed volume
in General Questions
Posted
@Bibbleq what was the response from Synology to your ticket? How did you solve your issue ?