heyper

Good question I looked it up, here is the explanation for the bash-shell: Single Quotes http://www.gnu.org/software/bash/manual/html_node/Single-Quotes.html Double Quotes http://www.gnu.org/software/bash/manual/html_node/Double-Quotes.html Also helpful: https://stackoverflow.com/questions/6697753/difference-between-single-and-double-quotes-in-bash

Hey, you could try something like (adding quotes): wget --user=myusername --password=mypassword "ftp://192.168.2.6:2219/volume1(sda1)/keyfile" -0 /root/keyfile

The correcting run was done and corrected many errors. The non-correction check afterwards ended with zero errors, so everything should be fine Thanks!

Thanks for your answer! Good guess, the errors started after the time the old party check would have been finished (before the parity swap) I'm running a correcting check and afterwards a non-correcting one and let you know the result

Sorry, forgot the attachment. Added

Hey there I was checking my parity (without writing corrections) and got tons of errors (about 800 million). The parity check was canceled at ~75%. The server is on UPS and there was no unclean shutdown. The hard drives don't have any uncommon SMART data. So I guess the problem must be somewhere else. I did a parity swap some months ago to use a larger party HDD but I'm quite sure that I checked the parity afterwards with 0 errors (last check was 3 months ago with 0 errors). I checked the log and got 100 of these messages: Jun 26 01:53:48 unRAID kernel: md: recovery thread: P incorrect, sector=11721045064 Jun 26 01:53:48 unRAID kernel: md: recovery thread: P incorrect, sector=11721045072 Jun 26 01:53:48 unRAID kernel: md: recovery thread: P incorrect, sector=11721045080 ... Jun 26 01:53:48 unRAID kernel: md: recovery thread: P incorrect, sector=11721045840 Jun 26 01:53:48 unRAID kernel: md: recovery thread: P incorrect, sector=11721045848 Jun 26 01:53:48 unRAID kernel: md: recovery thread: P incorrect, sector=11721045856 I guess it's quite strange that all these errors occurred at 01:53:48. I canceled the parity check (at ~ 75%) and I'm currently running SMART extended self-tests on the disks. Hopefully somebody has an idea

Hey! How did you do the install of DSM 6.0.2 ? The loader is a *.img file, but Unraid needs *.iso? (Running Unraid 6.3.5) I tried to install DSM 5.2 with an *.iso. It does not boot... --> edit I set HDD to sata and eth to e1000. Edit: DSM 5.2 ISO boots with SeaBIOS. After uploading the pat-file via browser the machine hangs after reboot "booting from hard disk" (seen in the vnc-monitor) DSM 5.2 is working. Changing the <boot order='1/> for the bootloader and <boot order='2'/> for the vdisk in the XML did it. Anyway, is there a chance to get a *.iso for DSM 6.x ? Edit2: The trick is to use the *.img bootloader as the frist vdisk (picture here): Now DSM 6.0.2 works. It displays an alert in the system health "DSM cannot start up normally. ..." But it works. Any Ideas on this?

That's awesome support ! Kudos ! It wasn't a script error; the disk was assigned to the array and showed as missing; Unassigned Devices showed the disk but the script refused to clear it, since it's serial number was still in super.dat. Not always we have the time, but today I had a few minutes to take a look into this. Thank you so much!!! Now I'm understanding the unRAID System better My Problem was this little "test" with mounting an existing ext4 as an array(Don't do it ): https://lime-technology.com/forum/index.php?topic=43593.msg538450#msg538450 I posted the fix at the end. For me it's a fresh start with unRAID, so no Problem Im looking forward to unRAID Pro now

ok! will send you the details via PN. Thank you!

@Helmonder Already removed and reinstalled the plugin. Still "Starting..." I also rebooted the Server two times... The server is freshly installed two days ago... Running the Trial so far. Did not start any array for the moment...

I wanted to start a new unRAID server und now I wanted to start with preclearing all the disks. I started the preclearing and waited some time (15min) but the GUI is showing " Starting..." and nothing happens. Here is the log: It's a WD Red 6 TB running fine so far. What is going on? The whole system with all Plugins is up to date.