asheenlevrai

I meant that as a question. I can no longer edit the OP, though.

Hello, I have this rig (see specs below) and now I received a warning message about filesystem error(s) on Volume1. Storage Manager tells me to run a file system check. However this fails every time (after ~1 minute) with this error message: The system could not complete the file system check on Volume 1 because errors occurred. You can check Log Center for more information and try again later. If this issue persists, please contact Synology Technical Support. The Log Center lists the following: - System ran [ext4 filesystem check & repairing] on [Volume 1]. Exit code: [4] I also get the following logs: - File system error was found on volume [1]. - [ext4 filesystem check & repairing] completed. System reactivated [Volume 1] and related services. Do you have any advice about how I could solve this problem. Currently, files on Volume1 seem to be available normally. PC specs: - Gigabyte GA-z87-hd3 (BIOS version: F8) - i7 4770s - 4x2GB DDR3 1333 - 9x 12TB Seagate Ironwolf (6x on MB, 3x on PCIe AIC) : Setup as RAID5 on 8 disks +1 hot spare - 5ports sATA3 PCIe3.0 x4 AIC - 550W PSU - DSM 7.1-42661 update 1 (Model "DS918+")

I also believe that it would make a whole lot of sense if ARPL and TCRP merged at some point (or if all devs would collaborate on a common solution), but I guess @pocopico answered this in post #20. Even though I don't see the logic behind it, it's definitely the dev's choice to do what they feel is the best (for them).

I believe what he meant is that not all apps that used to work in DSM6 will work in DSM7. Some of them reached EOL and others were replaced. I don't have a list (probably Synology published one at some point), but I know that, for instance, there was a Dokuwiki package available in DSM6 Package Center and they stopped offering the package in DSM7 (You need to install DW manually on your Synology NAS since DSM7 if you want it). AFAIR there was also some major changes for Synology Photo and related apps. Best, -a-

Hey What is the current status about hibernation? supported? broken? Thanks

Hello @Sak1s Is this trick "universal"? I need to enable hibernation on the following rig: - DS3622xs+, TCRP 0.9.3 with friend, DSM7.1.0-42661 (I'd like to upgrade DSM7.1.1-42962 if that's possible, still looking into it) - bare metal - Asus MB with Z77 chipset - i7-3770 (Ivy Bridge) Does hibernation only spin down the disks or can it also stop the fans? (case fans, CPU fan, ...) Thanks -a-

Any way I could mark this thread as [solved]?

Thanks a lot @rojoone2! 🙏 For some reason the PC was booting in legacy mode instead of UEFI. Changing this setting in BIOS fixed the problem

nope... same issue when using DS3622xs+

oh.... My CPU is not Haswell (4th gen). It's 3rd gen. I should chose DS3622xs+ instead of DS918+ 🤦‍♂️

Thanks @rojoone2 🙏 I used this image file for TCRP: https://github.com/pocopico/tinycore-redpill/releases/download/v0.9.3.0/tinycore-redpill-uefi.v0.9.3.0.img.gz

Thanks a lot 🙏 Sorry for not having provided the necessary information. (I haven't solved this yet) Do you know what can cause this type of error message? The specs of the new machine are: - i7 3770 - 16GB DDR3 1333 (4x4GB) - Asus P8Z77-M uATX MB (z77 express chipset). BIOS v2203 - 7x 1TB sATA3 HDD (Seagate Barracuda). 2 on MB sATA3 ports (4 sATA2 ports free, unused), the 5 others are on a 5-ports sATA3 AIC (see below) - 5-ports sATA3 PCIe3.0 x4 controller (Chipset: JMicron JMB585) - 450W PSU (xilence) Please let me know if there is any information that I failed to provide. Thanks again 🙏 -a-

Hey I just made a USB launcher using TCRP (DS918, using the tutorial from @flyride) for a new machine (bare-metal). Upon 1st boot on the USB dongle, I get the following: Error: symbol 'grub_disk_native_sectors' not found. entering rescue mode... grub rescue > What does that mean? What went wrong? Should I just restart from scratch and try to remake the USB launcher? Thank you very much in advance for your help and advice. Best, -a-

It looks better this time around. Except for disk 3 which is still stuck at 100%

drive 3 still stuck @ 100% utilization...

??? Power failure of drive 1 during data scrubbing File system check -> OK data scrubbing restarted with write cache disabled for disks 1-4

Hey Should I be worried about drive 3? (both regular and extended SMART tests as well as IW health test all come up OK) I don't know what kind of information may be relevant here so I'll just list the following, but do not hesitate to tell me if more detailed information could be useful. CPU: i7-4790k (4cores/8threads) RAM: 4GB (2x2GB) DDR3 1333 MB: Asus Z97-A HDDs: Seagate IronWolf 12TB x9 (RAID5 over 8 disks +1 hot spare) sATA ports: 6/6 sATA3 ports from MB (drives 1-6); 3/5 sATA3 ports from PCIe3.0 x4 AIC (ref) (drives 7-9). All 11 ports detected properly when loader was built (satamap). TCRP version: 0.9.3.0 (without "friend") DSM version: 7.1.0 42661

Thanks Can you please explain the difference between ./rploader.sh <model> bringfriend and ./rploader.sh build <model> withfriend (as described here)? Thanks a lot -a-

Hi I was running a bare metal Xpen rig that was using TCRP loader (no "friend") and running DSM7.1 42661 as a DS918+. I recently installed this rig and didn't have vital data on it. I tried to remake the USB loader (the same way as the 1st time) but this time adding the "withfriend" parameter when building the loader from TCRP. The idea was to be able to perform DSM updates more easily in the future (although it is still not clear to me how I should perform these updates whether or not I'm using TCRP with or without "friend"). After rebooting, my DS918+ was detected as "not installed" and I proceeded to install the corresponding pat file (DSM_DS918+_42661.pat - 346MB). However, after the 10 minutes countdown I get "something went wrong" and I can restart the process (which results in the same failure every time). Is there any way I could "fix" this? If not, how should I proceed to restart from scratch? Should I reformat all my drives and remake the USB loader (with or without "withfriend" this time?) ? Best, -a-

If I don't have TCRP with friend, what postupgrade actions should I do after upgrading? Thanks -a-

Thanks a lot Fortunately, I'm not running on a n54l

Thanks - What does JOT stand for? (out of curiosity) - Why do you say the use of TCRP "with friend" is now impossible) - Why are you mentioning the HP N54L? (Are you using this device?)

Hey @kekesed97 In order to make a new loader, can I just boot on the current USB dongle but in TCRP rather than into the DSM loader that was previously built? And then from TCRP "overwrite" the current loader with a new one? Or should I start from scratch (with a new USB dongle or after erasing the one I am currently using)? Thanks for your help -a-

Sorry @Peter Suh but I'm not sure I understand your previous message. AFAIU the different options to build the USB loader are (correct me if I'm wrong): - TCRP "alone" (cf the guide from @flyride) - TCRP "with friend" (cf this thread. Other tutorial anywhere?) - Your M-shell (based on TCRP "with friend" but using ARPL-style menus) (cf your github) - ARPL (cf their github) Both the 2nd and 3rd options seem very attractive to me. Right now I'm trying to figure out what would be the procedure for me to "convert" my current loader (TCRP "alone") to a new loader (based on TCRP "with friend". I rather not mess this up. Thanks again a lot for your support. -a-