Dark-Sider

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

Hi, 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

Hi, 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

Hi, I get 110 MB/s when copying files via GBit LAN. I'm using a LSI 9240-8i controller with stock-firmware w/o any Raid-Volumes defined. 6 WD-RED 4TB Disks are mapped via RDM (physical) into the Syno VM. The disks are attached as SCSI 0:1 thru 0:5. The Virtual Controller is LSI SAS. SMART is working except for the temp which displays 0°C Intel e1000 as virtual NIC. Mainborad is the A1SAM-2750F from Supermicro (Intel Avoton). bye, Darky

By googling another smaller issue, I found the solution to the problem where the first Data-Disk did not start as Drive 1. After adding "kernel /zImage rmmod=ata_piix,r8169,r8169_new" (you could probably leave the realtek stuff out) to the /boot/grub/menu_alpha.lst of the boot image I was able to get rid of the two phantom disks. The persisting problem still is, that the boot image vmdk (SCSI 1:0) get's somewhat recognized as /dev/sdg (sda thru sdf are my six data disks). This leads to the following log file entries: /var/log/messages Apr 21 01:16:39 Dark-NAS2 SystemInfo.cgi: disk_info_get.c:82 Failed to open /dev/sdg, errno=No such file or directory Apr 21 01:16:39 Dark-NAS2 SystemInfo.cgi: disk_info_enum.c:42 Failed to get disk information sdg Apr 21 01:16:46 Dark-NAS2 storagehandler.cgi: disk_info_get.c:82 Failed to open /dev/sdg, errno=No such file or directory Apr 21 01:16:46 Dark-NAS2 storagehandler.cgi: disk_info_enum.c:42 Failed to get disk information sdg /var/log/scemd.log Apr 21 01:17:59 Dark-NAS2 scemd: disk_temperature_get.c:28 open /dev/sdg failed. Apr 21 01:17:59 Dark-NAS2 scemd: external/external_fan_table_type_disk_temperature_ops.c:230 Invalid Disks temperature 0 Apr 21 01:17:59 Dark-NAS2 scemd: external/external_fan_config_table_lookup.c:148 Temperature Get fail logging those events every few seconds prevents the drives from spinning down and also makes clicking noise with the drives every other second... (this is what got me started in looking what's accessing my drives...) Any ideas on how to get rid of "sdg"? bye, Darky

So I probably found what those 2 upfront devices are... dmesg shows: [sun Apr 20 03:22:14 2014] ata_piix 0000:00:07.1: version 2.13 [sun Apr 20 03:22:14 2014] scsi0 : ata_piix [sun Apr 20 03:22:14 2014] scsi1 : ata_piix [sun Apr 20 03:22:14 2014] ata1: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0x1060 irq 14 [sun Apr 20 03:22:14 2014] ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0x1068 irq 15 [sun Apr 20 03:22:15 2014] stex: Promise SuperTrak EX Driver version: 4.6.0000.4 [sun Apr 20 03:22:15 2014] Fusion MPT base driver 3.04.20 [sun Apr 20 03:22:15 2014] Copyright (c) 1999-2008 LSI Corporation [sun Apr 20 03:22:15 2014] Fusion MPT SPI Host driver 3.04.20 [sun Apr 20 03:22:15 2014] Fusion MPT SAS Host driver 3.04.20 [sun Apr 20 03:22:15 2014] mptsas 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [sun Apr 20 03:22:15 2014] mptbase: ioc0: Initiating bringup [sun Apr 20 03:22:15 2014] ioc0: LSISAS1068 B0: Capabilities={Initiator} [sun Apr 20 03:22:15 2014] mptsas 0000:03:00.0: setting latency timer to 64 [sun Apr 20 03:22:15 2014] scsi2 : ioc0: LSISAS1068 B0, FwRev=01032920h, Ports=1, MaxQ=128, IRQ=18 So ata_piix gets added as scsi0 and scsi1. How do get rid of them?? Also changing internalportcfg to 0xfffffff (also adjusting usb and esata accordingly) did not improve the number of drives avail. The disk overview still shows only 6 slots left, with disks 3 to 8 inserted. bye, Darky

Hello, I got myself a Supermicro A1SAM-2750F (http://www.supermicro.com/products/motherboard/Atom/X10/A1SAM-2750F.cfm). I put the board into a 24bay 19" case. The SAS/SATA backplane is fed thru a LSI 9240-8i SAS-HBA and a port-expander. Since 8 cores seem a little much for just a NAS I installed ESXi 5.5 onto a Hard-Drive that is directly connected to the mainboards onboard SATA (which worked out of the box). I DL'ed both, the gnoboot 10.3 (ESXi) and 10.5 versions. I patched the 10.3 vmdk to point to the 10.5 .ext2.img file and gnoboot just bootet fine. The 9240 is running the stock-firmware without any RAID devices configured, so it just reports the single disks to the ESXi host. After that I setup 6 SATA 4TB drives which are attached to ports 0 thru 5 on the HBA as physical RMD within ESXi. I can access and see the drives from within the booted xpenology, although the suggested "Paravirtual SCSI" HBA did report my Drives as SSDs. Using smartctl I was able to pull all smart-values from the drives, but the disk manager within the DSM webinterface refused to show me any SMART-Values inclunding the serial-numbers. So I tried alle the different HBAs VMWAre would let me choose. Finalle the LSI-SAS HBA option displays all my drives as "HDD" and I get SMART readings (Serial-Number, self test possible etc.). Unfortunately the temperature of the drives shows as 0° C. Not sure why... Network Performance seems very good @110MB/s The gnoboot vmdk is LUN0:6 the Data Drives reside at LUNs 0:0 thru 0:5 There are still some other questions that are bothering me: 1) My first 4TB drive is listed as /dev/sdc (drive-3). I can't find out why. What occupies sda and sdb? fdisk can't open those devices. I'd prefer to have my first data disk sitting at /dev/sda. dmesg | grep sda also returns nothing 2) DSM reports a total number of 12 internal disks (since it's using the DS3612 software). I think I need to change the synoinfo internalportcfg value to 0xffffff if I want to have 24 internal disks. Maybe even 0x3ffffff if I can't figure out what occupies the first two slots. As far as I remember there is a copy of the synoinfo within etc.defaults. which file gets copied from where to where at which time? 3) Maybe the RS10613 software would contain some nice stuff for SAS drives, since the RM10613 probably uses a SAS HBA to connect to up to 106 disks 4) while browsing thru the synoinfo file I found the "eunitseq="sdm,sdq" line. Any idea what's that about? Expansion Unit? bye+thanks, Darky

Hi, I'm about to install XPEnology via gnoboot on my home-NAS. I have a frew questions. (Also I might suggest, as this thread grows and grows to setup a sub-forum for gnoboot) The gnoboot image goes on a usb thumb drive which probably corresponds to the "hidden" flash-boot device inside a normal synology box. The installer then installs the DSM onto the mirrored partition on all harddrives. As thumb drives _will_ fail some day, I wanted to ask if it's just a read only thing and if I can restore the downloaded gnoboot image to another thumb-drive and all will be fine again? Minor updates are downloaded in place and then the replacement with "sed" has to be done (why, do we need to change that string?). What about major releases. Let's say DSM 5.1 or even 6.0. Would one first update the gnoboot thumb drive and then in-place upgrade the DSM software? thanks for helping out, Dark-Sider

Hey folks, I'm building myself a NAS system. I went with a 24 Bay 19" case a SAS-Expander and a LSI 9240-8i HBA, which will be used without Raid-Functionality. As for board and CPU I'm using the Supermicro A1SAM-2750F with the Intel Avoton. I nearly got all the parts but I'm still waiting for the memory modules. So I was wondering if I could install XPEnology on the box. Which release should I try first, where might I come accross Kernel/Driver issues? thx + bye, Darky