Velun

Hi, I have a server with an array, and I've just built a new one and want to move that array to the new one and create another one in the old one with some old drives. I will only move the disks, not the Unraid stick. I have another stick for the new one with a new license, and I was wondering if I can just move the drives and if I keep the correct drives for array and parity, if it will just create another array with the data remaining there. I don't want to do something wrong and lose the data from the drives, so I said I better ask if it works or if there's another way to do it.

Just my luck.... Thank you for the help and quick response.

I've tried to run an extended test and it failed with error Failed in segment --> from the start. I can't even run a short test anymore, it failes around 8% with the same error, so I'm guessing the drive died. Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ] Description number (hours) # 1 Background short Failed in segment --> 3 91 - [- - -] # 2 Background long Failed in segment --> 3 91 - [- - -] # 3 Background short Failed in segment --> 3 91 - [- - -] # 4 Background short Failed in segment --> 3 91 - [- - -] # 5 Background long Failed in segment --> 3 91 - [- - -] # 6 Background short Failed in segment --> 3 91 - [- - -] # 7 Background short Failed in segment --> 3 91 - [- - -] # 8 Background long Failed in segment --> 3 91 - [- - -] # 9 Background short Completed - 45 - [- - -] #10 Background short Completed - 10 - [- - -]

Hi, A few days ago, I got two 18 TB SAS drives to put as my parity (they are the biggest drives in my array). I just removed the old one from parity and put these new ones and started the array with parity check and automatically started to rebuild parity. Around 97% one of the drives got errors and got disabled, the other one worked fine. So I tried again to add the drive that failed as parity and the second time got to around 98.7% as I can see. Before that, I ran a SMART short test and it was fine. From what I can see from the logs it gets some errors like I/O error, dev sdw, sector 10223794696 op 0x1:(WRITE) flags 0x0 phys_seg 119 prio class 2 md: disk0 write error, sector=10223794632 md: disk0 write error, sector=10223794640 md: disk0 write error, sector=10223794648 md: disk0 write error, sector=10223794656 md: disk0 write error, sector=10223794664 I/O error, dev sdw, sector 34706499072 op 0x1:(WRITE) flags 0x0 phys_seg 32 prio class 2 md: disk0 write error, sector=34706499008 md: disk0 write error, sector=34706499016 md: disk0 write error, sector=34706499024 md: disk0 write error, sector=34706499032 md: disk0 write error, sector=34706499040 I don't know how can I check if the problem is the drive or if it can be the cable, controller, firmware, etc. The cable is new as these are my only SAS drives, the rest are SATA. These are my only 18TB drives the rest are 12 TB, 8 TB, and a few 4 TB drives. What I was thinking of trying was to put that drive on another head from the SAS cable, it has 4 and I only have two drives, so two are free. The other thing was to run a SMART extend test on that drive. If anybody has other suggestions or if you can see if the drive is the problem from the logs please let me know. I've attached the diagnostics file if that helps. Thank you. tower-diagnostics-20231222-1103.zip

I've switched to ipvlan for now, let's hope that fix it. Thank you @JorgeB for the help.

After upgrading to 6.12.4 the server hangs up every 2-3 weeks. Nothing works, no webgui and no ssh, so I took some pic before restarting. I've attached the logs after restart, don't know if that helps or if I need to configure some sort of persistent logs, or if the images are enough. I saw something about macvlan there maybe it's about that bug, but I thought it was fixed in 6.12.4. tower-diagnostics-20231029-1315.zip

Thank you for the info. One more question do you know if the bracket for the Fujitsu card it's the same as the bracket for the Lsi card? I'm new with enterprise equipment so I ask a lot of questions :). Thank you again. Later edit: Ended up ordering an LSI Broadcom 9201-8i. It was a bit cheaper and I hoped it will overheat less than the 9300 one (i plan to mod the card and put an noctua fan on it). Do the cables between the controller and the expander are simple SFF-8087 to SFF-8087 ? or is anything special i should look into.

Hi all, I have a system on windows for a plex server and want to move to an Unraid setup. My first problem is that I have an Delock 10 ports card and from what I could find on the forum this card it's not ok because it's a port multiplier card. So I went on Ebay and ordered an Intel RES2SV240 expander card because I need lots of ports and now I'm searching for the controller. For what I could found on forum some guys already paired this with an LSI 9300-8i controller so I went ahead and searched and I found a few things where I need help. 1. Found a card from Fujitsu CP400i card and from what I understand it has an 9308 chipset and it's already flashed with 9300-8i firmware (LSI Firmware: 9300-8i 16.00.10.00, MPT3 BIOS 08.37.00.00, EFI BIOS 18.00.00.00). My question is if this card it's ok or not and if it's better to find one produced by Lsi or Broadcom. or should I search for another chipset. The card can be found here . 2. If I get a card with 3008 chipset does it get me any improvemests over SAS2308 or should I find a 2308 card because they are cheaper. 3. If that card from pct 1 it's ok what cables do i need. I'm guessing something like this for the controller to the expansion card and this from the expander to the drives. The card comes with a low profile bracket and i need full, does anybody know where i can buy a full profile in Europe? 4. I'm using a consumer motherboard I have and Intel 8700k on a Gigabyte Aorus Gaming 7 board. Are there any compatibility issues with consumer boards? Thanks