IG-88

Members
  • Content Count

    2,450
  • Joined

  • Last visited

  • Days Won

    101

Everything posted by IG-88

  1. as i dont know what exactly you've done i can only assume from the information i can read in general, there is no main drive from the (dsm) systems point of view, every disk gets a system ans swap partition when integrated in dsm (initialized), these system and swap are raid1 volumes over all disks in the system, even if only one disk is still working your system will com up so my guess is you had one 8TB with a basic volume and added two more later with a raid0 volume for the system (its linux mdadm) its two raid1 volumes over 3 disks (system and swap) one basic volume on one disk and one raid0 volume over two disks for the update you removed the 2 added disks updated to dsm 6.2 and reported one disk in the 1st post at least that would explain why 6.1 is back when you removed the system partition from the 1st disk, re-added the old two disks an rebooted one missing part is the usb in that scenario, if you updated to 6.2 the new kernel (zImage and rd.gz) would have been copied to the usb loader (still 1.02b) rendering the loader to a non working state, to get dsm 6.1 back running from the two remaining system partitions of the two old disks (raid1 with 2 of 3 working) you would have needed to reset the 1.02b loader from scratch (or a old copy) or restore the kernel files back to 6.1 state having a backup is good best way was 1st on my answer, use loader 1.03b and make it work, if you would have done this and get it working by using csm/legacy mode from bios the system would have just finished the update to 6.2.3 and you would have been on them latest dsm version if you still want to use 6.2.3 then disconnect all drives, try loader 1.03b (csm/legacy in bios) and see of you can find it in network, if you get this working you passed the hurdle for using 6.2.3, if that does not work out you still can use your old 1.02b usb to install 6.1
  2. i was about to ask the same, anyway even if its more the one disk as long as only the 1st partition was deleted the data raid set over all disks is still there before doing anything further plug in all disks and check if you data volume is there, dont change or initialize anything before the situations is clear the initialize just means that the system partition is not found but might also indicate it does not find a raid data volume either we would need to check the state of the raid's from the command line to see whats going on, also a screenshot or two from dsm disk manager might be good
  3. not really, we do this in our spare time and the corona crisis might even be more work for some people, not all have a relaxed job with home office there is no organized support team or anything, people in need of such structure might build them up, maybe start a wiki or pay the full price and buy a original synology hardware and get support from synology
  4. one specialty with 1.03b/6.2.x is that you cant boot in uefi mode, needs to be legacy and also the usb boot device from the list needs to be ckecked if its legacy (often csm/legacy is just a added option and you see uefi and legacy usb devices) the network driver seems to be a normal realtek, 2nd gen cpu also means no 1.04b/918+ if its just one disk you could also boot a recovery linux and delete the 1st partition (2GB) and the start installing your old dsm version with the old loader, the installer should ask if you want to keep the data when installing dsm i theory you could also use the recovery linux to reset the version file of dsm to a lower version as you had before, then the dsm installer would do a update to your 6.1 version and you would keep your data without raid (just one disk) its nothing special like assembling the system parturition's raid1 from all disks
  5. a folder /.xpenology can prevent 6.x from booting properly, it should be removed
  6. one difference comes to mind when thinking again, the host os (windows) can be used for caching and that might be a little out of the equation of linux/btrfs and when the power fails unexpectedly there might be a good amount of data missing (my vm's are just for testing and compiling drivers and i do have a backup so i guess i can leave the caching on) i dont know much about btrfs but i had expected it to be recoverable in this situation maybe i should try this out by overwriting some big block of sectors with zeros an see what files i can get out after it
  7. IG-88

    TerraMaster F2-421

    if you want to user the hardware transcoding you will have to replace the extra.lzma with 6.2.3 https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/ https://xpenology.com/forum/topic/24864-transcoding-without-a-valid-serial-number/
  8. IG-88

    TerraMaster F2-421

    from the hardware it looks like it should boot with 1.04b ootb (1.03b depends on if its uefi or legacy bios, but 1.04b can handle both) https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ check both nic ports, check dhcp server for used address, use synology assistant program from synology to find it in network
  9. yes, for every patch there is a definition from and to version it is valid #arrays declare -A binhash_version_list=( ["cde88ed8fdb2bfeda8de52ef3adede87a72326ef"]="6.0-7321-0_6.0.3-8754-8" ["ec0c3f5bbb857fa84f5d1153545d30d7b408520b"]="6.1-15047-0_6.1.1-15101-4" ["1473d6ad6ff6e5b8419c6b0bc41006b72fd777dd"]="6.1.2-15132-0_6.1.3-15152-8" ["26e42e43b393811c176dac651efc5d61e4569305"]="6.1.4-15217-0_6.2-23739-2" ["1d01ee38211f21c67a4311f90315568b3fa530e6"]="6.2.1-23824-0_6.2.3-25426-0" ) the last line needs to be extended so that the valid ends with "6.2.3-25426-2" instead of "6.2.3-25426-0" ["1d01ee38211f21c67a4311f90315568b3fa530e6"]="6.2.1-23824-0_6.2.3-25426-2"
  10. technically thats not a loader problem, its a driver problem, the mbr loader is a variation of how it boots, the drivers are loaded later fro m the rd.gz (default driver from synology) and extra.lzma, and the later can be exchanged with a new extra.lzma containing more drivers, BUT in your case it will not work https://xpenology.com/forum/topic/9508-driver-extension-jun-102bdsm61x-for-3615xs-3617xs-916/ !!!all sata_* and pata_* drivers are still not working because of the kernel source changes Synology did (same as in kernel 3.10.102 used and modded by Synology), as long as no one writes a patch for this I can use to fix this, it will stay this way !!! and it still that way with 6.2 if you dont have ahci then there are other options like a lsi sas controller a pcie cards with 4-8 ports with ahci compatible chips if you need to use the onboard non ahci controller and loader 1.02b with its default drivrs dont work for you then you need to stay with 6.0 so the people providing the modded loader can't help you as it is a driver problem anf the driver package for "normal" loader and mbr loader are the same
  11. you did not write about your hardware but if 1.02b work and 1.03b does not then it might be uefi/bios legacy problems, 1.03b does not support uefi https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ and depending on your cpu 1.04b might be possible
  12. any reason or motivation for writing this here? because i use btrfs in my test vm's for xpenology, never seen any problems and why should it make a difference if it run's in virtualbox?
  13. chip ist LSI 2108 und raid wird nur bedingt unterstützt, gedacht ist dsm für einzelplatte mit mdadm/lvm2 raid, wenn es normal oder "richtig" laufen soll dann würde man in den controller eine IT (intiator target) firmware flashen, jetzt ist eine IR firmware drin, das IR sieht man auch im controlelr bios da musst du genauer sein, die 918+ braucht min. 4th gen intel (hasewell oder neuer) außerdem wird das noch wichtig wenn die 8 kerne auch HT haben (=16 "sichtbare" kerne) , dann kommt für volle nutzbarkeit eigentlich nut 3617 in frage da die anderen beiden varianten nur max. 8 unterstützen ohne serielles (nullmodem) kabel als consolen monitor kannst du das nicht wiklich sagen, man sieht auf dem display nicht ob der kernel nicht bootet oder es am netzwerktreiber liegt wenn es nicht im netz gefunden wird loader 1.03b 3615/17 wollen nicht mit uefi da ist csm/legacy mode nötig und man muss auch vom usb legacy device booten zum testen ist loader 1.02b da besser, der kann uefi und legacy, wenn der nicht hoch kommt liegt es ziemlich sicher am netzwerk treiber https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ sowas bedeutet meist probleme mit vid/pid vom usb hin quicknicks 3.0 loader ist aber ein release das ohne seine zustimmung released wurde und ich werde da niemanden bei der nutzung unterstützen - deshalb gibt es dau auch eine richtige doku oder support ist interessant wenn jemand mehr über loader wissen will und die sache weiter entwickeln will was hat die kiste den für eine netzwerkkarte? hast du zusätzliche treiber in form einer extra.lzma benutzt? soweit ich mich erinere hatte jun ein seinem default treiber satz nicht immer alle firmware varianten für die broadcom nic's dabei die man häufig bei dell hat, so das eine extra.lzma angesagt wäre https://xpenology.com/forum/forum/91-additional-compiled-modules/ (gibt da merere threads je nach loade rund dsm version) nur um mal zu booen und zu sehen ob es im netzwerk gefunden wird musst du übrigens weder vid/pid noch sn oder mac anpassen, vid/pid wird erst beim installieren des *.pat files wichtig, sn ist für den grudlegenden nas betrieb egal ud mac nur wichtig wenn man wol nutzen will, kann man alles auch später noch anpassen . mach das testen schneller wenn man die grub.cfg nicht anpassen muss außerdem ist win10 bei den partitionen des loaders etwas zickig, da solltest du mal das lesen https://xpenology.com/forum/topic/29670-howto-1-partition-des-bootsticks-in-windows-mountenbearbeiten-grubcfg/
  14. in a vm its ok to have no usb but for a baremetal i would configure it, its not that difficult also keep in mind that a bigger update (200-300MB *.pat file) will replace the system partition and reset the synoinfo.conf to defaults an depending on the missing disks there will be raids not starting or lost redundancy disks that need to be rebuild
  15. you dont need to have usb configured, i never used usb storage with my xpenology vm's
  16. thats not as it should be, the internal and external(esate, usb) disks are overlapping that would be my choice for doing 24 disks esataportcfg="0x0" internalportcfg="0xffffff" usbportcfg="0xf000000"
  17. its a maybe and might also depend on the os or linux kernel, it might work if you install something like open media vault i can't recommend any card, usb3 is onboard for pretty long now and beside my ancient nec/renesas card i only bought a VIA/VLI based card (also years ago) and i would avoid these cards but i guess there are different chipsets now like Fresco Logic or ASM (but renesas seems to be still offered so the old via chips might be offered too)
  18. if you just want to pay with it you can use oracle virtualbox and install as VM for a real system that is supposed to be reliable a 10 year old hardware might not be a good choice, also after such log time there is also a lack of performance to expect
  19. then maybe loader 1.02b and dsm 6.1? https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/
  20. the usb3 chip is a NEC D720200AF, i do have a pcie card with a nec chip and it needed a firmware update to work properly, maybe that's your problem here, might be hard to get a update for a integrated component when there is not bios update containing it https://xpenology.com/forum/topic/13022-n40l-usb3-pci-e-card-not-functioning-in-dsm-62/ the board of your systems has something that looks like pcie 1x slot, maybe try to add a newer usb 3.0 card? https://www.smallnetbuilder.com/nas/nas-reviews/31962-thecus-n7510-nas-server-reviewed?start=1
  21. anything about "Hand-off" usb feature in bios?
  22. did you try with the additinal two "f", cant hurt to up the possible usb port number, ports not in that "bitmask" are not used in dsm i counted the "x ports detected" in your dmsg and thats more, as for sata, the system sometimes sees more then whats soldered to the systemboard
  23. IG-88

    DSM 6.2 Loader

    1.04b 918+ no go with your cpu as its to old most likely for 3617 you used loader 1.03b an d that needs csm/legacy mode (also as boot device) https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ loader 1.02b and dsm 6.1 is more easy in that area also you might read faq and tutorial https://xpenology.com/forum/forum/83-faq-start-here/ https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/
  24. is the front plugged usb devices shown with "lsusb" ? also if couting the usb port found messages there are 20 ports found so the 4 times "f" (akak4 ports) is not enough so make it two more "f" in the usbportcfg esataportcfg="0x0" internalportcfg="0xfff" usbportcfg="0xffffff000"