Transition Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About mario661

  • Rank
  1. Hi All, With this tutorial, I am able to compile kernel modules contained in the linux-3.10.x download. However, I need to compile a modified module from the backports file ( NAS GPL Source/15152branch/bromolow-source/). Can someone give me a hint on how to proceed?
  2. You can find all the updates here:
  3. OK. Thanks, that works. It will cry about dismounted volumes, but after a reset it works fine. Now creating custom packages for this beast. :-))
  4. Hi, I need to do some research on an old DSM version. Is there (still?) a bootloader available for DSM5.2 build 5967 update 8?
  5. mario661

    DSM 6.1.x Loader

    Hi all, I am running the loader for DSM6.0.2 (update 9) with Jun's loader and it runs fine for me, but there is one thing I can't seem to find how to fix. I can set the CPU scaling to "ondemand" and it will scale back my (4) cores from 3200 to 1600. (Intel i3 3220). However, after less than a day, it switches back to "performance" without any action, reset or tasks... Anyone any pointers where I can set the CPU governor so that it keeps the setting? Thanks for the help.
  6. You need to connect your PC to a monitor and log in as root. Try your old password. If that doesn't work, you can try the default password that is generated by Synology. You will have to look on the web since you need to generate this password. I do think it's specific to date. Once you get into your box, you can try to troubleshoot what doesn't work and why. If all else fails, the priority is to get access to your data. Install a clean Ubuntu on another PC. Once that's done and you have installed the dm-raid tools as well, try hooking up your DSM drives IN ADDITION TO your ubuntu drive and see if ubuntu wants to see the data on it. Do NOT reinstall, initialize, basically everything that wants to do something permanent to your drives. If you have PLENTY storage on another PC, make disk dumps (dd and ddrescue) which you can use to mount your drives. Sorry I can't help you more than this, but it will give you a starting point.
  7. Hi, This is all the knowledge I have, try these steps. Unfortunately if this does not work, there's nothing I can help you with. Make sure you have mdadm and lvm2 packages installed in your Ubuntu Linux. For my test, I did an installation of Ubuntu and made sure NOT to use Logical Volume Management so that I was sure that my tests only show results of the synology volume. Don't know how bootable USBs show up, but I guess that will not be an issue. FIRST OF: become and stay(!) root by typing "sudo su -" (don't forget that last minus-sign) and create a mount point you can use by creating a directory: mkdir /mnt/syno mdadm --detail --scan Try this, see if your RAID details are visible fdisk -l Check if you see a mdxxx device. In my test, I saw a /dev/md127. Try to mount it, create a mount point somewhere (remember that mkdir /mnt/syno???) and try to mount: "mount /dev/mdxxx /mnt/syno". But probably you will get an error (unknown filesystem type 'LVM2_member') lvmdiskscan This will output all kinds of info. You are hoping to see something like /dev/vg1000/lv and-or /dev/mdxxx and "1 LVM physical volume" lvdisplay You should see something like "LV Path /dev/vg1000/lv". vgdisplay Should display the volume name lvscan Should return the volume of your synology. When you see "Active", you are as good as set. If you see your volume, but "INACTIVE", try "modprobe dm-mod" followed by "vgchange -ay" and run lvscan again. If it's ACTIVE (for example, you see the output "ACTIVE '/dev/vg1000/lv' [xxxx GiB] inherit" you should be able to mount it with mount /dev/vg1000/lv /mnt/syno That's all the info I can give you. I wish you all the luck!
  8. To answer myself (ashamed ) the error has (in my case) no effect on network connectivity. I was able to find my 'NAS' and install the software. If you can't find your NAS, your problem might be due to something else.
  9. Hello all, I keep getting this error message when Nanoboot tries to initialize the NIC: "Error internal NIC devices 2 does not equal to internal NIC number 4" I found a post that recommended changing the netifw flag. I do have a value that looked a lot like it, but changing it (everywhere) did not make a difference (regardless if I did 1, 2 or 4). The installation is on-iron (so no virtuals). I also saw the same problem in the Chinese forum (I could recognize the error) but there were no replies there either. Can anybody point me in the right direction? Thanks.