• Content Count

  • Joined

  • Last visited

Everything posted by xrecar

  1. No. The data won't make sense without the other drives. ie: one file could be written across multiple drives - that's why a battery backup is so important, a power outage could corrupt all of your data if it were writing while it glitches. (Only takes once to learn the lesson) If you need something to "unplg", use a USB drive that is not part of the raid.
  2. I honestly feel like 5.1 seemed more steady than 5.2. I won't do the 5.2 update due to my system becoming"weird" (notifications stopped/hibernation stopped).
  3. Update 2 killed hibernation for me. Revert to the original IMG. Fixed it for me.
  4. Went back / did not do update 2. Hibernation works again.
  5. Update 2 seems to be my issue. 5.2 no updates works along with hibernation.
  6. I'm thinking the HD hibernation issue may be with update 2. Clean install with the 5.2.2 image HDD hibernation was working - now its not. Debating going back. I've had permission issues with Sick/Sab all of a sudden too -
  7. I actually reinstalled on accident losing my settings this way. (Prolly an easier way, but no one has answered) I was on the latest 5.2 update 2 after doing the usual flash USB with new IMG and then use pat file with synotools from 5.1.5. Didn't work well. Lost recent logs, and hibernation didn't work. Read that a 'fresh' install fixes things. Use at own risk. 1. Flashed USB with 5.1 IMG. 2. Rebooted and chose update at the bottom of the boot menu. 3. Synotools will tell you you have to reinstall when you choose to migrate/choose the old 5.1 pat, as the version installed is newer.
  8. Just me. But I'll prolly use this test version - especially if it has an expansion fix. Why be limited by the other?
  9. Asus C60M1-I. I'm sure there are newer options with built in usb3. But I have had pretty good luck as a file server. *never mind, I only see refurb and a new one for $300 on Amazon. It was more like $70 a year and a half ago.
  10. Migrated from beta 5. All OK except red notification, and telling me I have an intel core i3. AMD C60m1 here 16 gigs and 6*3tb. Thanks for everything.
  11. Sounds like you actually deleted your files. It took me a mistake like this to teach me the importance of secondary backups. (And enabling recycle bin)
  12. Sounds like you actually deleted your files. It took me a mistake like this to teach me the importance of secondary backups. (And enabling recycle bin)
  13. xrecar

    AMD APU ?

    C60M1-I running 4.2.3202 . I was able to get it fairly cheap at the time. DSM only reports 3 of the 16 gigs of ram installed. Debating upgrading to 4.3 because everything is working but that slight issue. Ram usage never seems to max out anyways. 6 disks, its a great file server/plex/media box.
  14. DSM 4.2-3202. Any way to fix the reported RAM reported under info via drivers? - 3072 megs vs 16 gigs installed. I'm nervous to upgrade to the new build as I have quite a bit on my volume 6x3 TB - do you think a migration would work? The last 3211 I tried only saw 5 drives. Thanks for your hard work. *sorry , meant to include I'm running on Asus c60m1-i.
  15. I attempted an earlier update to 3211 (not this build) , and only 5 of my 6 disks were seen. It said my volume was corrupt, I couldn't save my 12tb that was on it (this is before we knew about changing config file settings to see 12+ disks). I wouldn'tbe able to migrate or willing to try again , unless this version saw my disks 'out of the box'. Anyone have any info on this? The original 3211 saw my 6th as esata. Did not include it in the volume. Is this fixed at install? So make sure you have the backup always. Always.
  16. Got it to work by pasting these .ko files in /lib/modules/ using ssh and an ssh/ftp client. Is there a similar fix to see all 16 gigs of ram not just 3? usbcore%20ohci-hd.zip
  17. Yes I've seen that- like I said, I don't know how to do those things as my Linux knowledge is limited. If someone could create the image with the ohci implemented that would be boss.
  18. Can someone post this build (USB stick image) with the USB OHCI drivers for a basic UPS enabled? I'm a bit clueless, and don't want to reinvent the wheel if someone already has it running. Thanks in advance.
  19. Installed 4.2 3202. Had port forwarding enabled on my router long story short, massive traffic from China trying to use scripts with alphabetic user/pass attempts. Sometimes for two or more hours. 218.108.*.* 124.162.*.* 58.213.*.* 123.163.*.* Just to name a few. Added to blacklist and enabled login attempt blacklist on fail. If it were a backdoor, you think they would have had an easier time. Maybe its just safer not to have port forwarding enabled. Just my experience. Are they just constantly scanning everyone's ports at all times? I wondered as well. Warning Conn
  20. Seems to be working well. I have sabnzbd, sickbeard, couch potato and media server loaded and running. All in the small fractal design case. The bios setup I think I finally figured out- you have to go into advanced and delete the other bootup options other than your USB stick. It reboots and shuts down without probs. Wish it saw my APC via USB though. Tried the newer release and it corrupted the volume by identifying one of the six drives as esata. Had to reload 10tb. No USB 3.0 is a bit rough. Asus c60m1-i. Only sees 3 of 16 gigs of ram is other complaint. Newer build saw 16.
  21. Welp, this build sees my 16gigs of memory, but identified 1/6 3TB drives as Esata. Couldnt migrate backwards, said it was degraded. asus c60m1-i, 6x3TB, 16 gigs ram
  22. Asus C60m1-I with 16 gigs of ram. Only 3 gigs reported under DSM, 16 in bios. Wierd thing is, 3211 shows only 5 drives instead of 6, but showing the full 16gigs of ram. DS3612xs_3202-Repack How is this solved BTW?
  23. Seems to work on my Asus C60M1-I if anyone is interested. 16 gigs ram. 5x3tb wd red drives. Getting 90MB/sec xfer rates. FYI. I could only see 3 drives with the previous build. Love the interface. *something odd, I added a 6th drive and the 16gigs of memory went to 3gigs under info. 16 still reporting in bios.