extenue
-
Posts
70 -
Joined
-
Last visited
Posts posted by extenue
-
-
Hi Peter ,thanks for the update , looks like I was not enough patient , post reboot post DSM installation , ping came back after maybe 10 min (not sure exactly but was quite long) , after that , status has been stuck "demarrage des services" = "start of services" for another 10 min I would say
Right now , I can see Launching built-in packages , so maybe all this is expected , my first install with your loader was an upgrade , this times it's a fresh installation so maybe that explain why it's so long post reboot post DSM installation.
Else , yes , I have decided to reduce my RAID5 from 5 disks (4 from the bays + 1 from top) to 4 disks (all from the bays)
Once stabilized , I'll attempt again to plug that external SSD via USB to see if same issue happens again or not ..
-
1
-
-
Peter , please help , I don't know when you have updated your repo but now your loader is giving 64570 and no more 64561.
When have you updated your repo ?
Now , I am not able to bring back to life my proliant N54L , all is fine until DSM installation (post build , Synology Assistant see my N54L and propose me to install it on uploading a PAT) but after installation , on next reboot , then network does not work , all looks good on console but NAS is not found.
To validate this , could you please somehow add a line in your menu to install 64561 ? if that's the case then can you share the PAT if you have it as I have been unable to find it anywhere
Thanks & Regards
XT
-
On 5/25/2023 at 12:13 AM, unmesh said:
For anyone that is running on a N40L or N54L, did you have to manually adjust the sata related parameters in user_config.json to get the machine to boot into DSM?
Mine was running on bootloader 0.8.0.4 but is not booting DSM on the latest 0.9.4.6
your issue is most likely due to missing JOT mode on new version of TCRP (that's my theory) , please read page 34 & 35 from this post https://xpenology.com/forum/topic/60130-redpill-tinycore-loader-installation-guide-for-dsm-71-baremetal/page/35/
-
2 hours ago, extenue said:
Salut ! est ce qqun aurait un lien pour DL 7.2-64561.PAT pour DS3622XS+ SVP ?
j'en ai besoin pour reinstaller mon 54L mais impossible de trouver ce PAT , le seul que je trouve est le 570 qui ne fonctionne pas
Merci !
sinon j'en profite pour raconter mon experience .. avec le loader de picopico , je n'avais pas le réseau , j'ai découvert un autre loader visible dans ce thread https://xpenology.com/forum/topic/60130-redpill-tinycore-loader-installation-guide-for-dsm-71-baremetal/page/35/ , j'y raconte mon experience page 34 et le developpeur a meme MAJ son loader pour supporter 7.2 sur nos 54L , merci a lui ! car oui il s'avere que nos N54L necessite le JOT mode , par ailleurs j'ai découvert au autre thread ici qui parle de succes avec la 0.9.3.0 , j'en concluerais (peut etre) que jusqu'a la 0.9.4.4 , le loader de picopico integrerait ce fameux JOT mode ?
Big question : comment integrer le JOT mode dans le dernier loader de picopico ?
en résumé , on peut avoir DSM 7.2 avec ce loader M. Shell , mais pour moi il est bugué , comme indiqué dans le trhead en question , je peux planter le loader rien qu'en branchant en USB un SSD dans un boitier externe alors que RAS pour 2 HDD externe.
Je cherche donc un autre loader , compatible DSM 7.2 , autre que M. Shell ...
Sinon , mon BIOS n'a jamais été resétté avec le loader de picopico , le C1E reste sur désactivé , j'arrive pas a comprendre pourquoi sur un meme matos on obtient pas les meme résultats avec les memes loaders ... par ex en DS3622XS+ , l'usage RAM est inférieure a 1 Go donc rien a voir avec Gastonzz
Tchuss
XT
juste pour rajouter que dans l'autre thread que je reference (M. Shell) , le developpeur explique que le N54L n'est pas compatible TCRP Friend , je vous encourage a lire les page 34 et 35 car ca aide , somehow , a comprendre ce qu'il y a de spécial avec notre bon N54L ..
-
On 6/4/2023 at 6:38 PM, olomen said:
J'ai resolu avec le la version 0.9.4.4 et le comandes suivantes
./rploader.sh identifyusb now
./rploader.sh serialgen DS3622xs+ realmac
./rploader.sh satamap now
./rploader.sh build ds3622xsp-7.1.1-42962Repondre N
Je suppose donc que tu es en DSM 7.1 , avec le loader de M. Shell tu peux avoir la 7.2
-
Salut ! est ce qqun aurait un lien pour DL 7.2-64561.PAT pour DS3622XS+ SVP ?
j'en ai besoin pour reinstaller mon 54L mais impossible de trouver ce PAT , le seul que je trouve est le 570 qui ne fonctionne pas
Merci !
sinon j'en profite pour raconter mon experience .. avec le loader de picopico , je n'avais pas le réseau , j'ai découvert un autre loader visible dans ce thread https://xpenology.com/forum/topic/60130-redpill-tinycore-loader-installation-guide-for-dsm-71-baremetal/page/35/ , j'y raconte mon experience page 34 et le developpeur a meme MAJ son loader pour supporter 7.2 sur nos 54L , merci a lui ! car oui il s'avere que nos N54L necessite le JOT mode , par ailleurs j'ai découvert au autre thread ici qui parle de succes avec la 0.9.3.0 , j'en concluerais (peut etre) que jusqu'a la 0.9.4.4 , le loader de picopico integrerait ce fameux JOT mode ?
Big question : comment integrer le JOT mode dans le dernier loader de picopico ?
en résumé , on peut avoir DSM 7.2 avec ce loader M. Shell , mais pour moi il est bugué , comme indiqué dans le trhead en question , je peux planter le loader rien qu'en branchant en USB un SSD dans un boitier externe alors que RAS pour 2 HDD externe.
Je cherche donc un autre loader , compatible DSM 7.2 , autre que M. Shell ...
Sinon , mon BIOS n'a jamais été resétté avec le loader de picopico , le C1E reste sur désactivé , j'arrive pas a comprendre pourquoi sur un meme matos on obtient pas les meme résultats avec les memes loaders ... par ex en DS3622XS+ , l'usage RAM est inférieure a 1 Go donc rien a voir avec Gastonzz
Tchuss
XT
-
too many issues , I don't know what's going on , I can build loader , but once I install DSM , the installation is always fine but no network on next reboot , tested two times.
too much issues , I need to find some alternatives , is it possible to have that jot mode with another loader ? sorry to ask but I need to try something
something must have changed on the repo ? why it's not working now anymore whereas all was ok few days ago ? nothing has changed on my end ..
EDIT : my bad I think sorry ... the PAT I am using is DSM_DS3622xs+_64570.pat whereas build is for 64561 .. I forgot DSM has been updated recently , sorry , I guess all will be fine with 64561 ,I hope I can find it somewhere
EDIT 2 : unable to find 7.2.64561 , does anyone can give me a link please ? for DS3622XS+ , thank you !
-
18 hours ago, extenue said:
Hi Pocopico ! congrats for your hard work
all is fine under Storage Manager , I think the slowness are due to the high temperature , I am more concerned about what happened before , I've more or less reproduced the same problem on pluggin that SSD on new build , it has never been recognized , then I have seen similar message at this morning saying to connection has failed and I had to try to reconnect to DSM ... I have not rebooted since , maybe on next boot it'll be same
anyway , I know the data can't be lost , I have reconfigured what I have lost (mount , etc ...) , next time I'll backup settings from DSM ...
here we go ! on next reboot = same thing , DSM has the status of "not installed" with synology assistant , so issue is reproducible : I plug that SSD via USB and on next reboot no more DSM
-
internalportcfg="0xffff"
I don't know at all if that's good or bad
-
1
-
-
Hi Pocopico ! congrats for your hard work
all is fine under Storage Manager , I think the slowness are due to the high temperature , I am more concerned about what happened before , I've more or less reproduced the same problem on pluggin that SSD on new build , it has never been recognized , then I have seen similar message at this morning saying to connection has failed and I had to try to reconnect to DSM ... I have not rebooted since , maybe on next boot it'll be same
anyway , I know the data can't be lost , I have reconfigured what I have lost (mount , etc ...) , next time I'll backup settings from DSM ...
-
ok , meanwhile I've read that installing / reinstalling DSM do not touch data partition , I have reinstalled DSM 7.2 using your loader and PAT downloaded from Syno portal , all data are there.
I found everything more slow , it's hot now here , more than 30° C in the room
I still don't understand what happened ? from now , I am not sure I'll plug too many HDD at same time .. I can't believe what I am saying ...
EDIT : Thinking about it ... I am now booting on another USB drive which I know is slower than the first one , when any settings are saved in DSM , where this is stored : on the USB key (which I think) or somewhere on system partitions of the disks ? That slowness could be explained by poor performances of the new USB drive ..
and as DSM never appears anymore using first USB Pen drive (loader boot but DSM never came online) , I can imagine a corruption somewhere on the loader , is it possible to troubleshoot this , restore backup to try to come back to previous version or something like this ? any possibility to backup settings from first USB drive to restore to second ?
Thanks
XT
-
something REALLY strange happened
DSM up to date , two external 2.5'' HDD plugged via USB , copy in progress , I plug an external SSD 2.5'' drive from there nightmare began ...
one of the two 2.5'' HDD has been ejected , the SSD is not recognized , quick google research tells me to reboot ... on next reboot no more network , Synology Assistant find the Proliant not configured ?!? , it tried to apply DHCP then said failed ... reboot on build mode, I notice a backup being restored , maybe this happens all the time I don't know , network is recognized , I can access with SSH but I decide to not do anything so reboot on DSM : still nothing found
What should I do next ? do a fresh new build on a second USB stick ? something else ?
Have I lost all my data ?
EDIT : I've decided to redo a build using another USB key , I've verified all disks are seen while I was on build mode , with that new USB key , synology assistant see my Proliant , propose me to download PAT and install it , if I do this , will I loose all my data or is this will just wipe the system partitions on the disks ?
Else , any idea of what I can try to do on original USB disk so DSM can work again ?
Thanks,
XT
-
20 hours ago, Peter Suh said:
Jot is what TCRP looked like before it was once again developed as a FRIEND mod version.
FRIEND uses a separate kernel on top of the JOT kernel once more,
but this kernel has a problem of incompatibility with HP products such as N36L/N40L/N54L that use older AMD CPUs.
So you are forced to use only JOT.
ok good to know for future.
If I may ask , is there something doable to ensure disk can hibernate when not in use ? from what I can see my disks never hibernate even if that's configured on DSM , a quick google research show me it's a known issue but I don't really find any solution , is there a mod or something doable ?
Tchuss
-
et voila !! (oui je suis francais comme toi je crois)
et voila !! thanks m8 ! the upgrade went succesfully
I am curious , do you know why the N54L needs that JOT mode and what is JOT mode exactly ?
Thanks again
-
Hi , sorry for noob questions but I don't feel cumfortable yet about the upgrade
first of all , I have used img from this page https://github.com/PeterSuh-Q3/tinycore-redpill/releases/tag/v0.9.4.3-2 , is that ok ?
Second , to prepare the DSM update , on boot menu from USB key , shall I use Tiny Core PostUpdate (probably not) or Tiny Core Image Build ?
for now I have used "Tiny Core Image Build" and have connected with SSH , I have ran menu.sh and I can see now same as you above in your screenshot :thanks
so to do the upgrade , next step is to do build TCRP 7.2.0 JOT and reboot ? then use hypothetic new menu Tine Core PostUpdate 7.2.0 or nothing or something else ?
Thank you in advance
EDIT : I have used DS3622xsp
-
all is OK thanks for this loader
RedPill TinyCore Loader Installation Guide for DSM 7.1 BareMetal - Page 34 - Tutorials and Guides - XPEnology Community
-
1
-
-
Just now, nicoueron said:
Tant mieux!
Ce bon vieux N54L fonctionne toujours autant et fait toujours des adeptes je vois 😄
Perso ses performances pour mes besoins on eu raison de lui... je suis passé sur un Core i7 avec décodage hard, ça me change la vie.
je suis passé au mini PC a base de Celeron N5105 qui fait proxmox , j'ai eteint mon PowerEdge T20 qui faisait proxmox et rallumé ce bon vieux Proliant pour faire NAS
-
2 minutes ago, Peter Suh said:
I am modifying the program now to make 7.2 possible.
I'll deploy soon and let you know.wow thanks !
-
Alleluia !!
Merci NicoCoueron , j'ai applique les options BIOS par defaut puis appliqué exactement toutes celles visibles dans le premier post , puis reboot , puis BIOS again et la par magie TOUS les disques apparaissent en AHCI PUIS DSM les voit bien
Encore Merci !
-
Thank you for the answer but I don't have same menu , I can only image 7.1 , once DSM boot the network is found but the disks on port 4 and 5 are not seen. I have a N54L with 6 disks (4 internal + 2 located on top of the server) , the 4 are seen but not the 2
under loader , all the disks are seen but DSM only see the 4 - using TCRP , no network is found - using ARC / ARPL , network is found but not the 2 disks
What can you suggest for me to try so all disks are seen by DSM ?
Thanks
XT
EDIT : all good now for the disks , after change in BIOS then all the disks appears under AHCI and now DSM see them.
Remains to understand how image DSM 7.2 on this N54L
Thanks again
-
1 hour ago, olomen said:
Allor la je ne comprend pas....
TC trouve un adresse ip mais il n'existe pas sur le resaux il est connecte su le port 3
bienvenue au club , galere Xpen sur Proliant hein ? j'ai eu la meme a un moment donné
je suis en train de tester ce loader
RedPill TinyCore Loader Installation Guide for DSM 7.1 BareMetal - Page 34 - Tutorials and Guides - XPEnology Community
Release v0.9.4.3-2 · PeterSuh-Q3/tinycore-redpill · GitHub
j'ai du réseau mais pas tous les disques malgré le Jot Mod Loader sensé résoudre les probs Xpen avec le N54L (=N36 =N40) , N54L est pas compatible avec TCRP Friend ...
-
7 hours ago, nicoueron said:
Tous sont configurés en AHCI?
as-tu essayé avec une autre clé usb?
oui et oui
EDIT : en fait dans le BIOS dans AHCI settings , 4 HDD sont detectés et pas ceux sur Port4 et Port5 , ceci étant , une fois le loader chargé , tous les disques apparaissent avec un fdisk -l
il faut peut etre que je fasse une croix sur les 6 disques en bare metal sur le N54L ... pour l'instant je suis en proxmox , j'ai 5 disques , je ne peux pas rajouter de 6 eme car pas assez de SATA virtuel d'ou la volonté de passer en bare metal pour monter a 6 ... donc pour l'instant avec redpill , je ne peux pas remonter mon RAID5 de 5 disques , dégouté
EDIT 2 : en relisant le premier post et en revoyant les screenshots (merci d'ailleurs !) je vois que le disk sur le port 4 est détecté contrairement a moi , je ne vois pas ce que je manque dans les options par contre
j'ai bien le meme BIOS moddé (flashé a l'epoque y'a 10 ans environ)
-
Thank you for this
Is it possible with this loader to image DSM 7.2 on N54L ?
XT
-
Hi Community,
I Have a Proliant N54L , with TC loader , the 6 disks (4 internal + 2) are seen but DSM do not see the network , with ARC and ARPL loader , the network (internal NIC) works but only the 4 internal disks are seen.
Except purchase another NIC , any idea of what I should try ?
Thanks !
XT
RedPill TinyCore Loader Installation Guide for DSM 7.1 BareMetal
in Tutorials and Guides
Posted
ok , recap , when I was in 7.2.64561 (setup is RAID5 with 5 disks : 4 internal HDD from the bays + 5th located at the top plugged to either internal Sata or external) all was working fine.
To do some copies , I've plugged two other external HDD 2.5 via USB , no problem whatsover , the nightmare began after have plugged a third external drive , via USB port on front , SSD using this , from there I received error message , one of the HDD has been disconnected and on next reboot no more DSM ! the loader was dead
I have been able to reinstall a 7.2.64561 and I have been able to reproduce the problem ! this time I have not plugged the two HDD then the SSD but only the SSD and boom loader crashed !
Afterwards I have not been able to reinstall as , in the meantime , you have updated your loader to 7.2.64570
but it took me few hours to realize 
I am now running 7.2.64570 and all is fine , I have not tried to plug that SSD drive ..
Conclusion : all is good for 7.2.64570 BUT loader crashed by two times on two attempts when I was on 7.2.64561 on plugging that SSD external drive ... sorry for that but this is what I have experienced.
Else , I am backuping my data to delete the RAID5 and recreate it but using 4 disks , somehow the management are the two others is different and not all loaders can handle them.
Keep up the good work !
Just curious , any idea why the loader crash after plug that drive ? Picopico has asked me for a settings but I don't know how interpret the result , I think I've read that correspond to a total of 20 disks ..
I'll be happy to help if I can to troubleshoot this , I know now that even if we crash the loader then it's possible to reinstall without loosing any data , once I'll start with a fresh DSM once my RAID will be rebuild then i'll plug that external SSD .... note: this external SSD works like a charm on my windows laptop