Gex

Members
  • Content count

    17
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Gex

  • Rank
    Newbie

Recent Profile Visitors

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

  1. I tried the following update procedure without success: 1. Install DSM 6.0.2 into a new VM using Jun's loader 1.01 and create a basic volume 2. Update to 6.0.2 U9 (had to do a hard reset of the VM once after upgrading), successful 3. Shutdown 4. Remove 1.01 synoboot.vmdk, add 1.02a synoboot.vmdk and boot the VM 5. VM won't completely boot into DSM, web interface tells me to update to 6.1 6. Upload .pat file for 6.1 via web interface, everything seems fine up to this point. Chose the "migrate and keep settings" option over the "reinstall and only keep data" option. Update begins. 7. VM reboots and won't come up again --> fail. I had the VM redirect its COM1 port to a txt file and this is what it looks like now: [ 4.528899] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 4.581904] sd 0:0:0:0: [sda] Incomplete mode parameter data [ 4.611890] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 4.651344] sd 0:0:0:0: [sda] Incomplete mode parameter data [ 4.661292] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 4.982197] ata1: Read current link speed fail, retry 1 [ 5.017897] ata1: Read current link speed fail, retry 2 [ 5.036262] ata1: Read current link speed fail, retry 3 [ 5.074569] ata2: Read current link speed fail, retry 1 [ 5.088286] ata2: Read current link speed fail, retry 2 [ 5.098893] ata2: Read current link speed fail, retry 3 [ 5.106148] ata1: Issued IDENTIFY to non-existent device ?! [ 7.226517] ata1: Read current link speed fail, retry 1 [ 7.238722] ata1: Read current link speed fail, retry 2 [ 7.259413] ata1: Read current link speed fail, retry 3 [ 7.261137] ata1: Issued IDENTIFY to non-existent device ?! [ 9.418591] ata1: Read current link speed fail, retry 1 [ 9.440276] ata1: Read current link speed fail, retry 2 [ 9.465911] ata1: Read current link speed fail, retry 3 [ 9.480874] ata1: Issued IDENTIFY to non-existent device ?! [ 11.639599] ata1: Read current link speed fail, retry 1 [ 11.649804] ata1: Read current link speed fail, retry 2 [ 11.679829] ata1: Read current link speed fail, retry 3 [ 11.879651] md: invalid raid superblock magic on sda3 [ 868.949994] Restarting system. ............. [ 4.386686] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 4.443562] sd 0:0:0:0: [sda] Incomplete mode parameter data [ 4.472466] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 4.509918] sd 0:0:0:0: [sda] Incomplete mode parameter data [ 4.521888] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 4.834537] ata1: Read current link speed fail, retry 1 [ 4.869557] ata1: Read current link speed fail, retry 2 [ 4.901761] ata1: Read current link speed fail, retry 3 [ 4.935602] ata2: Read current link speed fail, retry 1 [ 4.947774] ata2: Read current link speed fail, retry 2 [ 4.957817] ata2: Read current link speed fail, retry 3 [ 4.959723] ata1: Issued IDENTIFY to non-existent device ?! [ 7.089336] ata1: Read current link speed fail, retry 1 [ 7.110555] ata1: Read current link speed fail, retry 2 [ 7.120545] ata1: Read current link speed fail, retry 3 [ 7.122814] ata1: Issued IDENTIFY to non-existent device ?! [ 9.282435] ata1: Read current link speed fail, retry 1 [ 9.309388] ata1: Read current link speed fail, retry 2 [ 9.355944] ata1: Read current link speed fail, retry 3 [ 9.389786] ata1: Issued IDENTIFY to non-existent device ?! [ 11.549004] ata1: Read current link speed fail, retry 1 [ 11.576282] ata1: Read current link speed fail, retry 2 [ 11.591274] ata1: Read current link speed fail, retry 3 [ 11.773601] md: invalid raid superblock magic on sda3 [ 42.114714] BTRFS: has skinny extents So now you could go ahead and try different approaches, two of them being: - Attempt to do the update via the DSM web interface before changing the synoboot.vmdk to 1.02a or - Choose the "reinstall and keep data" option when prompted on the web interface If I had taken a snapshot of the VM before the update, I would try... oh well. Edit: After rebooting the VM, the log looks a bit more promising: patching file etc/synoinfo.conf patching file linuxrc.syno patching file usr/sbin/init.post START /linuxrc.syno Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module ehci-hcd ... [ OK ] :: Loading module ehci-pci ... [ OK ] :: Loading module ohci-hcd ... [ OK ] :: Loading module uhci-hcd ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module etxhci-hcd ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading module BusLogic ... [ OK ] :: Loading module vmw_pvscsi ... [ OK ] :: Loading module megaraid_mm ... [ OK ] :: Loading module megaraid_mbox ... [ OK ] :: Loading module megaraid ... [ OK ] :: Loading module scsi_transport_spi ... [ OK ] :: Loading module mptbase ... [ OK ] :: Loading module mptscsih ... [ OK ] :: Loading module mptspi[ 4.444826] sd 0:0:0:0: [sda] Incomplete mode parameter data [ 4.449110] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 4.463970] sd 0:0:0:0: [sda] Incomplete mode parameter data [ 4.465942] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 4.482676] sd 0:0:0:0: [sda] Incomplete mode parameter data [ 4.484877] sd 0:0:0:0: [sda] Assuming drive cache: write through ... [ OK ] :: Loading module mptsas ... [ OK ] :: Loading module mptctl ... [ OK ] :: Loading module ata_piix[ 4.809929] ata1: Read current link speed fail, retry 1 [ 4.844371] ata1: Read current link speed fail, retry 2 [ 4.869253] ata1: Read current link speed fail, retry 3 [ 4.893491] ata2: Read current link speed fail, retry 1 [ 4.929099] ata2: Read current link speed fail, retry 2 [ 4.958922] ata2: Read current link speed fail, retry 3 [ 4.972704] ata1: Issued IDENTIFY to non-existent device ?! [ 7.050180] ata1: Read current link speed fail, retry 1 [ 7.063623] ata1: Read current link speed fail, retry 2 [ 7.093430] ata1: Read current link speed fail, retry 3 [ 7.110508] ata1: Issued IDENTIFY to non-existent device ?! [ 9.272260] ata1: Read current link speed fail, retry 1 [ 9.293305] ata1: Read current link speed fail, retry 2 [ 9.308325] ata1: Read current link speed fail, retry 3 [ 9.331196] ata1: Issued IDENTIFY to non-existent device ?! [ 11.493653] ata1: Read current link speed fail, retry 1 [ 11.528889] ata1: Read current link speed fail, retry 2 [ 11.559970] ata1: Read current link speed fail, retry 3 ... [ OK ] :: Loading module megaraid_sas ... [ OK ] :: Loading module mpt2sas ... [ OK ] :: Loading module mpt3sas ... [ OK ] Insert net driver(Mindspeed only)... Starting /usr/syno/bin/synocfgen... /usr/syno/bin/synocfgen returns 0 [ 12.253539] md: invalid raid superblock magic on sda3 Partition Version=8 /sbin/e2fsck exists, checking /dev/md0... 1.42.6-8438: recovering journal 1.42.6-8438: |== | 3.7% 1.42.6-8438: |======================================== / 84.0% 1.42.6-8438: |================================================| 100.0% 30816 inodes used (19.80%, out of 155648) 31 non-contiguous files (0.1%) 8 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 0/0/0 Extent depth histogram: 28045/12 244851 blocks used (39.33%, out of 622544) 0 bad blocks 1 large file 24594 regular files 3163 directories 2 character device files 0 block device files 0 fifos 1229 links 3048 symbolic links (2749 fast symbolic links) 0 sockets ------------ 32036 files /sbin/e2fsck returns 1 Mounting /dev/md0 /tmpRoot ------------upgrade Begin upgrade procedure No upgrade file exists End upgrade procedure ============upgrade Wait 2 seconds for synology manufactory device Thr Mar 2 16:34:15 UTC 2017 /dev/md0 /tmpRoot ext4 rw,relatime,journal_checksum,data=ordered 0 0 none /sys/kernel/debug debugfs rw,relatime 0 0 sys /sys sysfs rw,relatime 0 0 none /dev devtmpfs rw,relatime,size=506564k,nr_inodes=126641,mode=755 0 0 proc /proc proc rw,relatime 0 0 linuxrc.syno executed successfully. Post init [ 23.438885] BTRFS: has skinny extents DSMigrationTest login: Looks better to me (though still not good), but the web interface remains unreachable.
  2. Gex

    DSM 6.1.x Loader

    At least there's a post from 2015 which indicates that it used to work with 5.1. viewtopic.php?f=7&t=5026&start=60#p29661 So why don't you just go ahead and give it a try? Edit: Besides, a 2012 Mac Mini would (depending on its hardware configuration) still be worth a few hundred bucks, so you could still sell it and buy some hardware that is much better suited for an Xpenology system, including hard drives.
  3. Thank you for sharing! Finally a way to get DSM working on Virtualbox. Plus, it's really dead simple. I just successfully installed DSM 6.1-15047 for DS3617xs using Jun's Loader 1.02a. (So it would be safe to edit the thread title accordingly ) Pitfalls: * Make sure you add a SCSI controller for the data disks. I didn't read the instructions too thoroughly and added a SATA controller. This will lead to error 35 during installation (Failed to format the drive). * Make sure you make the virtual harddisk(s) bigger than the standard 8 GB. If the virtual disks are too small you might encounter error 35, too. Edit: @sera This is due to the partition layout that DSM creates during the installation. Every hard disk will hold a system partition (mirrored across all disks), a swap partition and a data partition. So the first two will use a certain amount of disk space and the data partition gets what's left. Edit: The link to Jun's loader in the first post is dead. Currently this one is working: https://mega.nz/#F!BtFQ2DgC!JgomNP3X8V9EuwxL4TXbng Edit: Installed DSM 6.1 Update 1 without any problems.
  4. AFAIK when using DSM, every installed hard drive will become a "system drive", holding a system partition. Changes to the system will be mirrored on all hard disks. So you can remove any hard disk at any time and still be able to boot the DSM (though depending on your RAID configuration, you might still lose your data, e.g. if you remove two disks from a RAID5 array). So as long as you don't remove all disks at once, your system will remain bootable. This should eliminate the need for a separate "system drive" for almost all use cases. Besides that, I haven't seen anyone installing DSM to a dedicated "system drive" yet, so I don't think it is even possible. But I may be wrong with that since I have started using DSM myself only a few weeks ago.
  5. Gex

    DSM 6.1.x Loader

    I am running DSM 6.0.2 on the ASRock J3455M (bare metal) and experienced some rather weird issues with the speed of the onboard Realtek RTL8111E chip. See the full details here: viewtopic.php?f=2&t=25026 After throwing in the Intel PCIe NIC and disabling the onboard Realtek chip, everything worked very smoothly.
  6. Gex

    Squeezelite und Logitech Media Server

    Hi, ich habe mich letztes und vorletztes Jahr mit dem Thema Multiroom-Audio beschäftigt und auch eine Lösung mit dem Logitech Media Server in Erwägung gezogen. Mein Tipp: Lass es. Logitech hat das ganze Squeezebox-Zeug eingestampft, den Server gibt es zwar noch, aber der wird (zumindest war das der Stand damals) von genau einem Entwickler weiter gepflegt, und das auch nur so halb. Das DSM-Paket ist auch nicht die aktuellste Version (7.9 Beta, ob da jemals noch eine stabile Version 7.9 draus wird wage ich zu bezweifeln) sondern eine alte (7.7). Das Web-UI ist altbacken, die verfügbaren Apps für mobile Endgeräte sind eher mittelprächtig, usw... außerdem brauchst du für jedes Paar Lautsprecher ja auch noch einen Raspberry Pi + DAC-Platine (der onboard Audio Ausgang ist nicht zu gebrauchen), also mal locker um die 70€ für jedes Set. Ich hab das ganze ausprobiert (Server + 2x RasPi) und es funktioniert schon nicht schlecht, aber aufgrund der genannten Einschränkungen habe ich mich dagegen entschieden. Für mich war die bessere Lösung der Google Chromecast Audio + DLNA-Server auf dem NAS, da gibt es schöne Apps für Android, die gängigen Musikstreaming-Apps (Spotify und Konsorten) haben ebenfalls den Support dafür schon drin, und jeder Endpunkt kostet 39€ (bei eBay Kleinanzeigen auch schonmal 25€). Die Dinger lassen sich auch gruppieren usw. und haben eine sehr gute Audio-Qualität. Also, meiner Meinung nach reitet man mit dem ganzen Logitech-Zeug ein totes Pferd.... wenn man so eine Installation schon hat und damit glücklich ist, OK, aber neu aufziehen würde ich mit dem System nichts mehr.
  7. Hi, thanks for pointing that out, I actually have a speaker built into my case and connected to the speaker pins on the Mainboard @tamamma: I have experienced some rather weird networking issues with the onboard Realtek chipset. Using an Intel PCIe NIC, everything works fine (bare metal).
  8. Hi guys, much to my surprise the search function returned virtually no results for keywords like "speaker" or "beep". I would like to either use the built-in "Beep Control" functionality in the task scheduler or any other command line utility (like http://www.johnath.com/beep/) to make the PC speaker beep e.g. on system shutdown or disk failure. The "Beep Control" feature doesn't work at all, no beep to be heard at the scheduled time. I then grabbed the beep binary (x86_64) from the debian package repository but it didn't work either (without any error message though). I am running a bare metal installation of DSM 6 on an ASRock J3455. Do I need a driver? Or do you have any other hints? Thanks!
  9. Gex

    DSM 6.0.2-8451 Update 9

    I am running a bare metal installation using Jun's loader v1.01, ASRock J3455M, Intel NIC, LSI 9211-8i IT-Mode, 6x 1TB RAID5 (btrfs). Since it's a pretty fresh installation I hadn't disabled automatic update yet, so last night DSM installed update 9 (was 8 before) automatically. No issues at all, according to the system log the box came up within a few minutes after the update. No network problems either. EDIT: Well, I just noticed that SSH and Telnet services seem to be broken, at least when accessing the machine from the internet via port forwarding. Duh... EDIT2: Works fine one the local network. Still have to figure out why it didn't work from a remote location (that used to be ok, no blocked ports or anything).
  10. Gex

    DSM 6.1.x Loader

    I have been able to install baremetal with an IBM M1015 crossflashed to LSI 9211 8i (IT-Mode) without any issues. Mainboard ASRock J3455M. That board has Realtek RTL8111E nic did you have to edit grub.cfg for it to work? What ramdisk.lzma are you using? What's the firmware version on your LSI card? My card is flashed to P20 IT mode. Hi, sorry for the delay. RTL8111E: Worked out of the box, but turned out to cause some weird network speed issues as described here: http://xpenology.com/forum/viewtopic.php?f=2&t=25026. I decided to just disable the onboard NIC and use a pair of Intel PCIe NICs instead. ramdisk.lzma: I don't even know how to change this or where to get or how to create alternative ramdisk files. I just used the latest Jun's loader... LSI firmware: P20 IT mode, too.
  11. Gex

    DSM 6.1.x Loader

    I have been able to install baremetal with an IBM M1015 crossflashed to LSI 9211 8i (IT-Mode) without any issues. Mainboard ASRock J3455M.
  12. I now got a par of HP NC110T NICs from eBay (in used condition at just 5$ each). These use the Intel 82572GI controller and are supported by the e1000e driver: root@DiskStation:~# ethtool -i eth0 driver: e1000e version: 3.3.5-NAPI firmware-version: 5.11-10 bus-info: 0000:02:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no Using this NIC, the slow download rates are gone. Everything works at full GBit speed now, regardless the way I access the machine. If you google around for RTL8111E and r8168, you will find A LOT of issues people are experiencing with this chip and this driver on Linux. Although most of the issues should have been fixed in the driver by now and it is said to be performing quite well, this doesn't seem to be quite true for my setup. I will just disable the onboard Realtek chip and use the Intel card(s). So my recommendation by now would be: If you run into trouble with the RTL8111E, this is most certainly an issue with the driver. Don't waste your time trying to fix it - go and grab an Intel based NIC off eBay instead.
  13. Some more info: Driver seems to be r8168 in version 8.043.01-NAPI. According to the Realtek website, this is (almost) the most recent version (8.043.02 currently being available for download). root@DiskStation:~# dmesg | grep 'Ethernet' [ 30.763611] Intel(R) Gigabit Ethernet Network Driver - version 5.3.5.4 [ 30.815623] i40e: Intel(R) Ethernet Connection XL710 Network Driver - version 1.3.47 [ 31.651453] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.714.0 ($DateTime: 2016/08/25 21:13:29 $) [ 31.992124] pch_gbe: EG20T PCH Gigabit Ethernet Driver - version 1.01 [ 32.012556] QLogic 1/10 GbE Converged/Intelligent Ethernet Driver v5.2.42 [ 32.630113] r8168 Gigabit Ethernet driver 8.043.01-NAPI loaded root@DiskStation:~# uname -a Linux DiskStation 3.10.77 #8451 SMP Wed Aug 17 05:12:41 CST 2016 x86_64 GNU/Linux synology_bromolow_3615xs root@DiskStation:~# ethtool -i eth0 driver: r8168 version: 8.043.01-NAPI firmware-version: bus-info: 0000:01:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: yes supports-priv-flags: no I will try to get my hands on a NIC with Intel chipset and see if that changes anything.
  14. So I am playing around with DSM 6 (Update 6, jun's loader v1.01) on my ASRock J3455M, Realtek RTL8111E NIC. I noticed that when downloading a file from DSM via SMB, there is a HUGE drawback in speed when I access it via its hostname (like \\mydiskstation). Download speed ranges from <1 MB/s to ~2.5 MB/s depending on the client I run the test on. When I use the IP address instead (like \\192.168.1.10) everything is fine and I download at full GBit speed (up to 110 MB/s). This could be reproduced on two different laptops (Lenovo X201 and R61) and three operating systems (Windows 10, Windows 7 and Ubuntu 16.04). It could NOT be reproduced when uploading a file. Upload speed varies between 70 and 110 MB/s regardless the way I access the machine. I have a Zyxel NAS on the same network which happily provides its full download speed of ~45-50 MB/s both via hostname and IP address. All additional packages that I had installed before have been stopped and QuickConnect has been disabled. The network settings are all pretty default, fiddling around with the SMB protocol didn't help. Static IP vs. DHCP didn't make a difference either. I see the same scenario when downloading a file via HTTP (web interface) or SFTP (ssh). Using the host name: very, very low speeds (< 1 MB/s using HTTP, even less using SFTP). Using the IP address: 45 MB/s using HTTP, >10 MB/s using SFTP (which seems rather slow too, but SFTP is not a use case for me at the moment, so I don't really care). So I assume it's safe to say that this has nothing to do with the SMB protocol but seems to be a problem somewhere further down the network stack. When I googled around for that issue, I found several forum posts even on the official Synology forum by people who seem to have similar problems with their genuine Synology boxes. Although they usually just complain about their download being slow. Any help would be appreciated!
  15. Gex

    DSM 6.1.x Loader

    I have now successfully installed DSM 6.0.2 Update 6 on my System (ASRock J3455M "Apollo Lake" Mainboard, LSI 9211-8i SAS/SATA HBA, bare metal). I had changed VID/PID, MAC and SN in my grub.cfg as described and then installed DSM to two 80GB disks attached to the LSI. When creating a RAID1 volume I got an error, but i'd rather blame that on the 12 y/o drives I had kicking around my junk drawer for years than on DSM Everything else went smoothly and looks very promising so far.