68rustang

Members
  • Content Count

    24
  • Joined

  • Last visited

Everything posted by 68rustang

  1. Asus MB, i3 CPU, gskill RAM, Corsair PSU, WD HDDs, unsure of the SATA Card. Initially after first getting errors I checked all the SATA and power connections on the MB and SATA card. This seemed to fix it at first then I started getting more errors and everything went downhill. I do not think my problems had anything to do Xpenology itself. In my experience over the last year or so it has been very stable and indistinguishable from my other real Synology DS415+ I have at the office. The only difference being my Xpenology build was way more capable than the 415+ for about the same money sp
  2. The boot drive seems to be OK as I never had an issue starting the system it was just once it was up and running that I was seeing failures, degraded volumes and sometime no drives at all. The 1.5 TB WD GREEN that was not part of the array was showing as bad but I haven't tested it yet. The 3TB WD RED that was part of the array is now showing as removed and I am not sure what caused that. I will test it once I have safely removed all the data . I actually have a large APC UPS that this PC and all my connected network gear is plugged into. The power issues being the root cause is only s
  3. I had tried rebooting XPenology with different hardware/HDD combos but that just seemed to make things worse. After some more reading last night I ran fsck on the LV and after answering "y" a few hundred times I had READ ONLY access to volume 1. Woohoo! I then rebooted the box with Xpenology and I was met with an orange "degraded" warning but still have READ ONLY access to the volume. It looks like I may have lost some files, a couple directories are showing as empty, but most of the things I care about are still there. The new DS showed up yesterday and the HDDs should be here today.
  4. FWIW mdadm --detail: ubuntu@ubuntu:~$ sudo mdadm --detail /dev/md2 /dev/md2: Version : 1.2 Creation Time : Sun Feb 8 04:13:39 2015 Raid Level : raid5 Array Size : 11701741056 (11159.65 GiB 11982.58 GB) Used Dev Size : 2925435264 (2789.91 GiB 2995.65 GB) Raid Devices : 5 Total Devices : 4 Persistence : Superblock is persistent Update Time : Thu Feb 25 02:19:45 2016 State : clean, degraded Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 64K Name : DiskStation:2
  5. List partitions fdisk -l ubuntu@ubuntu:~$ sudo fdisk -l Disk /dev/ram0: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram1: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram2: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512
  6. running dmesg | tail give me: ubuntu@ubuntu:~$ dmesg | tail [ 571.526516] JBD2: no valid journal superblock found [ 571.526521] EXT4-fs (dm-0): error loading journal [31114.861827] JBD2: no valid journal superblock found [31114.861833] EXT4-fs (dm-0): error loading journal [31118.935355] JBD2: no valid journal superblock found [31118.935359] EXT4-fs (dm-0): error loading journal [31119.654014] JBD2: no valid journal superblock found [31119.654018] EXT4-fs (dm-0): error loading journal [31176.915385] JBD2: no valid journal superblock found [31176.915391] EXT4-fs (dm-0): error loading jo
  7. Is there anybody willing to help guide a Linux noob through attempting to recover data from a fubar'd SHR volume? Last weekend my normally reliable XPenology box decided to blow up. It might have been power related I am not sure because I was not home. The majority of my issues are explained here : http://xpenology.com/forum/viewtopic.php?f=2&t=12414 and here: http://xpenology.com/forum/viewtopic.php?f=2&t=12458 Where I am at right now is that I have the computer booted up from a Ubuntu LiveUSB stick and I tried following the Synology tutorial for recovering data using
  8. Yeah it was a bad night, the more I tried to figure out the worse it got. I have shut it down for now and the new DS1815+ should be here Friday. I'm hoping that the new hardware will be able to reassemble the volume. If not I am going to try to read the data using Ubuntu. My initial guess is that the power issues zapped either the MB, SATA card or PSU. that is the only way I can explain the weird jumping around of the problem.
  9. I just ordered a new DS1815+ to replace my home built XPEnology box. Can I simply remove the HDDs from the XPEnology box and plug them into the Synology and migrate them over? Synology make sit sound like you can as long as the disks are plugged in in the same order they were originally. On the XPEnology my disks are 3, 9, 10, 11, and 12. If I move them to the DS1815+ and plug them in as 3=1, 9=2, 10=3, 11=4 and 12=5 will it work? I thought I remembered seeing a post somewhere about straightening out the HDD #s in XPEnology but I can't seem to find it now. t
  10. I agree about the WD Greens. That is why it was used for downloads and junk files. It looks like both problem drives are plugged into the SATA card. After shutting it down, checking all connections and restarting it was able to repair the RED drive. The GREEN is still showing as crashed. **EDIT** - I don't know what is going on with this box. The drives have always showed as 1,3,9,10,11, and 12 in Storage Manager. 1 and 3 were the first two giving me problems and were both plugged into the SATA card. I unplugged 1 and everything was OK. Now It is showing 3 as 1 and thinks 3 and 12 are miss
  11. Over weekend one of the disks in my NAS crashed. It was a single disk (1.5TB WD Green)volume (Volume3) that was used for downloads and as a TimeMachine backup destination. No biggie, backup what I could, wiped it and tested it. It tested OK so I reinstalled it and started the initialization this morning. It is now reporting as crashed again!?! Also one of the 3TB WD RED dirves in the SHR array of Volume1 is reporting as crashed and volume 1 is degraded. At the end of last week we did have some issues with power but the NAS is plugged into a large APC UPS and should have been insulated from
  12. when I updated mine it initially hung at the same spot. I did a hard reset and it booted up normal.
  13. Any news on 5.2 progress? Which boards, threads,etc are people discussing it on? Please don't take this as me being impatient I understand it takes some time. I am just wondering where I can keep tabs on any progress and maybe learn a thing or two about the process.
  14. There isn't one solution that works for everyone but a few of us have found ways around the problem with our hardware. My Recommendation is to go in and disable everything in the BIOS that isn't needed.
  15. That is interesting because on my Asus board setting the SATA ports to IDE mode did not have any effect.
  16. Got it. Turns out the Trigger message is normal. Since I wasn't getting any feedback here and didn't know any better way I went into the BIOS and started disabling all all of the unnecessary items and rebboting after each one. After disabling the onboard serial and printer ports all is good with 5.1.
  17. Anyone? Even a nudge in the right troubleshooting direction? I am not sure the "trigger device plug event" is an error but in normal boot mode it is the last thing shown before the NAS powers off. This has been mentioned over in the russian section as well.
  18. I am trying to update from 5.0 to 5.1 and having a problem. This has been mentioned in the big 5.1 thread by a few of us but doesn't seem to be getting any attention. I am able to boot from my Xpenoboot USB drive and choose update. It finishes booting and I am able to find the NAS with Synology Assistant and choose and install the 5022.1.pat file. The NAS reboots again and the trouble starts. The NAS shows up as "Starting Services" in Synology Assistant but then eventually disappears. If I hook a monitor up to it and watch the boot process it hangs for a short while at "====trigger device
  19. why not just leave the HDD in the PC?
  20. I have a new DS415+ sitting here if it would be any help. I can follow directions if somebody lets me know what they might need.
  21. seems that the router rebooting was the problem. The NAS didn't seem to mind prior to installing 4528.
  22. After going over the logs again I noticed that it was showing as starting services every morning around 4 AM. Looked like it was rebooting or something. POking around further I found that the router was rebooting everyday around that time. Lets see if that fixed it.
  23. I need some help figuring out what is going on with my NAS. Occasionally it will just stop responding. The power is on, the lights are on and the Synology Assistant shows it as "ready" but no IP address is listed. It is set to receive a static IP from the router. None of the web interfaces respond. I think it is after long periods of inactivity but not certain. I think it started doing this after the DSM 5.0 4582 Update. It is a home built machine running DSM 5.0 - 4582 Update 2. I applied Update 1 and 2 hoping it would fix the issue but it hasn't. I don't see anything in the logs, literally