Polanskiman

The question(s) in this topic have been answered and/or the topic author has resolved their issue. This topic is now closed. If you have other questions, please open a new topic.

The question(s) in this topic have been answered and/or the topic author has resolved their issue. This topic is now closed. If you have other questions, please open a new topic.

The question(s) in this topic have been answered and/or the topic author has resolved their issue. This topic is now closed. If you have other questions, please open a new topic.

The question(s) in this topic have been answered and/or the topic author has resolved their issue. This topic is now closed. If you have other questions, please open a new topic.

The question(s) in this topic have been answered and/or the topic author has resolved their issue. This topic is now closed. If you have other questions, please open a new topic.

The question(s) in this topic have been answered and/or the topic author has resolved their issue. This topic is now closed. If you have other questions, please open a new topic.

The question(s) in this topic have been answered and/or the topic author has resolved their issue. This topic is now closed. If you have other questions, please open a new topic.

The question(s) in this topic have been answered and/or the topic author has resolved their issue. This topic is now closed. If you have other questions, please open a new topic.

The question(s) in this topic have been answered and/or the topic author has resolved their issue. This topic is now closed. If you have other questions, please open a new topic.

Use the manual: I am unsure what page that is since it's all in Chinese. My notification config page doesn't look like that. Also next time please remove any identifiable information such as IP, email address etc. This is for your safety. I just did a 'Send a Test Email' and it worked for me. You might want to look at your local network or the machine that is sending the email. I see you are using a local IP.

Welcome.

This is intentional to prevent DSM updating automatically without user knowledge. For the notification issue, this is unrelated. You probably misconfigured the email config section. I have no problems receiving notification via email from DSM.

The question(s) in this topic have been answered and/or the topic author has resolved their issue. This topic is now closed. If you have other questions, please open a new topic.

@dove7 This is the second post we have to move in less than an hour. Please pay attention to the section titles and post in the right place. Thank you.

Question has been moved here.

Really not the place to ask this. Please search the forum or post in the appropriate section.

Ok it was a success. So I ended up editing 2 databases but without deleting all the entries relating to my drive serial number. I only deleted the entries that showed an error. I initially tried the normal .dump command with sqlite but ended up with some encrypted database 🤷‍♂️ so I went animalistic and simply copied over the databases to my Mac, opened them with 'DB Browser for SQlite' and deleted the entries that were offending me. I then copied over the database back to their original location in the NAS. Needless to say I obviously kept the original databases as backup in case my little stunt wouldn't work. .SYNODISKTESTDB: contains what type of test was done (quick or extended or was aborted) .SYNODISKDB: shows the status of the disk (warning, critical etc) the third one: SYNODISKHEALTHDB: contains the disks error count. I didn't see the need to edit this database since all disks are showing 0 errors. Now, running an extended SMART test for good measure. As if it had never happened 😁 Problem solved!

I had looked around and had found this https://www.reddit.com/r/synology/comments/kktmon/reset_status_of_failing_drive/ which states what you say but ended up not working so I didn't go through that procedure. Beautiful. I should have searched a bit longer!

@Peter Suh This is a reminder for you to use code tags. Thank you.

DSM 7.1 as per my signature. Not the forum. Forum is on a proper server offsite. This is my home's NAS. Mostly pic back ups and movies. Nothing fancy or that I would panic if lost.

Hello everyone, So 2 days ago we had a big fat storm. Lightings and thunders. Power outage. Murphy law came into play and UPS batteries died soon after juice was out. To top it off, DSM was doing a data scrubbing when electricity went out. After juice came back Volume was showing it was in critical conditional, that errors were found and that all hell would brake lose if I didn't change the drive. Right. so I run a quick SMART test and it came as healthy. Then run an extended SMART test which got stuck at 90% so I canceled it. I then run a data scrubbing and it came fine. Run another extended SMART test and it came as healthy. There is no bad sectors or any errors of the sort, yet the drive is still showing me a warning sign. This is annoying. The drive looks fine to me, but the power outage probably triggered that error somehow and now DSM refuses to understand the drive if fine. Any way to remove that warning?

The question(s) in this topic have been answered and/or the topic author has resolved their issue. This topic is now closed. If you have other questions, please open a new topic.

Also, important to note. Be aware that you are using a development version of the loader. Stable version stops at v0.8.0.5 https://github.com/pocopico/tinycore-redpill/tree/stable

You really need to provide some more information else I don't see much help coming your way.

There are presently 2 mainstream loaders available: https://xpenology.com/forum/topic/53817-tinycore-redpill-loader-tcrp/ (TCRP) and https://xpenology.com/forum/topic/63486-automated-redpill-loader-arpl/ (ARPL) I believe both should be able to handle the upgrade to 7.1 at least. Before that I suggest reading this: https://xpenology.com/forum/topic/61634-dsm-7x-loaders-and-platforms/ and this: https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/ TCRP is testing and implementing a new functionality called 'withfriend' (TCRP Friend) which is creating problems with N54L. Read this: https://xpenology.com/forum/topic/62871-tinycore-redpill-loader-tcrp-development-release-09/?do=findComment&comment=347676 If you don't use it you should be fine. I don't have a N54L so can't comment much on the specific so I'll let other chime in.