MacModMachine
-
Posts
23 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by MacModMachine
-
-
On 1/4/2023 at 7:47 PM, limetech said:
This is nonsense but beyond the scope of the discussion dealing with CRC/DMA errors.
For sure, 100%, DMA/CRC errors are hardware faults, not caused by software, file systems, etc. They are reported by physical controllers and indicate a physical h/w problem. In my experience, these kinds of errors commonly originate with bad cables or connectors, or simply faulty components. Another overlooked cause is faulty or overloaded power supplies. Back when we offered server products, we always were careful to source single-rail PSU's so that full capacity of the power supply can be fed to the hard drives. Servers with multi-rail PSU's might have a high overall wattage rating, but any one rail is a fraction of that; and, typically one rail would serve the entire hard drive array. I'm sure you can deduce what the problem is with this arrangement.
I haven't looked at many low-level Linux device drivers for several years but I'll take a look at a few and see if they retry CRC/DMA errors. Adding retry logic in md/unraid driver might be something for us to consider.
As has been stated correctly, Unraid only disables devices which fail writes because what else can you do if a write fails (and presumably all retries fail)? But sure, if there is a lot of other activity in the server causing a transient dip in voltage, then maybe a retry would succeed.
Hi, Tom
i have been using unRAID for 13 years now. I love it.
however this issue did come up for me when using 6.** specifically. Opened a ticket with support and it was closed as a hardware issue which i accepted. So in getting that news i installed truenas ( some years ago). it still runs today with the same hardware without issue.
Money not being much of an issue for me as i use unRAID for my photography business. I invested another 5k in 2 systems. All brand new hardware , including SAS/SATA controllers / Cables. This error hit me after about 3 months of using it disabling 2 of my disks overnight. The second system lasted for about 5 months hitting 1 failed disk overnight.
Replacing the disks on both systems , This time failures on month 4 and 6 with different disks plugged into different cables. Then i proceeded to installed truenas on both systems , they have been running for a year and a bit.
I built a new unraid system at this time with new hardware. The problem cropped up around month 8 this time , using NAS rated WD RED's.
Im at a loss at this point , very torn. i love unRAID. but i cannot trust either hardware in general or unRAID.....im just not sure which one it is right now.
-
On 11/12/2022 at 8:04 AM, csard said:
Hey mikeyosm,
I'm looking for the same. Recently bought two P4s and I would like to use it for 4 VMs. I saw a great tutorial from craftcomputing to do this on Proxmox with M40s but I'm not knowledged enough to translate the tutorial to unraid (if even possible).
Link to the tutorial:Please let me know if you found somthing on this topic!
I used this with success on my P4's
-
On 10/12/2022 at 8:22 AM, mikeyosm said:
DId this work? I'm thinking of buying a Telsa P4 and splitting the vgpu across multiple Windows 11 VMs
you can use vGPU , its a complicated process and very hacky. i have 2 p4's split up myself.
-
28 minutes ago, johnnie.black said:
You're also using a SASLP, can't see SMART since the disk dropped offline but those controllers are known to drop disks without a reason and not recommended for a long time.
crappp....ii think your right....i must have f'd up somewhere....the disk that failed was no doubt on that controller....ill have to hate myself for the rest of the day at minimum....
thanks...seriously...thanks.
ill remove that controller and burn it with a torch.
-
22 minutes ago, johnnie.black said:
You're also using a SASLP, can't see SMART since the disk dropped offline but those controllers are known to drop disks without a reason and not recommended for a long time.
That was added after , the disks in question are not on it. This problem started before that saslp was added. I can take it out it will make no difference with this problem.
-
this is what i can see possibly being the issue, however not much information is given :
May 26 17:01:19 fileserver kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1
May 26 17:01:19 fileserver kernel: sd 10:0:1:0: [sdd] tag#504 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
May 26 17:01:19 fileserver kernel: sd 10:0:1:0: [sdd] tag#504 CDB: opcode=0x8a 8a 00 00 00 00 00 74 81 02 60 00 00 00 08 00 00
May 26 17:01:19 fileserver kernel: print_req_error: I/O error, dev sdd, sector 1954611808 -
Had another drop out , grabbed the logs this time.
-
I forced the PCIE down to V2 from auto to see if that could possibly be the issue , since i have a H310 in this now. I have tried several brand new 9211's though.
-
9 minutes ago, Squid said:
What do you mean by booted?
What I see is that the system looked like it started normally. Then you unassigned the parity drives, reassigned them and restarted the array. The system starts to build the parity information and then you cancelled it.
thats my bad , i forgot to grab the diag before reboot. ill wait for it to show again and grab it again.
by booted , i mean they show a red X , however the disk remains fine. must be removed and readded to array. they are showing cannot write sector in the logs. however the disk is fine. scanned it several times with spinwrite.
Quote -
Here is a doozy , been using unraid for 11 years now , never had to ask a question.....well today is that day.
Unraid 6.8.3
9 disks in array. Ryzen 3400G + 64GB Ram + LSI2008 controller.
Disks getting booted from array overnight.
Replaced Controller
Replaced cabling + power supply (Data+power)
Replaced ram
Replaced motherboard + cpu (ryzen 3600 now)
replaced every disk with brand new sealed disks
ran memory test for 7 days with no issues. ran Freenas on same system with ZFS pool's and no issues for 14 days.
still booting disks....in unraid.
grateful for any help as im going slightly crazy.....posting diag
-
I migrated to unRAID from FreeBSD and the thing I miss most of all from FreeBSD is the ability to scrub. I am probably going to convert all my drives to BTRFS primarily to gain the ability to perform scrubs again. If this were integrated into the GUI it would make me very happy. I think others will find the value in performing scrubs once they have the capability.
It is surprising how much bit rot happens on large arrays. I usually found errors during zpool scrubs about once every few months. I have had BDrips that had become unplayable due to rot be perfectly restored through zpool scrubs.
This is the number one feature I am looking forward to.
craigr
how can i get my drives easily converted to btrfs ? one at a time ?
is it worth me to do for the scrubbing ?
thanks!
-
after some serious testing here are my findings,
used 2 new thumb drives , still error.
tested my 4gb stick , it had memory errors.
used another 4gb stick and it booted.
no matter what , safe mode or not reg unraid or xen unraid it will not boot with 1gb ram.
i also used another core 2 system and tested it with 1gb ram with the same error, but booted fine with 2gb.
problem solved , unraid needs more than 1gb ram with beta 6 and on.
-
I just built a new machine with the following ,
ECS NM70-i
1gb ram
4x3tb hdd
its a mini itx build.
it runs unraid 5.0.5 just fine , soon as i try beta 6 release 10a it blows up with this error.
I see you're using 1gb of RAM. If you're booting with the Xen modules then you might be running out of available memory. From the "splash screen" you might try booting in safe mode without Xen.
i just tried this, made no difference , i even put in a 4gb stick just to be sure.
thanks
-
Quick question, did you try to upgrade 5 to 6a without removing your old 5x plugins?
they are both fresh installs in both cases , freshly formatted drives.
i just put my pro key on it.
thanks
-
Disclaimer: This is beta software. While every effort has been made to ensure no data loss, use at your own risk!
If you are running -beta9, or -beta10, you can update via the Plugin Manager by selecting following URL and paste in the Install Extension box (beta9) or Install Plugin box (beta10):
https://raw.githubusercontent.com/limetech/webGui/master/unRAIDServer/unRAIDServer.plg
If you are running beta10 you will see some messages that look like:
Warning: mkdir(): File exists in /usr/local/emhttp/plugins/plgMan/plugin on line 146
Those are harmless and eliminated in the release you are downloading.
Sorry about the bugs in -beta10; most were due to my own snafu in creating the actual release...
Summary of changes from 6.0-beta10 to 6.0-beta10a ------------------------------------------------- - emhttp: get rid of extraneous "closeConnection" messages - shfs: fix issue preventing new object creation on use_cache=yes shares when cache not present - plgMan: eliminate extraneous mkdir warning - plgMan: fix issue where 'update' operation installs wrong symlink - webGui: eliminate extraneous timezone indicator on DateTime page - xenMan: restored 'x' bit in event scripts
I just built a new machine with the following ,
ECS NM70-i
1gb ram
4x3tb hdd
its a mini itx build.
it runs unraid 5.0.5 just fine , soon as i try beta 6 release 10a it blows up with this error.
-
I would like to ask again as I did not see a reply to my original question.
I currently have Unraid installed and working great as a server. I would like to keep all my content and current configuration but move the unraid instance to a virtual machine as the server is being underutilized. Assuming this is possible, is there special instructions I can follow to accomplish this? Can someone with a bit of knowledge please give me feedback or a bit of guidance? I would like to run a mythtv back-end on the same server for home pvr.
My CPU (Celeron G1610 Processor) supports VT-x but not vt-d. My motherboard (asrock b75 pro3-m vt-x) supports vt-d. Is it worth updating my CPU to also support vt-d?
Thanks.
yes , you will need VT-D to do passthrough (pass hardware through to VM's)
the only other way is make a data store on the drives and use them inside the VM (not recommended)
you should be able to find an 1155 socket cpu to support VT-D for 200-300$
depending on that motherboards configuration you will need a PCIE sata controller , i recommend a M1015 / i9220 based card, with 2 SAS forward breakout cables.
-
i have been using these in production environments , they work really well.
you add a few settings on boot , configure (5mins max) and your good to go.
i have setup several websites on them , crm's and invoicing systems too.
-
The problem could not be reproduced with the above test if any of the following conditions are met:
* Disk write cache is disabled.
* NCQ is disabled. This may not always be true as the c't lab also reported problems with NCQ disabled.
* A modified test version of smartctl which does not issue IDENTIFY DEVICE commands is used. Then all other SMART and non-SMART commands used by smartctl work without any data loss.
Christian Franke
NCQ Is disabled on my system, i run virtual machines and have 5 of these 204UI disks and have never noticed the issue and you think i would considering a virtual machine would be very sensitive to data corruption.
Also putting the pc in IDE mode according to christian will alleviate the issue.
since im running so many of these disks im going to spend some serious time trying to make this issue show up.
-
i second this
Samsung HD204UI
i have a 3tb seagate external , i had taken out the internal drive and had it in my unraid server for 2 months without issue and eventually replaced it with a WD Black disk for reliability.
-
hi,
i have built a system using ZOTAC NF610I-K-E motherboard + E8400 cpu and it works great, i have been using it for almost 5 days without issue.
only has 10/100 ethernet, but works for all my media fine.
Motherboard :
i have also tested several esata 4Bay disk enclosure's i will list later on with more testing.
The motherboard Bios needs some adjustments , set bios to defaults and disable intel VMM this will load unraid without error.
im sure the Sil3132 chipset has been tested, but i have also tested it with port multiplier and it checks out good, a little slow but still functioning and no issues.
all tested with 3 2TB WD EADS (Data) + 2TB WD Black (parity) + 500GB WD Black (Cache)
watched shows 2+ hours a day on popcorn hour (C-200).
verified checksums with Md5
hope this helps someone.
Write cache is disabled on all drives after installing new LSI card
in General Support
Posted
literally just fought this battle , a firmware update did the trick for me. also forcing write cache on using : smartctl -s wcache-sct,on,p /dev/sdX