Jump to content

Maticks

Members
  • Content Count

    239
  • Joined

  • Last visited

Community Reputation

8 Neutral

About Maticks

  • Rank
    Advanced Member
  • Birthday 12/28/1981

Converted

  • Gender
    Male

Recent Profile Visitors

1067 profile views
  1. Even with Defaults creating a Windows 10 VM i get this error when clicking create. Anyone know what is causing it? When i create any other VM type it seems to work fine. internal error: process exited while connecting to monitor: 2020-05-21T23:06:15.068081Z qemu-system-x86_64: -blockdev {"driver":"file","filename":"root","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}: A regular file was expected by the 'file' driver, but something else was given.
  2. Even with Defaults creating a Windows 10 VM i get this error when clicking create. Anyone know what is causing it? When i create any other VM type it seems to work fine. internal error: process exited while connecting to monitor: 2020-05-21T23:06:15.068081Z qemu-system-x86_64: -blockdev {"driver":"file","filename":"root","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}: A regular file was expected by the 'file' driver, but something else was given.
  3. Maybe it is just a controller difference, not sure all my other 9 drives have WD-WCXXXXXXXX for their serial number. It seem to have passed though woth two Uncorrect Errors. Kicked off an Extended Smart as well. Event: Preclear on 3704212 Subject: Preclear: PASS! Preclearing Disk 3704212 (/dev/sdv) Finished!!! Description: Preclear: PASS! Preclearing Disk 3704212 (/dev/sdv) Finished!!! Cycle 1 of 1 Importance: normal Disk sdv has successfully finished a preclear cycle! Ran 1 cycles. Last Cycle\`s Pre-Read Time: 8:38:14 @ 128 MB/s. Last Cycle\`s Zeroing Time: 7:51:33 @ 141 MB/s. Last Cycle\`s Post-Read Time: 8:39:03 @ 128 MB/s. Last Cycle\`s Elapsed TIme: 25:07:36 Disk Start Temperature: 31 C Disk Current Temperature: 33 C S.M.A.R.T. Report ATTRIBUTE INITIAL CYCLE 1 STATUS 5-Reallocated_Sector_Ct 0 0 - 9-Power_On_Hours 1 27 Up 26 183-Runtime_Bad_Block 0 0 - 187-Reported_Uncorrect 0 2 Up 2 190-Airflow_Temperature_Cel 30 33 Up 3 196-Reallocated_Event_Count 0 0 - 197-Current_Pending_Sector 0 0 - 198-Offline_Uncorrectable 0 0 - 199-UDMA_CRC_Error_Count 0 0 - SMART overall-health self-assessment test result: PASSED
  4. I think i got done buying a counterfeit drive hrmm.. The Serial number is very weird... this drive "WDC_WD40EFRX-68N32N0_3704212" all my other WD Red 4TB Drives "WDC_WD40EFRX-68N32N0_WD-WCC7K6ELLFVA"
  5. it's a WDC_WD40EFRX WD Red 4TB drive, the guys gone out of business so i can't even take it back My only option is RMA through Western Digital, i guess ill wait for the preclear to finish see if there are bad results.
  6. I bought a new WD Red Drive and started my preclear, the Smart Info has it new with no errors. But starting off the preclear the speed is holding 164MB/sec but every 2 seconds it makes this sectoring noise for 1 second its about 5-6 clicks its the same pattern over and over. I can't remember any of my other precleared drives making noise while preclearing. Anyone know if this is a bad sign, i don't see any errors as of yet im only at stage 1 of preclearing.
  7. I have a 9210-8i that wouldn't let me flash it from IR to IT mode throwing some error messages. Then after a reboot when i do -list it says controller is not operational asking for a firmware file. neither 2108it or ir seem to work. It says a firmware hostboot is required and its stuck in RESET state. Looks like it needs a file i can't find to get it out of this state, anyone else this before? It is an LSI SAS: SAS2008(B2) not sure if this B2 is the issue i haven't seen that before.
  8. Second Parity Check completed with 0 errors. Should i bin this disk when my new one arrives or is it ok to keep running it? It is 7 Years old coming up to 8 it kind of is close to end of life back in the old days before i knew about NAS drives.
  9. My Smart finished vault-smart-20200409-2146.zip
  10. attached is the Diag file. Looks like that Disk that had the errors this morning is throwing read errors now while the parity check is running. Noticing 32 errors so far vault-diagnostics-20200408-1901.zip
  11. Hoping someone here can help i have run a parity check with the write corrections box ticked. Included some screenshots. On the 12-01-2020 5847 Errors were corrected after running the check. On the 12-02-2020 5849 Errors were corrected after running the check. Now i am running it today and its most the way through i am back at 5849 again. My Disk 8 Threw some Smart messages "offline uncorrectable is 8 " and current pending sector is 8 . I just ordered a new one and will pull it out and replace it with a new one once it arrives. my issue is will my array rebuild here properly? I an running this check now i want to make sure my data is correct before i pull the disk out. Anyone about to help out work where these errors are coming from ?
  12. Wondering if you can use ZFS on the Cache pool of 2xM.2 Drives the same size. I tried running with BTRFS with two drives and always end up with one drive going into read only mode randomly. Then having to rebuild the mirror again. I always end up ripping out one drive and run unprotected off a single Cache drive in BTRFS but it seems only happy with that setup. Not sure if it was a bug but i haven't tried in a good year now, i want to though fix this protection issue. I noticed ZFS had some support here for data drives, so can that be extended to the Cache Pool as well ? BTRFS seems a bit broken at least for me.
  13. When VM's are running on BR0 traffic will not follow across the default gateway out of the unraid server. From the local LAN ran it works fine. It also breaks any Dockers running on BR0 from working on the LAN at all. When you stop all the VM's running on BR0 the Dockers running on BR0 all return to normal.
  14. This problem can be annoying. Delete the boot bios from the LSI card. You cannot boot from a drive off the LSI card anymore. But you can boot off your USB ports and system SATA ports. If you place more than one LSI controller in your system you have to do this. Don't know why but the bios on the controller fights and disk's go into error randomly. You simply run the flash tool on the LSI card and tell it to delete the bios. Go to the boot section and set the first boot to the UEFI shell and restart. From the SHELL> prompt, type in this command sas2flash -list save the results of this output by your preferred method. From the SHELL> prompt, type in this command sas2flash -o -e 5 to erase the boot services area of the flash chip. And one last time, type in sas2flash -list and verify the Bios Version now reads N/A
  15. I'm back on 6.6.7 really hoping for a fix soon.