badboyz

Members
  • Posts

    28
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

badboyz's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Thanks for the assistance Johnnie. I think its the old netapp 24 bay shelf making the crc errors. I'm planning to move back to my 12 bay lenovo sa120.
  2. here are the diags from the VM nas-diagnostics-20190208-0855.zip
  3. I had a new HBA with 20.00.07.00 that I swapped out but I was still getting the same issue. Going crazy I switched the server back to booting to esxi and running unraid as a VM and the array starts now. Any idea why it might work in esxi with the controller being passed through but on the same physical server if I try running it bare metal it hangs? Happy its working again for now, but I'd really like to move to running it directly on the server (dell r710)
  4. I have been trying to figure this out for last 2 days and I'm just at a loss on what to do. I had a drive drop out of the array and had previous issues so moved unraid from running in esxi as a VM to bare metal on a dell r710. All the hardware is the same other than not being passed through from esxi. When trying to start the array it gets hung up while mounting the drives. attached are the diagnostics. Please help. nas-diagnostics-20190207-2048.zip
  5. I'm in the process of converting the the metadata now before I copy my data back over. I just wanted to check if this looks correct now after I run that command.
  6. I'm able to read the drive outside of unraid, so I'm in process of copying the data to an external drive before letting unraid wipe the drive. I attached another diagnostic file from earlier. If you have any insight into what my cause my i/o time out issues? I just don't know if its the 24 bay enclosure or one of its components or the hba card in my r710 server... nas-diagnostics-20180827-1620.zip
  7. I've been having issues for a while now and haven't figured out the cause. It seems anytime I have an unclean shutdown from a power failure during the parity check one of my drives will start reporting errors and eventually get disabled. At first I thought maybe it was a power issue but now I believe it may be my HBA card or the controller in the disk shelf. My current issue is during a parity rebuild another disk starting having I/O errors and then showed up under "Unassigned Devices" even though the rebuild was still running. After the rebuild finished this disk was now disabled and like an idiot I click on mount in "Unassigned Devices" but it did not mount. I checked the actual disk shelf to make sure the drive was properly connected and rebooted unraid. After rebooting this disk now says "disabled/emulated" but also says Unmountable No file system. Is there a way to recover from this within unraid or should I remove the disk and copy the data off, then allow unraid to reformat it? Below is the log info for the disk and attach is the diagnostics. Aug 27 16:14:00 nas emhttpd: shcmd (150): mkdir -p /mnt/disk19 Aug 27 16:14:00 nas emhttpd: shcmd (151): mount -t btrfs -o noatime,nodiratime /dev/md19 /mnt/disk19 Aug 27 16:14:00 nas kernel: BTRFS info (device md19): disk space caching is enabled Aug 27 16:14:00 nas kernel: BTRFS info (device md19): has skinny extents Aug 27 16:14:01 nas kernel: BTRFS error (device md19): bad tree block start 9784718863715718926 2751066292224 Aug 27 16:14:01 nas kernel: BTRFS error (device md19): failed to recover balance: -5 Aug 27 16:14:01 nas root: mount: /mnt/disk19: wrong fs type, bad option, bad superblock on /dev/md19, missing codepage or helper program, or other error. Aug 27 16:14:01 nas kernel: BTRFS error (device md19): open_ctree failed Aug 27 16:14:01 nas emhttpd: shcmd (151): exit status: 32 Aug 27 16:14:01 nas emhttpd: /mnt/disk19 mount error: No file system Aug 27 16:14:01 nas emhttpd: shcmd (152): umount /mnt/disk19 Aug 27 16:14:01 nas root: umount: /mnt/disk19: not mounted. Aug 27 16:14:01 nas emhttpd: shcmd (152): exit status: 32 Aug 27 16:14:01 nas emhttpd: shcmd (153): rmdir /mnt/disk19 nas-diagnostics-20180827-2318.zip
  8. Did this fix the issue? I occasionally have this problem too.
  9. Did I post this in the wrong section?
  10. In order to control the fans on my lenovo SA120 enclosure I need to use sg_ses (part of sg3_utils). Can someone point in the right direction of how to install sg3_utils in unRAID? I only have experience with installing the packages that someone else has made...
  11. I am thinking of using this script to assist in my move to XFS, but I wanted to know does this method preserve all of the file attributes or will things like the time/date stamps change? I was going to use this command: Disk1 is the currently full and disk4 is the newly formatted XFS disk and I wanted it to save a log. diskmv -f "" disk1 disk4 > disk1move.log
  12. Like it or not, this IS the support thread as published for needo's containers. All of this and no support. guess I should make a new thread @ironicbadger
  13. The notations for sickbeard say to set EDGE=1 to run the latest master branch, but regardless if I set edge to 1 or 0 it still keeps me on the latest development branch. I really want to switch to the master branch in hopes of getting the plexnotifier working again. When changing the edge setting from 0 to 1 do I need to do anything else or once I hit save should be switching and updating to the master branch?
  14. No sensor temps for me: Linux 3.4.26-unRAID. root@RobertNas:~# sensors -u k10temp-pci-00c3 Adapter: PCI adapter temp1: temp1_input: 43.500 temp1_max: 70.000 temp1_crit: 90.000 temp1_crit_hyst: 87.000 Motherboard/cpu : ASRock E350M1 AMD E-350 APU (1.6GHz, Dual-Core) AMD A50M Hudson M1 Mini ITX Motherboard/CPU Combo
  15. Signed up with yours. Here is my link: http://chunkhost.com/r/dreamkiller Sent from my HTC Vivid