IG-88

Members
  • Content Count

    3,705
  • Joined

  • Last visited

  • Days Won

    169

Everything posted by IG-88

  1. there is a new thread in tutorials https://xpenology.com/forum/topic/42765-how-to-undo-a-unfinished-update-623-to-624-no-boot-after-1st-step-of-update/ main points beside deleting the update files are to reset/delete the two VERSION files on disk AND reset the zImage and rd.gz on the loader to the 6.2.3 versions the rd.gz on the loader also contains a VERSION file, the loader checks the VERSION files on the loader and on disk and if one is still 6.2.4 it will not downgrade
  2. there is a section "Tutorials and Guides" in the forum https://xpenology.com/forum/forum/36-tutorials-and-guides/ the normal howto for installing references to extra.lzma and its the same for 6.2, with 1.04b 918+ its extra.lzma AND extra2.lzma you need to replace https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/ accessing the partitions got a little more complicated with newer win10 versions (but maybe use the method i added at the end of the thread) https://xpenology.com/forum/topic/29872-tutorial-mount-boot-stick-
  3. beside the mounting with partitionwizard there is a better way to use the tool to get easy access to the loaders 1st and 2nd partition start the tool, right click on the loaders main entry where is states GPT, convert it to MBR, apply to execute the oüeration, do the same again but revers it, convert it to GPT and click apply now windows 10 can access both partitions as its supposed to be and you don't need any additional tools and with that its also possible to get the MBR version of the loader (often needed for HP desktop's), no need for a special download of the loader
  4. yes, you need them to get the devices back just copy the new ones (0.13.3) to your loader and reading the first post of the thread would explain why ("... basically synology reverted the kernel ... i completely removed jun's i915 drivers ...)
  5. yes, you activate ssh in dsm web gui and use putty maybe install package synocli-file and use midnight commander (mc) to access the files (F3 is view a file iirc) /var/log/ dmesg and messages are the files to look into
  6. its usually suggested to test it to some extend, i would at least run memtest over night. install dsm to a single hdd, copy some date and look into the logs in /var/log/ if there is anything unusual
  7. if you started dsm with 1111,1111 too then it seems like every other vid/pid then the real one does work, pretty odd as its usually the other way around i guess thats something only jun himself could answer as its seem closely related to how the loader works (code wise)
  8. interesting, what do you see as usb vid/pid when you use a live linux from the usb in question on the CUS (checking if bios of CUS does anything unusual to usb device)? wrong vid/pid would also prevent dsm from starting properly (not just installing) - at least on my systems, it does not show up in network and serial console show "mount faild" i doe remember some people having vid/pid right and getting error 13 on install can you check one anotheer wrong then 0000/0000 like 1111/1111 just to make sure 0000/0000 is not special?
  9. for sure, if the btrfs file system is damaged just using a different or new installed OS in is not going to change that you can keep the system and delete the raid, but finding the source of the corruption is still to do and might be the more important task for now, without fixing that even trying to repair the file system in any way might be a fruitless effort
  10. the usb flsh drive itself is just for loading the kernel, dsm even unmounts the usb after starting dsm i see some possible sources 1. the usb device itself is producing some kind interference to the system - you could check that by using the old usb again, check if the problem is there and then remove the usb and check again, as long as you dont reboot the nas the usb is not needed 2. driver problems, maybe you used a different extra.lzma containing different driver versions (mainly nic driver) - but i thing thats unlikely also to make sure there are no other interference's
  11. wouln't you need to check the lvm volume for a btrfs file system instead of md4? MD -> LVM -> filessystem (as there are logical volumes i guess you had a SHR) btrfs check /dev/vg2/volume_2
  12. the m.2 slots on these cars are exclusive sata so there is no gain in having m.2 as it would just have the sata limits as a normal 2.5" drive you can get jmb585 cards cheaper when buying over amazon from china or use aliexpress or just look for a 88se9230/88se9235 card (that is not pcie 1x layout) should be the same price as your highpoint card chipset onboard is usually ok, and if there a re bandwidth limits on a added card (like pcie 2.0 and low pcie lane count) the a better to have less drives on that added card no use at all as its already dea
  13. 1.04b will work but you should read some things (you cant install dsm exclusive to your ssd) https://xpenology.com/forum/forum/83-faq-start-here/ https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/
  14. if you did not use any specual extra/extra2 for 6.2.2 (just the default from the loader) then 6.2.3 should at least install, to get i915 working you would need my extra/extra2 from here https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/
  15. i do have all the usual braodcom drivers for dell in my extra.lzma i guess yours is BCM5720 and that should be working with tg3.ko if you have pci vendor and device id i can check if its in the driver imho it should work, try 3615 and 918+ (r430 seems to be haswell, so 918+ should work) any intel based will do, there seem to be a lot hpe quadport intel nic's around, maybe you can get one for cheap
  16. download loader 1.02a and use then vmdk from that one, its a text file that works as wrapper for the img, can also be used with 1.03/1.04 just open it with a editor and you will see
  17. beside this with just 4 disks you will use onboard sata for sure (ahci as driver), no problems with this when using disk hibernation
  18. download loader 1.02a (zip) and in there is the vmdk, its jsut a text that can be used with any (even newer) *.img just open the file with a editor and you will see
  19. i'd suggest a jmb585 based card in the pcie 16x slot (that has pcie 3.0, the other slots seem to be 2.0) https://xpenology.com/forum/topic/35882-new-sataahci-cards-with-more-then-4-ports-and-no-sata-multiplexer/ i guess so, not much choice for >6 onboard, maybe a used system is a option 88SE9128, sees extremly old silicon, if anything then use 88se9235 two pcie 2.0 lanes and 4 ports, if you just want to use two atm there is no bandwidth problem at all (pci4 4x slot with pcie 2.0 on you board) if you use 3617 as base you could also use a lsi
  20. maybe this one? https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/ but thats specific for scsi/sas controller when using disk hibernation on 918+ the newly compiled driver (no smart, no sn) does not have this problem but makes disk handling more or less impossible as you cant identify disks properly in the gui and cant user smart data to determine the disks condition
  21. if you look at my screenshots (they where intended to give a little guidance, 3rd picture) there is filesystem and there should be your btrfs you can mount with omv you usually dont do things on the command line, its intended to be used in the web gui after mounting it you can create a share under smb/cifs and acceess it the way you most likely do (there is also nfs and something for apple, OMV has online help and even a 161 pages documentation, openmediavault-readthedocs-io-en-stable.pdf) AAAAND? what was the result, maybe it was not both 6.2.3? when st
  22. thats just normal SATA3 no nvme is pcie and if you bring that into connectot for hdd's its called U.2 the m.2 slot can have more types of connections usable for devices then just pcie https://en.wikipedia.org/wiki/M.2#Form_factors_and_keying if you have a sata ssd and m.2 with m or b+m key then there might be sata on the connector too and you could get it to a normal sata connector by a adapter (link above) or you use the pcie to to do the same as with a normal pcie slot and a sata controller, the sata controller is just smaller and more fragile
  23. thats what backup is for and the scale depends on then work done and the kind of data (juggling 8k videos needs more space then a photoshop project or some office documents in most cases the really important data is just e few TB and the daily amount is not that much have the data on your computer, backup that to nas (daily) and then backup the nas (weekly) its also possible to use a usb hdd for backup of important data, it does not have to be a 2nd nas you can read on the internet about recovering btrfs and we have some cases here in the forum (2-3?) you can sear
  24. like this https://geizhals.de/?cat=hdssd&xf=4832_4 and then take the exact product code, but there only seem to be max 2TB for sata one a other way is to use a (mechanical) adapter to get the sata connector from the m.2 https://www.amazon.com/SATA-NGFF-Adapter-Power-Cable/dp/B01FE8NKC2/ or use a m.2 card with pcie connected sata chip like asm1061 or similar and use a normal sata 2.5" ssd
  25. i was more thinking of buying a used board like from ebay or a company selling used hardware when looking for using a pcie card that is a possible solution (one of the adapters with a 25cm cable https://www.amazon.com/ADT-Link-Riser-Gen3-0-PCI-Express-Extension/dp/B07Z4QR598/ the flex cable gives some freedom to place the card in the housing, there are m.2 adapters with a pcie 4x slot soldered to it but they will give you some headaches about mechanical problems (space the pcie card takes and stability of the thin board) sounds like the only map the sata port to m