curiouskid

Members
  • Content count

    34
  • Joined

  • Last visited

Community Reputation

1 Neutral

About curiouskid

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. Device is disabled, Contents emulated

    Attached here are diagnostic file. My data drive is now unmountable. xfs_repair didn't help either. I am getting the feeling that i my data is in extreme danger. Parity is still valid. So, if someone can advice me on how to rebuild it, I would appreciate. root@UnRaid:~# xfs_repair -v /dev/sdc1 Phase 1 - find and verify superblock... - block cache size set to 660784 entries Phase 2 - using internal log - zero log... zero_log: head block 91463 tail block 91448 ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. unraid-diagnostics-20171005-1606.zip
  2. One of my drive seem to have failed but it's passing smart. However, when I tried to start array, I notice following errors in system log and it has not started array for last 30 mins. Oct 3 23:27:59 UnRaid kernel: ata10.00: failed to read SCR 1 (Emask=0x40) Oct 3 23:27:59 UnRaid kernel: ata10.01: failed to read SCR 1 (Emask=0x40) Oct 3 23:27:59 UnRaid kernel: ata10.01: failed to read SCR 0 (Emask=0x40) Oct 3 23:27:59 UnRaid kernel: ata10.01: limiting speed to UDMA/100:PIO4 Oct 3 23:27:59 UnRaid kernel: ata10.02: failed to read SCR 1 (Emask=0x40) Oct 3 23:27:59 UnRaid kernel: ata10.03: failed to read SCR 1 (Emask=0x40) Oct 3 23:27:59 UnRaid kernel: ata10.04: failed to read SCR 1 (Emask=0x40) Oct 3 23:27:59 UnRaid kernel: ata10.15: exception Emask 0x4 SAct 0x0 SErr 0x0 action 0x6 frozen Oct 3 23:27:59 UnRaid kernel: ata10.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen Oct 3 23:27:59 UnRaid kernel: ata10.01: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen Oct 3 23:27:59 UnRaid kernel: ata10.01: failed command: WRITE DMA EXT Oct 3 23:27:59 UnRaid kernel: ata10.01: cmd 35/00:00:40:84:00/00:02:00:00:00/e0 tag 6 dma 262144 out Oct 3 23:27:59 UnRaid kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 3 23:27:59 UnRaid kernel: ata10.01: status: { DRDY } Oct 3 23:27:59 UnRaid kernel: ata10.02: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen Oct 3 23:27:59 UnRaid kernel: ata10.03: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen Oct 3 23:27:59 UnRaid kernel: ata10.04: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen Oct 3 23:27:59 UnRaid kernel: ata10.15: hard resetting link Oct 3 23:27:59 UnRaid kernel: ata10.15: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Oct 3 23:27:59 UnRaid kernel: ata10.00: hard resetting link Oct 3 23:28:00 UnRaid kernel: ahci 0000:02:00.0: FBS is disabled Oct 3 23:28:00 UnRaid kernel: ahci 0000:02:00.0: FBS is enabled Oct 3 23:28:00 UnRaid kernel: ata10.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Oct 3 23:28:00 UnRaid kernel: ata10.01: hard resetting link Oct 3 23:28:00 UnRaid kernel: ahci 0000:02:00.0: FBS is disabled Oct 3 23:28:00 UnRaid kernel: ahci 0000:02:00.0: FBS is enabled Oct 3 23:28:00 UnRaid kernel: ata10.01: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 3 23:28:00 UnRaid kernel: ata10.02: hard resetting link Oct 3 23:28:01 UnRaid kernel: ata10.02: SATA link down (SStatus 0 SControl 320) Oct 3 23:28:01 UnRaid kernel: ata10.03: hard resetting link Oct 3 23:28:01 UnRaid kernel: ahci 0000:02:00.0: FBS is disabled Oct 3 23:28:01 UnRaid kernel: ahci 0000:02:00.0: FBS is enabled Oct 3 23:28:01 UnRaid kernel: ata10.03: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Oct 3 23:28:01 UnRaid kernel: ata10.04: hard resetting link Oct 3 23:28:02 UnRaid kernel: ata10.04: SATA link down (SStatus 0 SControl 320) Oct 3 23:28:02 UnRaid kernel: ata10.00: configured for UDMA/133 Oct 3 23:28:02 UnRaid kernel: ata10.01: configured for UDMA/100 Oct 3 23:28:02 UnRaid kernel: ata10.03: configured for UDMA/133 Oct 3 23:28:02 UnRaid kernel: ata10: EH complete I even tried replacing SATA cable thinking it might be faulty but it didn't help. I even tried replaceing power cable by borrowing it form SSD and it didn't help either. Array doesn't start for me to run xfs_repair -v /dev/sdc1 Can someone please help?
  3. Error: Call Traces found on your server

    Fix Common Problem plugin advised me to post diagnostic file here to learn more about Error: Call Traces found on your server. Exact message: "Your server has issued one or more call traces. This could be caused by a Kernel Issue, Bad Memory, etc. You should post your diagnostics and ask for assistance on the unRaid forums" I hope some expert can help me understand what's wrong and advice on how to fix it. unraid-diagnostics-20170930-1824.zip
  4. Need Help Unable to boot using UnRaid USB

    jonathanm Thank you for additional point. Above line got me reading more about Dual Parity. I enjoyed Further discussion#1 thread till page#3 as I could not follow all that was discussed from there on. Because I am infra guy and my programming skill is limited to small scripts and have no base for advanced mathematics to understand formula for data recovery. Anyway, as per WIKI Part highlighted in RED got me confused because I do see slot for 2nd parity drive in Web-UI of current stable release of UnRaid ver 6.3.5. For consumer with simple use case mentioned below which is better option? A. 2nd Parity assuming it's Q Drive with Reed-Solomon code implemented correctly. B. Hot Spare which can be used to replace parity or data disk quickly. C. Buy Cloud Backup with hope that they give me my-data when needed. Instead of showing fine print of user agreement about their limited liability about their inability. Even some of top cloud backup provider's customer review suggest that when they tried restore, it didn't work or it was incredibly slow where complete recovery would take months. Use Case: Very limited at this point. 1) Only user who writes. 2) A Share named VMs - For ESX_VM_Backup. 3) A Share named ISOs - For repository of ISOs. 4) A Share named TimeMachine - To backup Mac. 4) 3 Share named Data, Audio Video - To store 3 type of data. 5) Docker image running Plex.
  5. Need Help Unable to boot using UnRaid USB

    Frank1940 After about 20 mins of silence with crossed finger, I got GUI back. Which now reads. Current Status: Total size:6 TB Elapsed time:17 hours, 57 minutes Current position:2.05 TB (34.2 %) Estimated speed:32.6 MB/sec Estimated finish:1 day, 9 hours, 35 minutes I will write update on recovery after 1 day and 10 hours. For notification I am using Boxcar Notification Agent. Free notifications on phone app from delivered almost real-time from UnRaid. Only problem is that I get too many of those even for green status. After I get my drive back, I will extend research to get only one important ones. Lesson from 1 data disk failure, 1) Read notification and act on them. Prerequisite is that I get few. 2) Do not do anything in panic. It can hurt my data. 3) When in doubt ask community. 4) Accept the fact that just like humans, data loss could occur due to many reasons and in many ways and I can get protection only from few of those reasons. 5) Get an off-site backup. Which I do not have at the moment. Squid Thank you for response. mdResyncPos/mdResyncSize * 100 = % of completion. I am proposing if you could write command line version of everything that Web-UI is doing or showing? May be a shell script with few command line argument about part of Web-UI in clear text on console. That way no Web-UI condition would not provoke novice user like me to push reset button in the moment of panic. This time I didn't do it because I knew drive rebuild is in progress. trurl Yes. I raise white flag for that. Forgive me for my ignorance. Yes. Thank you. Once again thank you for helping. I truly appreciate everyone's attention to detail in this community.
  6. Need Help Unable to boot using UnRaid USB

    Thank you trurl for correcting me. I had oversimplified understanding/misunderstanding of Parity drive and it's role in re-construction of data. Because of your post, I carefully studied https://wiki.lime-technology.com/Parity and there I noticed, following. "At these times, all of the disks (including parity) are read to reconstruct the data to be written to the target disk. As the sum of the bits is always even, unRAID can reconstruct any ONE missing piece of data (the parity or a data disk), as long as the other pieces are correct." Could you please confirm if extended understanding of long sentence above is correct. 1) Only one drive's failure can be tolerated for reconstruction of data. 2) All other drives in array should be present and readable. 3) Pre-condition for recovery of that one drive is that other drives should not have any issues. which means as UnRaid owner I must pay attention to error notification very seriously because fault tolerance window is very small. If I do not act quickly to replace faulty drive quickly and in between if second drive run into any issues, there is no chance of recovery.
  7. Need Help Unable to boot using UnRaid USB

    When I opened ticket with mother board manufacturer, they asked me to take photo of each BIOS setting and send to them. In the process, I learn that under Advanced Menu ->CSM Setting -> boot option filter was set to "UEFI only". While I was preparing response for them, I notice this. So, I quickly changed it to "UEFI and Legacy" which allowed boot. (See BIOS photo attached). In short, My drive was following legacy MBR boot and motherboard was looking for UEFI bootable media. Hence, it was not booting. After above change, I could boot without any issues. However, for this troubleshooting, I had power cycled system multiple time and often not so gracefully. As result one of my data disk in array went bad. Luckily it was not Parity drive. So, I followed https://wiki.lime-technology.com/Troubleshooting#Re-enable_the_drive and confirmed it passes SMART test and started rebuild. It's 6 TB drive with about 850 GB data in it. so, rebuild is seem to take forever. It seems once I have fired rebuild disk and start array, GUI stops responding. Frank1940 could you please advice if there is a way to monitor rebuild process via command line? How do I know if rebuild is going well? Is there a log file about drive rebuild that I can look for?
  8. Unable to boot UnRaid

    When I opened ticket with mother board manufacturer, they asked me to take photo of each BIOS setting and send to them. In the process, I learn that under Advanced Menu ->CSM Setting -> boot option filter was set to "UEFI only". While I was preparing response for them, I notice this. So, I quickly changed it to "UEFI and Legacy" which allowed boot. (See BIOS photo attached). In short, my drive was following legacy MBR boot and motherboard was looking for UEFI bootable media. Hence, it was not booting. After above change, I could boot without any issues. However, for this troubleshooting, I had power cycled system multiple time and often not so gracefully. As result one of my data disk in array went bad. Luckily it was not Parity drive. So, I followed https://wiki.lime-technology.com/Troubleshooting#Re-enable_the_drive and confirmed it passes SMART test and started rebuild. It's 6 TB drive with about 850 GB data in it. so, rebuild is seem to take forever. It seems once I have fired rebuild disk and start array, GUI stops responding. johnnie.black could you please advice if you have way to monitor rebuild process via command line? How do I know if rebuild is going well? Is there a log file about drive rebuild that I can look for?
  9. Unable to boot UnRaid

    After I had upgraded UnRaid to Version 6.3.3 I am unable to boot to UnRaid. Any troubleshooting assistance would be appreciated. From other post I was advised to raise issue here. As per support suggestion on other posed I was asked to checked my flash drive EFI folder to rename to make it fall back on Legacy boot method. However, I checked flash drive and could not find EFI folder in there. Could you please suggest what else can I share to get support?
  10. unRaid checkboxes not visible in Firefox 54.0

    I prefer stable code of FireFox from ESR (Extended Support Release). User can download it from https://www.mozilla.org/en-US/firefox/organizations/all/
  11. Better Deal?

    $309 for two 8 TB is good deal north worth missing. However, each with 8 TB is not good idea as it will sky rocket your build cost. Enterprise class or not enterprise class doesn't really matter much as per google research on Storage Drives. If you are going to use UnRaid, go for cheapest per TB storage option as reliability concerns are well managed by UnRaid. Throw two cheap SSD there and mover job over night. See you tube video about it. Define spin down config and schedule monthly scrub/parity check with write correction. Spin Down config will keep HDD cool when idle (assuming 24x7x365 for this box. One thing that most of lime tech expert has not said often is that you is that you need good UPS for your UnRaid build. unclean shutdown is worst enemy of data. My idea of UnRaid is to write to SSD at fast speed and let mover job move data over night to HDD. Rest of the time when HDD is idle, let it sleep. Here power saving by HDD Spin Down is close to nothing but it will add value to long life of your data. Unless you are building storage system and itching to finish build and load your data, I would wait for July 4th deal or something.
  12. Synalogy makes good products but Lime Tech's UnRaid is better. Now, that's just my two cents based on my feeling. Your milage may very. Now, let's come to your issue. First thing you want to fix is SSH to your UnRaid. If you have access to GUI, reset password from there and reboot your box (Gracefully, Get Plugin as suggested by Spaceinvader One in https://youtu.be/1TTsV9nfazk . After that we can do necessary check to see what goes wrong when you attempt to copy files.
  13. Need HW Advice For UnRaid Downgrade

    To save $ without loosing data and protection, I decided to move this to low power computer build mentioned above. So, I built replacement PC and tested it by installing Windows 10 in Mini PCIE SSD using USB bootable media. I confirmed all hardware including booting from USB worked. After doing stress test when I was happy with newly built PC's stability and performance, I decided to move UnRaid to this computer. I gracefully power down above mentioned Monster PC and pulled out USB Drive for UnRaid and put it in newly built low power PC. I had used same USB slot where i had put in another bootable USB drive for Windows install earlier. I got disappointed when UnRaid didn't boot. I had verified and confirmed that USB stick for UnRaid was top priority in boot order and all other devices were disabled in boot order list. I tried all 4 available USB ports and no luck booting Unraid from any of them. So, I put that USB back into old monster PC and it worked. One thing I did notice is that USB drive for Unraid shows as UEFI : Samsung USB <Serial number of UnRaid USB Drive> Would you please advice on what can I do to ensure newly built PC can boot into UnRaid? I would really appreciate any assistance on this issue.
  14. I had UnRaid running on 16 core 32 thread 128 GB RAM on monster PC. While I appreciate everything this PC did for me, it was power hungry. To save $ without loosing data and protection, I decided to move this to low power computer. So, I built replacement PC and tested it by installing Windows 10 in Mini PCIE SSD using USB bootable media. I confirmed all hardware including booting from USB worked. After doing stress test when I was happy with newly built PC's stability and performance, I decided to move UnRaid to this computer. I gracefully power down above mentioned Monster PC and pulled out USB Drive for UnRaid and put it in newly built low power PC. I used same USB slot where i had put in another bootable USB drive for Windows install earlier. I got disappointed when UnRaid didn't boot. I had verified and confirmed that USB stick for UnRaid was top priority in boot order and all other devices were disabled in boot order list. I thought may be bad port and I tried all 4 available USB ports one by one and no luck booting Unraid from any of them. Drive was getting detected each time. Now, I was more concerned. So, I put that USB back into old monster PC and it worked. One thing I did notice is that USB drive for Unraid shows as UEFI : Samsung USB <Serial number of UnRaid USB Drive> Would you please advice on what can I do to ensure newly built PC can boot into UnRaid? I would really appreciate any assistance on this issue.
  15. 10Gb network card

    Assuming your 10GBE is VmWare compatible, it will be detected as vmnic2 when you boot your ESX host. If not, you would have to hack your way to get that NIC to show up in ESX.
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.