• Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About madhits45

  • Rank
    Regular Member

Recent Profile Visitors

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

  1. madhits45

    DSM 6.2 Loader

    The docs on XPen have improved so much since DSM 5 when I started. I never really relied on DSM 5 and it was just something to play with, never even stored data cuz I did not trust it. Before now I did what you said and always used 1 huge drive that I just backed up and threw in a corner till I needed it. Then I found Surveillance Station and a docker VM. Now I actually need it up and running 24/7. I also looked at OMV and considered it a lot, It has also improved since I last looked. I wonder if BTRFS can be recovered with OMV? I know there was a lot of talk with BTRFS came out th
  2. madhits45

    DSM 6.2 Loader

    Wow Thank you for all the detail. I forget this when I test for a new update and I'm so lucky this update went ok this time. I'll take down this note for updating next time. So awesome you explained it, i knew it had to be there. I'm starting to depend on my xpenology and updating becomes very dangerous if your potentially going to loose all your storage and have to start from scratch.
  3. madhits45

    DSM 6.2 Loader

    Your loader must store the DSM version on the USB right? I have this procedure when looking at a new update. 1. Before I update DSM version I like to install the newer DSM on a blank drive removing all my NAS drives before to test the new DSM. 2. If successful I unplug that drive and go back to all my original nas drives and do the update, if it fails I dont do the update. Now the above would appear to work BUT it seems DSM is aware of me doing my drive swap & update and the only place that could possibly store any info like that is the USB. Is ther
  4. - Outcome of the update: SUCCESSFUL - DSM version prior to update: DSM 6.2.1-23824U1 - Loader version and model: Jun v1.04b - DS918 - Using custom extra.lzma: NO - Installation type: BAREMETAL - Gigabyte GA-H270N - Additional comment: Restart works, so do both NIC cards. So far so good. I plan to do the update again but this time on my already installed HD with 23824U1.
  5. The problem is i have to many sata drives and just a few IDE, so the mix works we'll the way it is. If I was to move the 1tb drives to the sata controller id just end up with the 500gb drives on the IDE. So it really does not matter. This is my secondary nas, I have a newer machine that I expect better support on. This one is simply duplicate critical files for disaster recovery.
  6. I know its actually the controller I'm interested in because I have a few IDE drives but also sata to IDE adapters that allow me to use 1tb drives with this via raid controller. So I have 2x 650gb IDE drives and 2x 1tb drives that work with sata to IDE adapters on this via controller. The board also has 4 sata ports but they only support unto 500gb drives which is odd, since the via can handle larger drives with the sata to IDE adapter.
  7. ohh no, maybe Jun can help with this since it seems pretty high level.
  8. UPDATE: Looks like the issue is also faced in Spanish section see: module loads to late in the startup process, seems to be the issue.
  9. IG-88.. Here is the output. unknown symbol, could it be that it did not ID the hardware correctly? dmesg | grep -i via [ 20.680059] pata_via: Unknown symbol syno_libata_index_get (err 0) [ 46.669469] via_rhine: v1.10-LK1.5.1 2010-10-09 Written by Donald Becker [ 46.669475] via_rhine: Broken BIOS detected, avoid_D3 enabled DMESG MORE dmesg | more [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] L
  10. Just had an idea, could this be a driver ID issue? IE my chipset is not in the driver index and thus it wont ID it to load, ive seen that before in windows. Perhaps its happening here, thoughts? Ill report back after I get into SSH of this box, trying to install DSM 6.1 now.
  11. I know this is a dumb question, but where is the log? On the USB or inside DSM?
  12. UPDATE: It did not load the VIA driver again. Same problem as 6.0.2? Any ideas? I confirmed that AccessData FTK Imager saved the changes to the image. I used OSFmount to see that the extra.lzma and the grub.cfg were written correctly. Its something with the driver, it simply wont load. I get into DSM via find synology and it says no hard drives. The network driver is loading up though, so that's something.
  13. OK yeah I did that all correctly it just won't lock the drive and thus won't let me save the img. I think AccessData FTK Imager is working so ill stick with it or switch to disk utility on the mac. Ok Ill stick with 1.02b I've tried to repack that LZMA myself but could not find the VIA_PATA.ko recompiled for the kernel in 6.1, so i'm stuck there. Do you have a link to an updated driver pack for 1.02b that has the VIA_PATA.ko? Sure here is the link to my main board specs: Its not a super