Jump to content
XPEnology Community

Eduardo

Member
  • Posts

    145
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Eduardo

  1. 11 hours ago, IG-88 said:

    i was able to reproduce broken raids when hdd hibernation is active, not all disk wake up properly and will result in problems

    initially @richv31 discovered the problem, i might not have recognized it as i usually don't wait that long to to see if a disk goes into sleep (and in most tests i dont have 3 or more disks, often one or two and sometimes not even as raid)  and my own new 918+ system does not use the sas controller anymore, i was going for "native" and that's ahci for 918+ (and that's also working for the other two)

    with the new driver made from 24922 kernel source or lsi's newer source there is no broken raid, the disk seem not to go inter hibernation either, at least not distinguishable, the log show hibernation and instant wake up within a very short time after hibernation, so the effect might only come from the fact that the disk in real life never really switches off and never reaches the state we see with jun's drivers

     

    also there was feedback about 0.13 still showing smart but it already is made with the new drivers - have'nt checked this as i was busy getting nvidia drivers to test so they hopefully can be used independently from intel qsv for transcoding (on all three images)

    Understood.

    I don't think my disks go to sleep. It really doesn't worry me from some years ago.

    At this point, I'm not sure what to do. I'll wait some other feedback before making a decision.

  2. Hi @IG-88
    I've been out last days and this thread and your great drivers change quickly. Now it's easy to get confused among versions.
    J4105B with 9211-8i IT here. DSM 6.2.3-25426 918+. 1.04b loader. extra918plus_v0.11.
    Smart Info and SHR volumes (BTFRS) seem to work flawlessly. 25 days now. 😀
    Just to be sure, is extra918plus_v0.11 unsafe? Should I sacrifice smart info and migrate to extra918plus_v0.13.3?
    Thanks a lot for your brilliant work.

  3. 16 hours ago, tdse13 said:

    Thank you very much. I installed Windows 10 on a small SSD. Unfortunately, I cannot change the mac address. It does not accept my input. Any idea what could be the problem? Thank you.

     

    Did you tried  /s parameter?  Ex: wmac c 7085C2110715 /s

  4. 6 hours ago, tdse13 said:

    I want to change the mac address of my J4105. to use WOL properly. Since  this board boots only in UEFI 64 mode the tools from Asrock do not work anymore. Does anybody have a solution? Thank you.

     

    Sent you a PM.. I forgot to mention you'll need a Windows to do it. You could download and use a live CD though.

    Good luck

  5. 6 hours ago, IG-88 said:

     

    what are your plans on how to use it?

    synology loads cpufreq* modules by itself but how are you intent to use the new module?

     

    Actually I don't think wee could achive an automatic frequency scaling. Only powersave performance userspace here.
    There are some scripts over there to adjust frequency when in userspace. I used one of them some time ago. But couldn't we get a new ondemand governor with  cpufreq_ondemand.ko?

  6. Yo creo  que tienes dos opciones.  La segunda es más aconsejable desde el punto de vista de la seguridad.

     

    1.- Más o menos, lo que dice ese  video. Habilitar el acceso SSH al usuario root:

    - Establece contraseña del usuario admin. Esa misma contraseña debe ser la de root.

    - SSH como admin y ejecuta sudo -i   Pon la contraseña de admin.  Y pulsa intro.

    - Introduce   synouser --setpw root ppppp    Donde ppppp debe ser la contraseña de admin. No vale otra.

    - Ejecuta  cp -p /etc/ssh/sshd_config /etc/ssh/sshd_config.orig && sed -i 's/\#PermitRootLogin prohibit-password/PermitRootLogin Yes/g' /etc/ssh/sshd_config

    - Reinicia.

    El usuario root ya debería poder entrar SSH con la contraseña de admin.

     

    2.- Mediante elevación de sudo en shell de WinSCP del usuario administrador.

    - SSH como admin y ejecuta sudo -i   Pon la contraseña de admin.  Y pulsa intro.

    - Ejecuta cp -p /etc/sudoers /etc/sudoers.orig && sed -i 's/.*administrators ALL=(ALL) ALL/%administrators ALL=(ALL) NOPASSWD: ALL/g' /etc/sudoers
    - En la sesión guardada de WinSCP, avanzado: Campo shell, estableces sudo -i -u root  y en el campo usuario pones el usuario admin.

  7. 9 hours ago, IG-88 said:

    as a newer mpt3sas.ko made no difference and jun's  mpt3sys did not work i assumed the difference might be on level lower so i kept the new mpt3sas v27.0.0.1 and replaced my own new complied version (synology kernel source 24992) of scsi_transport_spi.ko, scsi_transport_sas.ko, raid_class.ko with the files from jun's original extra/extra2

    test looks good, no problems loading mpt3sas and there are smart infos now

    Nice! This new way can be useful for other hardware too.

  8. On 4/21/2020 at 11:38 PM, IG-88 said:

    bare metal install?

    i dont have this on my system with a 9211-8i (IT), there are smart values, i can can run the smart quick test and get a healty

    the driver used atm is from kernel 4.4.59

    i will try to compile a more recent and see it it works, if not i still can put back jun's driver from initial 1,04b loader, should also work

    Hi IG-88,

    All working fine but little smart info issue. Which files could we try  to put back from Jun?

  9. 35 minutes ago, IG-88 said:

    should both work with juns 1.03b extra.lzma

    when updating from 6.2.2 and replacing the 6.2.2 extra.lzma with the one from the original loader and having reboot/shutdown problems then just empty /usr/lib/module/update/ and reboot

    the "older" extra.lzma will not overwrite (6.2.2) drivers that where added later (by my extra.lzma) so in same cases they might be loaded an crash on boot

     

    Not sure to understand. How to achieve Realtek 8111F NIC drivers then? Not on Jun extra 1.03b.

  10. Outcome of the installation/update: SUCCESSFUL

    - DSM version prior update:  DSM 6.2.2-24922 Update 6

    - Loader version and model: Jun's Loader v1.04b - DS918+

    - Using custom extra.lzma: YES (v0.1 for 6.23)

    - Installation type: Baremetal Asrock J4105B-ITX, on board lsi9211 passthrough.

    - Additional comments: SMART info is not showing.

  11. On 12/31/2019 at 2:46 PM, IG-88 said:

    just remove the button.ko and evdev.ko  from /usr/lib/modules

    there are new one in /usr/lib/modules/update already

    the plugin is not aware of the changes of 6.2.2 and blindly overwrites with old 6.2.0 files

    the rest is fine, after removing the old/wrong files and rebooting your system should be able to use acpi power off

    i'm using this with my dsm test vm's in virtualbox

     

    the plugin needs to be extended for 6.2.2 and needs new button.ko/evdev.ko files (can be extraxted from my extra.lzma's)

     

    Don't do that on 6.2.3   Old drivers working again. Just install POWERBUTTON_6.2-0002.SPK. It should work.

    • Like 1
  12. 18 minutes ago, IG-88 said:

    one "safe" solution might be to boot up open media vault from a external (additional) source/disk, that will give you network access to your raid (data) volume - if you need files from there - thats my personal plan "f" if i loose access when dsm does not boot (if your raid is damaged then you are beyond "f")

     

     

     

    Interesting. Should it work when SHR used?

  13. On 1/31/2020 at 5:57 AM, gadreel said:

    I might be wrong but I remember that the first time I installed DSM it was notifying me about any DSM and package updates.

     

    DS918+ has 6.2.2-24922-5 since 15/01 and I do not get any notification. Every time I go to Control Panel I get "Your DSM Version is up to date".

     

    Same goes for packages. Hyper Backup package version 2.2.3-1117 was released 2 months ago and I still have 2.2.2-1113 even on the control panel it is set to automatically update the packages.

     

    Any idea what is going on?

    Same here. I'm digging on to not avail.

×
×
  • Create New...