JorgeB

v2.4.1 fixed my display issue.

It's been a while, much more since I really used DOS, but IIRC you need to add to your config.sys something like: DEVICE=Path\to\HIMEM.SYS DOS=HIGH,UMB Try the remove other DIMMs option first, easier if it works for you.

I had a similar error fixed by booting DOS with himem.sys

http://lime-technology.com/wiki/index.php/Crossflashing_Controllers#LSI_SAS2008_chipset

Looks great! You should add that to the FAQ

Yes

No, this would only work to have VMs/Dockers, etc.

It's possible to use a btrfs pool using the unassigned devices plugin, it won't look pretty since it's not officially supported (ie, only one device shows as mounted) but it works with any raid profile: btrfs fi show /mnt/disks/Test Label: none uuid: 75c7d7f5-74e4-4662-b465-c400b7384a6c Total devices 2 FS bytes used 1.75GiB devid 1 size 232.89GiB used 2.03GiB path /dev/sdf1 devid 3 size 232.89GiB used 2.03GiB path /dev/sde1 btrfs fi df /mnt/disks/Test Data, RAID0: total=2.00GiB, used=1.75GiB System, RAID1: total=32.00MiB, used=16.00KiB Metadata, RAID1: total=1.00GiB, used=2.02MiB GlobalReserve, single: total=16.00MiB, used=0.00B ETA: You'll need to manually create the pool first (or use the cache slots).

FYI, since v6.2 clear is done with the array online, but disk is not tested like when using preclear.

That's normal, unRAID only checks for the preclear signature after starting the array.

I believe the problem is related to this: http://lime-technology.com/forum/index.php?topic=52362.msg503483#msg503483 But this was supposed to be fixed on the kernel included with v6.3, I would just convert all disks to xfs to avoid these and the other reiserfs issues.

Was this feature removed? I'm using latest preclear and trying to stop the array during a preclear doesn't work anymore, stuck on sync filesystems... Any idea why this stopped working? It's not just me as I've seen at least a couple of users with the same problem recently.

You can't fit a PCI-E connector on the CPU AUX or vice versa, they are keyed differently, good thinking from someone

I believe rsync also has a sparse flag, users with vdisks on the array should use it.

If the vdisk was sparse before it's not now, that's the different, you can make it sparse again by using: cp --sparse=always /path/to/source.img /path/to/destination.img

How do you reformat an existing xfs disk as xfs? Do these steps twice by formatting with a different filesystem first, then putting it back to xfs? Yes.

I'm afraid it's still there.

Turbo write should be a little faster than normal writes but because the source disk has to alternate between reading the data to copy and data do update parity it's considerably slower then normal turbo writes, IIRC it maxes out at ~60MB/s.

That means you used: rsync -avPX /mnt/disk2 /mnt/disk3/ It's missing one / at end of disk2 If you want to disable parity stop array, unassign parity, start array, then re-assign it in the end, a parity sync will begin (obviously you'll be unprotected during the conversion)

Most times cycling the UD security setting fixes it: Settings -> Unassigned Devices -> Enable SMB Security Change to Yes, apply, back to No and apply again.

My issue at the time was not unRAID related.

I'm using 1.26 sent by Supermicro support because of another issue, you can try and ask for it.

I have an X11ssm-f but only get the "error clearing flags", try updating the BMC firmware.

That flag is only needed to turn a non sparse file into one, if the backup is sparse you can use just cp without any flag.

In general, the root user has no special access to network shares, so if you try to use root as a login it will just be given the same access as any anonymous user. Notice when you try to setup security for any share that root is not one of the users you can select. For this specific example, what do you have for Settings - Unassigned Devices - SMB Security? If you disable SMB Security your Unassigned Devices will have public access. If you enable SMB Security your Unassigned Devices will have whatever access you give to whatever users you give them to, but Windows won't actually let you change logins to network shares easily, even though it may give you a login prompt. See this post. Sometimes cycling the UD security setting fixes it: Settings -> Unassigned Devices -> Enable SMB Security Change to Yes, apply, back to No and apply again.