Aidan13

Waring for others Just went thru a 52 hour pre-clear on a 14TB drive I stopped my array added the pre-cleared drive to the array started the array backup I went to shared to add this new drive as part of a share. I go back to main and I see the new drive is unmountable, unformated. I stop the array, deselect the drive from the array and go to try and format but their is no format button, I keep looking for the format button, I see their is a check box next to the start array button (i think called) "deselect drive from array", I click the start array with check box checked this and the drive goes to unmounted devices I then format it, stop array add drive start array and the array now the system wants to do a 15 hour rebuild, argh!!. Must have been me trying to add this new drive to shares, I'm assuming, that triggered the need for rebuild. So now after a pre-clear of 52 hours I need to have a data-rebuild of 15 hours. argh again!! Your Pre-Cleared drives need to be Formatted, before use, Tales from the Dark Side Tim N

This file is on the flash drive, what caught my attention is the 44 year last modified stat. Just curious what this was. Tim N

I will have to do some research and set this up, but why is this instantaneous working from a windows environment as compared to moving files with Krusader or rsync. I am doing the same function but with a different tool? Here is my rsync terminal command rsync -avh "/mnt/user/Download/Movies/" "/mnt/user/Movies". I am moving files from same drive, same directory just taking files down 1 directory file level and rsync and krusader want to do a cut and paste operation. Just makes me think I am doing something simple wrong. Thanks for the input Tim N

I did read the specialist parity swap before I started my swap. The Parity Check Tuning sounds brilliant, I will add this plugin for parity checks when I'm done with the swap. My weather has cooled down with a light breeze, so I'm over the hump. Thanks Again Tim N

Already have a exterior fan on my Server and I have both side panels open, doing what I can to keep things cool. Swapping 1 14TB parity drive for 2 - 20TB parity drives. Not sure swapping 2 for 1 is slower but here I am, should have planned doing this when climate was more agreeable. Thanks Tim N

This was a recent post which kind-of mirrors my problem. Pause a parity rebuilt? By xdriver March 1, 2023 in General Support I am having an overheating issue with a Parity Drive Swap, it is fairly early morning, before 8:30A. My drive swap started about 7pm last night and this morning my drives are at the low heat warring, between 118 - 121 F. This day is suppose to be a warm one, if I could pause my drive swap to start again when it cools down early evening I would love to be able to do it. So a pause button for swapping would be a good option. Thanks Tim N

The wipefs did not work. This command would not recognize my unassigned, unmountable drive. What did work is going to the little setting wheel way right of the Unassigned Disc panel, select the tiny settings wheel and this will open to a Common Setting page where you Enable Destructive mode. Then go back to the Unassigned Disc panel, select the drive you need to format and there will be a tiny icon at the end of the drive identification select this and you will be able to clear and format drive. Tim N

Thanks for th answer Vr2Io. I didn't know what the command wipefs was, this is the llnk and info as to what this is for anyone else: https://man7.org/linux/man-pages/man8/wipefs.8.html wipefs(8) — Linux manual page NAME | SYNOPSIS | DESCRIPTION | OPTIONS | ENVIRONMENT | EXAMPLES | AUTHORS | SEE ALSO | REPORTING BUGS | AVAILABILITY WIPEFS(8) System Administration WIPEFS(8) NAME top wipefs - wipe a signature from a device SYNOPSIS top wipefs [options] device... wipefs [--backup] -o offset device... wipefs [--backup] -a device... DESCRIPTION top wipefs can erase filesystem, raid or partition-table signatures (magic strings) from the specified device to make the signatures invisible for libblkid. wipefs does not erase the filesystem itself nor any other data from the device. When used without any options, wipefs lists all visible filesystems and the offsets of their basic signatures. The default output is subject to change. So whenever possible, you should avoid using default outputs in your scripts. Always explicitly define expected columns by using --output columns-list in environments where a stable output is required. wipefs calls the BLKRRPART ioctl when it has erased a partition-table signature to inform the kernel about the change. The ioctl is called as the last step and when all specified signatures from all specified devices are already erased. This feature can be used to wipe content on partitions devices as well as partition table on a disk device, for example by wipefs -a /dev/sdc1 /dev/sdc2 /dev/sdc. Note that some filesystems and some partition tables store more magic strings on the device (e.g., FAT, ZFS, GPT). The wipefs command (since v2.31) lists all the offset where a magic strings have been detected. When option -a is used, all magic strings that are visible for libblkid(3) are erased. In this case the wipefs scans the device again after each modification (erase) until no magic string is found. Note that by default wipefs does not erase nested partition tables on non-whole disk devices. For this the option --force is required. OPTIONS top -a, --all Erase all available signatures. The set of erased signatures can be restricted with the -t option. -b, --backup Create a signature backup to the file $HOME/wipefs-<devname>-<offset>.bak. For more details see the EXAMPLE section. -f, --force Force erasure, even if the filesystem is mounted. This is required in order to erase a partition-table signature on a block device. -J, --json Use JSON output format. --lock[=mode] Use exclusive BSD lock for device or file it operates. The optional argument mode can be yes, no (or 1 and 0) or nonblock. If the mode argument is omitted, it defaults to "yes". This option overwrites environment variable $LOCK_BLOCK_DEVICE. The default is not to use any lock at all, but it’s recommended to avoid collisions with udevd or other tools. -i, --noheadings Do not print a header line. -O, --output list Specify which output columns to print. Use --help to get a list of all supported columns. -n, --no-act Causes everything to be done except for the write(2) call. -o, --offset offset Specify the location (in bytes) of the signature which should be erased from the device. The offset number may include a "0x" prefix; then the number will be interpreted as a hex value. It is possible to specify multiple -o options. The offset argument may be followed by the multiplicative suffixes KiB (=1024), MiB (=1024*1024), and so on for GiB, TiB, PiB, EiB, ZiB and YiB (the "iB" is optional, e.g., "K" has the same meaning as "KiB"), or the suffixes KB (=1000), MB (=1000*1000), and so on for GB, TB, PB, EB, ZB and YB. -p, --parsable Print out in parsable instead of printable format. Encode all potentially unsafe characters of a string to the corresponding hex value prefixed by '\x'. -q, --quiet Suppress any messages after a successful signature wipe. -t, --types list Limit the set of printed or erased signatures. More than one type may be specified in a comma-separated list. The list or individual types can be prefixed with 'no' to specify the types on which no action should be taken. For more details see mount(8). -h, --help Display help text and exit. -V, --version Print version and exit. ENVIRONMENT top LIBBLKID_DEBUG=all enables libblkid(3) debug output. LOCK_BLOCK_DEVICE=<mode> use exclusive BSD lock. The mode is "1" or "0". See --lock for more details. EXAMPLES top wipefs /dev/sda* Prints information about sda and all partitions on sda. wipefs --all --backup /dev/sdb Erases all signatures from the device /dev/sdb and creates a signature backup file ~/wipefs-sdb-<offset>.bak for each signature. dd if=~/wipefs-sdb-0x00000438.bak of=/dev/sdb seek=$((0x00000438)) bs=1 conv=notrunc Restores an ext2 signature from the backup file ~/wipefs-sdb-0x00000438.bak. AUTHORS top Karel Zak <[email protected]> SEE ALSO top blkid(8), findfs(8) REPORTING BUGS top For bug reports, use the issue tracker at https://github.com/util-linux/util-linux/issues. AVAILABILITY top The wipefs command is part of the util-linux package which can be downloaded from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils/util-linux/>. This page is part of the util-linux (a random collection of Linux utilities) project. Information about the project can be found at 〈https://www.kernel.org/pub/linux/utils/util-linux/〉. If you have a bug report for this manual page, send it to [email protected]. This page was obtained from the project's upstream Git repository 〈git://git.kernel.org/pub/scm/utils/util-linux/util-linux.git〉 on 2023-12-22. (At that time, the date of the most recent commit that was found in the repository was 2023-12-14.) If you discover any rendering problems in this HTML version of the page, or you believe there is a better or more up-to-date source for the page, or you have corrections or improvements to the information in this COLOPHON (which is not part of the original manual page), send a mail to [email protected] util-linux 2.39.594-1e0ad 2023-07-19 WIPEFS(8)

I am use to windows file system, if I wanted to move files from 1 directory to another on the same drive it was almost instantaneous, windows basically changed the name to the file for file location and that was it. Unraid it seems needs to rewrite all information when changing files from 1 directory to the next within the same drive. I am moving a bit over 5TB using Krusader is their another file manager I should be using for this operation? Thanks Tim N

I am adding 2 drives from my broken qnap system to unraid. These drives show up in Unassigned Discs but there does not seem to be a way to format them for Unraid. The discs show as Dev 1 and Dev 2. With each of these disc there is a little number array 1 thru 5 with a button to "Change Mount Point". Not sure what the means. I have rebooted unraid several times, started and stopped the array, selected each of the new drives and am able to get into the drives settings, attributes, etc. but there is no way to format these existing drives. I have looked on this site for formatting drives but those solutions are not working or not helping I am new to Unraid and a little lost at this point, any help is appreciated Thanks Tim N

bthoven Thanks for the info, I'm just about there; question when I save the self-signed cert should this newly created file be .txt? Cheers Tim N

SimonF - Well that works, Thanks for the reply Tim N

The way my unraid is setup I start the server which brings me to the Terminal Log-In, I enter the username and password, then I go to my windows computer and log-in to unraid with the gui sign-in window. Is it possible to bypass the terminal login or setup an automatic signin at terminal so there is only 1 sign-in. Thanks Tim N

Thanks Frank1940 will make sure when I do the copy to unraid. Thanks Tim N

Easy enough, Thanks for your reply Tim N

I have just setup a new server with 1 parity and 3 data drives all 14Tb drives, there is no data on drives. I want to transfer my movies, tv shows, etc files from my qnap to my unraid, from what I am reading this transfer is better completed without the parity drive to speed things up. My qnap is having issues, half of my drives (1 pool) no longer works due to a mosfet problems. I would like to transfer these files from remaining drives as fast as possible. Would it be advisable to re-setup unraid without a parity drive and copy over files then setup parity, and what would be the best procedure for resetting unraid without parity drive. Thanks Tim N

Thanks for the response. I was able to get to unraid gui thru another computer, I originally had a bad ethernet cable. Documentation buttons on the main unraid web page are not very good kind-of like bud light. The documentation I got from unraid gui is much much better, I'll be reading thru them. Thanks again Tim N

I am setting up my 1st server for unraid. I have the hardware built and have gone thru setting up the unraid usb drive. I have setup the bios, and this is where I am running into some issues & I have questions. 1st my reading of setting up unraid is if I want windows it will be thru a VM (I've never setup a VM before) so I'm assuming that windows is installed on top of Unraid, is this correct? I've already tried running Unraid thru USB drive, this only gets new to a windows type of command prompt (no GUI), I was able to get past username and password prompt but do not know what to do next. I have looked for a manual on line but the only reference to one is back in 2015 with a broken link. If there is a manual for the current version I'd be glad to read it. Thanks for any help Tim N