Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

ahab666

Members
  • Joined

  • Last visited

Everything posted by ahab666

  1. 1 tb btrfs -----> 1x 4tb made of 2x2 tb nvme strips the 3rd nvme slot might just be an option for transfering or mirroring the very slow usb boot thumb drive .... still need to find a cheap 128/256 nvme slot compatible ssd cheers ....
  2. now 1 TB, then 2 x 2 TB and one smaller one if sata III only speed ... the sata only speed might also occur if I populate all ram slots with 4x16 GB for my data drives ... they are mainly media files video/audio for local streaming and some plugins amd docker apps for keeping the server alive and well. cheers and thx for your patience - alX
  3. okay, at the moment i have one phyical nvme as my only pool device, the new board supports 3 physical nvme slots but depending on the usage of the onboard sata III ports and the optional GPU one of them degrades to sata III speeds .... my plan was/is to make one big pool device with slot 1 and 2 and transfer the slow usb boot stick to the third one .... without an additional GPU it might still get 2 or even 4 PCIe lanes. my pool device is only used to house the docker.img and the appdata and sys* dir and of course as a network write buffer ;) hope that helps ... cheers alX
  4. hmmm, as I mentioned in the msg the transistion should be smooth, with minimum downtime .... shutdown, remove the mobo, put in the new one tansfer the pool device transfer the sata controller , disks are in the identical physical ports connect to my network reboot from my old USB stick atm i have my appdata dir,the system dir, and the docker img stored on my pool device .... thats it ....
  5. hello, i am just about to replace some of my hardware mainboard cpu I5 ->> I8 ram gen3 32GB -> gen4 64GB pool 1x nvme -> 2x nvme gen 4 , 1x nvme sata III gpu internal intel , optional RTX 1060 please post a step by step tutorial on how to do that without loosing the config (users,shares,fileshares), the plugins and their config files the docker container and the docker app settings the cache/pool device the parity drives. before i begin, what to back up and where (like on an unassigned drive) cheers alX
  6. Hello thx for the replay, Just to be on the save side : 1. I had to remove the “bad” drives physically mid of May to send them to the manufacturers, one of them was very quick, like after a week I have got those drives back. The other one was a bit problematic, one of the 3 swapped drives was DOA. The preclear process it is running right now. 2. By keeping all the assignments and remove the old ones before even creating the array might a bit problematic. Mostly because I am not sure if I used the same physical ports during and after the thunderstorm that ruined the original ones. 3. User shares - to minimize the spin down/up cycles, I tried to separate the user shares to as few drives as possible and used the Unbalance tool excessively to accomplish that. My Docker image was placed on the cache drive, mostly because of loading speeds. 4. How can I make sure, that the formatting process will not be forced or “indefinitely suggested” on the “old” drives that harbor the data from before. cheers and thx
  7. I need to create a new and blank server, because I lost both parities and 3/10 data drives physically. Then one of the exchanged RMA drives was DOA and the whole slow process of getting that excange restarted ... The old array does not start because I get wrong drives at all 5 of them ..... If I use the unassigned drives tool, I am still able to access the data on them. So my idea was to unassign them all, then create a new config with no preserving the array and/or pool slots. Then start the new server, set a basic config (usernames a.s.o.) and add the new 5 (precleared drives) after that, I'll try to add the old ones one by one ..... Any idea if and where I can find the old config data, like user share names and locations, installed plugins and docker apps ? I am adding the latest diagnostic file - maybe you can look into it. When I am talking server I mean the same hardware - server is synonymous for new unraid installation ... An yes i plan to use at least one parity drive in the new installation. cheers tower-diagnostics-20240628-1910.zip
  8. Hi, just to clarify - I create a new empty/blank config. Can I just add the existing drives (including the data on them) to the newly created array ? cheers
  9. Hello Experts, Some time ago I lost both parity drives and 3 data drives during a severe weather event.” Is there any chance to use the data from the “old” data drives in the new created server ? All the RMA'ed disks were checked by pre-clear and seem to be okay. For some reason, the now empty parity discs are not accepted in the old configuration, same as the new data drives. Any ideas please, I can try to create and send the diagnostic file cheers ahab666
  10. Well, I am facing a similar problem even with only one HQ (???) nvme as cache drive .... The moving of the files from a defective drive (emulated by one parity) drive runs with 30 to 95 MB/sec and uses up to 60% CPU resources. So moving a half full 18 TB drive seems to take 4 ever - reading speed off the HDD are about 140 MB/sec, writing speeds are around 80-90 ... Transfer speeds stay at about 100 for some short time (20 sec) and then crash down to 20 or 30 for the next few minuts ..... so patience .... I just hope that the emulated date stay emulated until a crc 32 as well as some MD5 hash check confirm the validity of the data on the physical drive ... good luck to you and cheers
  11. Another idea : do a full (read-zeroing-read) Preclear on that drive and check the logs .... might take some 2 to 4 days. Besides the cables, it might be a PSU/PSA problem and in the worst case the mobo's onboard controller and or/or an PCIe installed HBA failure. The cable swapping might help as well, of course. sorry JorgeB could not resist .... cheers
  12. Hi gurus and experts, I have the opportunity to speed up my server a bit, so I'd like to ask you some NOOB questions, 1. My HDD HBA card has 4x4 SATA 6 connections, with 4 connectors on the card and 16 endings for the individual HDDs. How important is it to keep the HDDs on the same port (LUNs)? 2. In theory, I can add 3 NVMs, but the connection speeds and lane counts are different ! 2 of them have an PCie gen 4 port, the third one is PCIe gen 3. Will the slower one interfere with the 2 faster ones ? Either by slowing them down, or might it even cause timing problems ? 6TB of cache would be nice, but I can easily live with 4 (2x2) TB. Does splitting them up in 2 pools, like one exclusively for docker apps the 2 faster ones as mirrors Raid 0 ? and the slower one as input buffer ? 3. Can one of name me the terminal commands for checking on the integrity of the data HDDs (XFS) superblocks and all that jazz b4 I start the disassembly and re-assembly of my server. Aaaah and I need/will replace 1 Data drive as well as the second Parity disk. Anything else to be aware of ? thx for reading and cheers - ahab
  13. Well, it did, and I am definitely not using a RAID controller - just a pure HBA. I just wonder if I should add two new replacement disks to the array and copy the emulated files to them ? Now I need to prepare for my vacation - I will be away for 2.5 weeks starting with Friday. But I'll be back cheers and thx for your help so far
  14. Hello again, That I cannot do, because UNRAID than states wrong disk. Cheers
  15. Yes i had to - my controller has mini SAS combi ports, 16 channels and 4 jack ports, the cable splits up halfways and the HDDs are connected via 4 seperate jacks (sata). There were all ready issues with both disk 01 and Disk 02 when I sent my original post - both disks were unmountable, but disk 2 had a different indicator in front. Disk01 had the red disabled icon, while disk 2 has the orange warning triangle. There are issues with both Disks, what really troubles me is the fact, that as soon as I start the array in non maintainece I see boatloafs of read errors on the parity 2 drive any ideas what's going on cheers
  16. Hello JorgeB et al here is a newer diagnostic file.i changed the Powersupply cables as well as the data cables. Disk 01 as well as disk 02 are still emulated but the plethora of errors i saw in the xfs repair report with the -n optopn are really bothering me. If i resart the array another resync will be initiated, that will take about 48 hours to complete. if I run a complete pre-clear you need to ad about 2x48 hours as well .... here is the new diag - cheers tower-diagnostics-20231107-1705.zip
  17. Hello, after some power problems, my Unraid server is missing 2 drives, unsupported or missing file system. One of the drives is disabled, but the data on it are still emulated, the other one does not even show that red indicator. XFS repair replaced the primary super blocks but is stuck at stem 2 because the Log files are empty or zeroed. any ideas on how to repair or rescue my array ? cheers tower-diagnostics-20231107-0342.zip
  18. THX - removed it and voi la - it is working again .... As I additionally use the parity sheduler tuning tool, I need to wait for the mover to end and look if the case 2 thingy (Move Now) works too cheers and thx for the quick response ....
  19. Hello again, For some reasons the Gui button for invoking the Mover do not work any longer, i mean the buttons from : 1. Gui : main, array operations, Move 2. Gui : main, array operations, (Move) Scheduler, Mover Settings, Move Now case 1. There is a very short Error msg like "Disabled ......." to fast to read case 2. The GUI shows Mover is running and "jumps" to the Trim Tab. Clicking the Mover Settings tab again, it still shows mover is running until I refresh the screen and go back to Mover settings. any idea what is going wrong ? cheers ahab tower-diagnostics-20231007-1614.zip
  20. Hello, unRAID file corruption: 30-09-2023 00:03 Notice [TOWER] - bunker verify command Found 37 files with MD5 hash key corruption where can I find information which 37 files (and their location) have that md5 hash corruption ? I have no external syslog server running cheers
  21. I support that request and like suggest an UnRaid specific NFS Server Tutorial too !
  22. I'd like to thank JorgeB for his patience - he helped me a ton !!! At least I did not fall into dispair and precleared either my Data Drive nor the "failed" parity drive. JorgeB you are the best thank you , thank you , thank you (x1000)
  23. okay - lets say the recovery of my data drive works out, and it changes back to a physical=not emulated state. How can I recover the first parity drive ? Do I need to pre-clear it 1again and then rebuild parity ? BTW 2 new diagnostic files one after the rebuild, one after a reboot and some maintenance (2 docker app updates) cheers tower-diagnostics-20230822-0900 after reboot.zip tower-diagnostics-20230822-0842 after rebuild.zip
  24. rebuild is in progress 4.8 % done atm - last attempt "stopped" at 4.6 - i am hopeful again ....
  25. @JorgeB et al, the 3 short and extended SMART tests are all error free, so far there are no errors on Parity 1, Parity 2 and/or the Data Drive in question. here are 2 diag files the name explains what they are .... i could pack and send you the smart log files as well if you need them. cheers tower-diagnostics-20230820-1927 maint mode.zip tower-diagnostics-20230820-1937 norm. mode.zip

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.