Jump to content
XPEnology Community

chickey

Member
  • Posts

    49
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

chickey's Achievements

Regular Member

Regular Member (3/7)

6

Reputation

  1. Hi Thanks for the message. I ended up doing it exactly the way you described. The only issue i did have that is after the upgrade several packages like file station would not run and could not be repaired. I tried to manually remove these as would have been done on dsm 6 but that did not work so i went for the nuclear option and did a reset and then manually installed the latest DSM 7 pat file i could get away with and it all worked great. Thanks for the links i've seen the DOM modules but in this case i didn't need it. I also have a USB stick as a fallback which i've been able to change the pid/vid to F400 so can boot off that if required.
  2. Your answers were most certainly cryptic. All you had to say was please start a new thread as i don't think that is relevant enough.
  3. I agree it's getting off topic so will make a new thread, was just going with the usb dom image theme. It was your responses which were cryptic unless that was you being funny. Re the downgrade that is not a bad shout. Shall try that and create new thread otherwise. thanks for the help.
  4. It is but i don't get why you are mentioning selling the unit to you or providing proof of purchase or business packages. I have bought a defective DS716+ and it fires up and i can connect to it over the network, psu has been tested and good. when i try to set the device up it can not see the hard disks to initialise, these are blank drives just for testing. I was curious if the USB DOM image may be the issue as it's a beta version of DSM 7 also so wondering if it's crashed during an upgrade/update or similar. Your responses are extremely cryptic.
  5. You've totally lost me there, no idea what your going on about. For the last part i'm not trying to unlock business packages just to get it to see the hard disks.
  6. Hi, it was more where to source the vender specific file for the RS814+. I've managed to get it working by manually amending the files and doing a manual installation of the .pat for the RS814+ it was a bit broken since filestation and some other packages were failed and wouldn't repair so i did a reset and then used a slightly newer DSM 7.1 pat file for the RS814+ and it's now working ok. Shame there isn't a repository of the USB boot images with the serial number removed. I also bought a DS716+ as faulty and i think it's the USB DOM image causing the problem with it.
  7. Sorry to drag up an old thread but do you have an image of the RS814+ with serial removed as just gotten a DS412+
  8. Sorry to drag up an old thread but do you have an image of the RS814+ with serial removed as just gotten a DS412+
  9. Sorry to drag up an old thread but do you have an image of the RS814+ with serial removed as just gotten a DS412+
  10. Out of curiosity what power usage are people managing to get down to? on a i9500t setup i'm still getting 30w at idle with 1 drive. Col
  11. create a triggered task rather than scheduled than you can choose the trigger of boot-up Col
  12. Thankyou, i can now run the script. I shall have to do some testing. Now this is working i need to look into why my drives will only hibernate for 20 seconds!
  13. Has anyone had issues with HDD hibernation on DSM 7.1 on a DS918+ setup. I've checked the scemd.log and it shows the below, i read in the past there was an issue with the HDD led stopping the drives going to sleep but the error was more obvious then the below just mentions the hdd LED. It says waking but they don't appear to go to sleep and also thought there would be a corresponding log entry for sleeping. I've set the drives to hibernate after 10 mins and also enabled logging. I guess also as it's only showing hibernation for seconds the drive never really spins down so that's why i can't tell. Maybe need to figure out what's keeping it awake. # tail -f /var/log/scemd.log 2022-06-28T18:28:21+00:00 nas scemd[12467]: event_disk_hibernation_handler.c:47 The internal disks wake up, hibernate from [Jun 28 18:27:59] 2022-06-28T18:28:24+00:00 nas scemd[12467]: led.c:334 Enable power & phy LED 2022-06-28T18:39:22+00:00 nas scemd[12467]: event_disk_hibernation_handler.c:47 The internal disks wake up, hibernate from [Jun 28 18:39:00] 2022-06-28T18:39:24+00:00 nas scemd[12467]: led.c:334 Enable power & phy LED 2022-06-28T18:58:46+00:00 nas scemd[12467]: event_disk_hibernation_handler.c:47 The internal disks wake up, hibernate from [Jun 28 18:58:24] 2022-06-28T18:58:48+00:00 nas scemd[12467]: led.c:334 Enable power & phy LED 2022-06-28T19:09:51+00:00 nas scemd[12467]: event_disk_hibernation_handler.c:47 The internal disks wake up, hibernate from [Jun 28 19:09:29] 2022-06-28T19:09:53+00:00 nas scemd[12467]: led.c:334 Enable power & phy LED 2022-06-28T19:29:31+00:00 nas scemd[12467]: event_disk_hibernation_handler.c:47 The internal disks wake up, hibernate from [Jun 28 19:29:09] 2022-06-28T19:29:33+00:00 nas scemd[12467]: led.c:334 Enable power & phy LED 2022-06-28T20:00:06+00:00 nas scemd[12467]: event_disk_hibernation_handler.c:47 The internal disks wake up, hibernate from [Jun 28 19:59:44] 2022-06-28T20:00:10+00:00 nas scemd[12467]: led.c:334 Enable power & phy LED 2022-06-28T20:11:27+00:00 nas scemd[12467]: event_disk_hibernation_handler.c:47 The internal disks wake up, hibernate from [Jun 28 20:11:05] 2022-06-28T20:11:30+00:00 nas scemd[12467]: led.c:334 Enable power & phy LED 2022-06-28T20:28:07+00:00 nas scemd[12467]: event_disk_hibernation_handler.c:47 The internal disks wake up, hibernate from [Jun 28 20:27:45] 2022-06-28T20:28:11+00:00 nas scemd[12467]: led.c:334 Enable power & phy LED 2022-06-28T20:39:24+00:00 nas scemd[12467]: event_disk_hibernation_handler.c:47 The internal disks wake up, hibernate from [Jun 28 20:39:00] 2022-06-28T20:39:27+00:00 nas scemd[12467]: led.c:334 Enable power & phy LED
  14. As a side note does your system spin down the HDD if you configure it? Mine doesn't so wondering if it's some C state issue although i have it fully enabled i believe in the BIOS.
×
×
  • Create New...