Robert_Chandra

I think I'm all set now. Thanks!

Actually good news. I'm not sure why this fixed it but after the file system check exited, I stopped the array, started it again, and now everything is mounted perfectly. So I might be good to go now. Copying files from disk 2 to disk 4. Once the copy is done you were saying I can use the New Config tool to change the disk assignments? Is there any risk of me messing something up in that process and wiping out data? Or if you're willing to walk me through that I'd appreciate it.

After all that, all it said was "Exiting now." Sounds like it never found a superblock. So what's my next step for fixing the filesystem? There's no data on this drive.

I just did some math and if I'm reading this correctly, it should only take about 15 million reads to cover the whole drive. It's currently at about 5. So that means probably a couple more hours. Once it finishes and assuming it finds a second superblock, all I'd need to do is rerun the filesystem check without the -n correct? -n means it's just a test run? If it doesn't find a superblock then what's my next step?

Yes. Also from the Main screen I can see the number of reads going up still. It's at 1,871,552 Is that referring to bytes or sectors or what? Because at this rate covering 4TB is going to take a while I'm thinking.

From the GUI, no change yet. Still stuck on the same "attempting to find secondary superblock" line.

Stuck on the new drive being "Unmountable". Running a filesystem check now, with the -n: Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... I'm assuming my next step is to run the filesystem check without the -n?

Ok so I wire up the old HDD and the new SSD at the same time, copy everything from one to the other, remove the HDD, and then just leave Disk 2 as missing from now on? Or is there a way to remove Disk 2 from the array? Or have it start treating Disk 4 as Disk 2 from now on? If I replace more of the HDDs and now I’ve got a 4 5 and 6, would all of 1 2 and 3 be missing forever or can I get the array to treat 4 5 and 6 as 1 2 and 3, etc?

Ok another thing I found while digging through the forum is to try reiserfsck --check. Here's what that gives me: reiserfsck --check /dev/sdb reiserfsck 3.6.27 Will read-only check consistency of the filesystem on /dev/sdb Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes Failed to open the device '/dev/sdb': Unknown code er3k 127

Trying to replace a 4TB seagate harddrive with a Samsung 4TB SSD. Trying to get the array started but I'm seeing the error "The replacement disk must be as big or bigger than the original. After reading other posts I'm seeing that this may have something to do with the motherboard creating an HPA on the drive. I am running a Gigabyte motherboard. The drive is currently assigned as /dev/sdb. Looking at fdisk -l, I'm seeing all of my drives (all of them are 4TB) have 4000787030016 bytes, 7814037168 sectors. The only thing that is obviously different between the new drive and the old drives is the Sector size and I/O size: SSD: Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes HDDs: Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Not sure if that matters though since the total bytes and sectors are identical. hdparm -N on each of the drives all show the same results: max sectors = 7814037168/7814037168, HPA is disabled I have the unassigned devices plugin and tried to format the drive to see if that would do anything. Formatted to XFS with the array still stopped (all of my drives are on XFS - Encrypted) but the error is still not fixed. So as far as I can tell the total sectors and bytes are identical, HPA is disabled, yet the array still won't start because it thinks the new drive is too small. I'm stumped. I'm not a Linux expert so you may need to walk me through commands like you're explaining to a newbie. Any ideas what might be going on here? Thanks!

Did the fix for AMD GPUs not showing up in the dropdown ever get updated?

Right now it says "Good connection". I tried a couple times with hardware encoding both on and off, and turning it off does appear to fix the stutter issue. When it's on the encoder is using "VAAPI", and when it's off the encoder is using "Game Vulkan NV12 + libx264 main (4 threads)". What exactly does that mean? Does my video card just suck? What's the benefit of hardware encoding? When I turn it off does that mean it's using my CPU instead? If my hardware needs some upgrading I should know which hardware is causing the issues. Also I still have the black screen when connected remotely issue, even with the stutter fixed.

I'm getting the same issue as above, AMD GPU with RadeonTop installed, no options to select from in "Unit ID for Dashboard". lspci | grep VGA gives me this: 07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef) Trying to see my GPU usage because I'm getting a stutter from the encoder while using the steam-headless container. Any help is appreciated.

I'm also getting a really annoying stutter. It's about every ten seconds or so, video will hang for about a second before continuing. It's not just while playing games but also in the Big Picture UI, after connecting through Steam Link. I was connected via WiFi at first, and when the stutter would happen I'd see it as the Ping jumping from less than a millisecond up to about 10 milliseconds. So then I hard wired the client to the network, and I still get the stutter but it shows as a reduction in the incoming bitrate rather than an increase in the Ping. This isn't the direct/relay problem, because I can see in the details that I'm getting a direct connection. Is the issue more likely to be related to my network or related to the server itself? I don't know any reason the local network wouldn't be running extremely fast. Or if it's related to the server, is there a way I can see what resource might be getting maxed out? Obviously something has to be bottlenecking the connection. EDIT: Ok I've been looking into this more and it seems to be related to the encoder. In the performance details I see the encoder as "Desktop OpenGL NV12 + VAAPI H264", and the decoder is "tvOS Metal hardware decoding", since I'm using an Apple TV. Whenever the stutter happens, there's some yellow text that pops up and says "slow convert, decode, display". There's a discussion on Steam where people are recommending simply checking the "Use NVBFC capture on NVIDIA GPU" box in the Steam settings, however I'm using an AMD GPU So is it possible to change my encoder or do I just need a newer graphics card?

I'm getting the "sound but no video" bug when connecting remotely via Steam Link. Running on an AMD graphics card with a dummy HDMI plug, and the Radeon-Top plugin is installed. If this can be fixed with a simple settings change, I haven't been able to figure it out yet. Googling the issue seems to suggest that it could be related to the Advanced Host Settings or the GPU driver settings, but nothing I change in Steam's settings seems to have fixed it and I don't know my way around Linux enough to mess with driver settings. So I'm stuck. Any advice is appreciated.