Jump to content
XPEnology Community

gnoboot & DSM 5.0-4482 - Experiences?


DerWuff

Recommended Posts

It should be a good beginning to see what's happening when DSM create the dsm.dat and what are error messages.

But how to start? somebody can send logs from an impacted DSM for analysis?

 

I think the easiest way to do is like we did with 4.3, I repack a minimal 5.0-4482 build with only sata/network drivers so everyone can test/debug.

Link to comment
Share on other sites

It should be a good beginning to see what's happening when DSM create the dsm.dat and what are error messages.

But how to start? somebody can send logs from an impacted DSM for analysis?

 

I think the easiest way to do is like we did with 4.3, I repack a minimal 5.0-4482 build with only sata/network drivers so everyone can test/debug.

 

Hi Trantor, happy to test on an HP N54L.

Link to comment
Share on other sites

Trantor wrote:

 

john_matrix wrote:It should be a good beginning to see what's happening when DSM create the dsm.dat and what are error messages.

But how to start? somebody can send logs from an impacted DSM for analysis?

 

 

 

I think the easiest way to do is like we did with 4.3, I repack a minimal 5.0-4482 build with only sata/network drivers so everyone can test/debug.

 

 

 

Hi Trantor, happy to test on an HP N54L.

 

Hi,

 

I will be happy to help too :grin: .

I have a N54L and could put in place an ESXi if needed.

Link to comment
Share on other sites

Until you try to go to DSM

Server is working properly!

After entering unmount drives.

The mount command runs a script overwrites the contents of the fstab file and everything works as before. All checked twice.

But after the second restart, these actions do not help.

For those who still doubt that a pair of The valid serial number and MAC address does not work! (Flashed MAC address in the network card itself)

Link to comment
Share on other sites

Hi there,

 

Here are the results of my investigation around 4482.

 

After some research here and there, I've seen an old error seen before with esata drives :

 

Failed to open /dev/sdc, errno=No such file or directory

/sys/block/sdc/device/../../scsi_host/host*/proc_name

 

It seems that 4482 uses different drivers (or sysfs implementation).

 

When manually rebuilding devices files with mknod, it is possibilie to fdisk it but it's deleted again by some script around /usr/syno/bin/scemd

 

C.G.

Link to comment
Share on other sites

Did Synology updated their kernel or base distribution from 4458 to 4482 ?

 

Gnoboot itself doesn't use the kernel from DSM 5, it still uses 4.x kernel.

 

4458 and 4482 builds use same source files.

I don't know what kernel and/or toolchain gnoBoot use, but:

 

DSM 5.0 and 4.3 use the same kernel 3.2.40.

 

But toolchains are different:

4.3 use gcc420 and glibc2.3.6

5.0 use gcc473 and glibc2.17

 

No time to investigate deeper for now.

Link to comment
Share on other sites

*

THE ONLY SOLUTION:

 

give all the information to compile the kernel , add drivers , ...

 

and do not keep some "secrets" so that there will be more people to experiment and there will be a chance to find solutions

 

the opposite of politics Sir "gnoboot"

 

It is my opinion especially if we know that there are other solutions such as Freenas, Openmediavault, or just a Windows / Linux Server

Link to comment
Share on other sites

the solution can be: strike the forum !

 

when those who believe indipendables types realize that there's' more interested in them ...

 

personally if I do not receive a positive response to my request I would disappear forever

 

translated by google

Link to comment
Share on other sites

Hi,

 

I'm shocked, did you loose the fact that it's just a challenge and not really legal ?

How could you criticize the forum or trantor, gnobot, guys that permit to everyone to have access to an excelllent toy (Xpenology) ?

 

Ok now they don't have really time to work on the new build, that's the life. You are frustated because you have your own data on a dev/hack release of DSM, don't you think it could be more comfortable for you to buy a real syno ? and keep your Xpenology just for backup or to play.

 

If you want to work for build 4482, you have some good information here: http://xpenology.com/wiki/en/building_xpenology

 

I not skill in Linux kernel compile but i thing if we are some of this forum to test and work together we could arrive to do a functionnal build.

 

And once again many thanks to Trantor and Gnoboot for their excellent job :wink:

Link to comment
Share on other sites

Hi,

 

Of course this procedure was for DSM 4.3.

For the 5.x release we need to use different release as Trantor said:

 

4458 and 4482 builds use same source files.

I don't know what kernel and/or toolchain gnoBoot use, but:

 

DSM 5.0 and 4.3 use the same kernel 3.2.40.

 

But toolchains are different:

4.3 use gcc420 and glibc2.3.6

5.0 use gcc473 and glibc2.17

 

You will find some good documentation from Andy here: https://github.com/andy928/xpenology/tr ... umentation

 

Regards,

Link to comment
Share on other sites

Yes big community = big progess

 

First instead of yelling start helping the community (like creating FAQ or updating the wiki / how to or creating a git)

viewtopic.php?f=2&t=2502&start=10

 

There is not "secret" at all. Everything is already online:

 

Synology sources : http://sourceforge.net/projects/dsgpl/files/

Synology dev guide : http://ukdl.synology.com/download/ds/us ... _Guide.pdf

Andy's commits (to patch kernel sources) : https://github.com/andy928/xpenology/commits/master

gnoBoot even released his kernel patch : viewtopic.php?f=2&t=515&start=40#p13873

All my kernel include the .config files

 

 

Deleting your post is showing a very good mentality...

Contenu supprimé : je fais grève
Link to comment
Share on other sites

Thanks Trantor.

 

I read Andy tuto, using http://xpenology.com/wiki/en/building_xpenology guide

Then I built kernel 3.2.11 using DSM 4.1 tool chain and now a second kernel 3.2.11 using DSM 5.0 tool chain.

I'm now digging into DSM_DS3612xs_4482.pat to see how hack synobios.ko. this pat layout is a bit different than one from Andy tuto.

 

In Part 3, Synobios modification, there is a disassembly.

I'm wondering what option has been provided to objdump, I didn't see symbols in ouput like SetMicropId, but I see symbols via srings

 

objdump -t -D -b binary -mi386 lib/modules/synobios.ko

lib/modules/synobios.ko:     file format binary

SYMBOL TABLE:
no symbols



Disassembly of section .data:

00000000 <.data>:
      0:       7f 45                   jg     0x47
      2:       4c                      dec    %esp
      3:       46                      inc    %esi
      4:       02 01                   add    (%ecx),%al
      6:       01 00                   add    %eax,(%eax)
       ...
     10:       01 00                   add    %eax,(%eax)
     12:       3e 00 01                add    %al,%ds:(%ecx)
       ...
     25:       00 00                   add    %al,(%eax)
     27:       00 d8                   add    %bl,%al
     29:       72 00                   jb     0x2b
       ...
     33:       00 40 00                add    %al,0x0(%eax)
     36:       00 00                   add    %al,(%eax)
     38:       00 00                   add    %al,(%eax)
     3a:       40                      inc    %eax
     3b:       00 17                   add    %dl,(%edi)
     3d:       00 14 00                add    %dl,(%eax,%eax,1)

Edited by Guest
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...