• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

F23 Server - "Unknown Error" During Installation - DeviceTreeError?

W

WaR-ped

2[H]4U
Joined
Mar 10, 2000
Messages
2,379
Background: I'm totally new to linux and my end goal is to get an Amahi 9 based home server setup (which requires Fedora 23 Server to be installed first). I had previous success with an older set of hardware that I used as a trial run before investing in new hardware and additional storage. The new hardware setup consists of an AMD A88X based system (Asrock FM2A88M +Pro3 and AMD APU) and I re-used 2 of the old SATA hard drives by pairing them up with the UEFI AMD hardware RAID (1) process.

To make sure the RAID drives were set up correctly, I mock-installed Windows 10 up to the point of choosing a hard drive location. After using a separate USB flash drive to load the AMD RAID drivers, everything appeared to work fine.

Which brings me to the F23 Server installation process. With the hard drives plugged in, the installation process crashes right after the language menu GUI pops up indicating an "Unknown Error" has occurred. I tried out the bug submittal process:


reason: blivet.errors.DeviceTreeError: failed to add slave viaccbhhiciad of device viaccbhhiciad1​

What does that mean? Not sure how to troubleshoot at this point. I tried both the UEFI and BIOS boot versions of my Fedora Media Writer based flash drive. I tried both the Net Install and full versions of the F23 Server ISO.
 
I found the root cause of the problem. The 2 old drives were previously setup in a RAID configuration on the old motherboard. Somehow it carried that information over to the new setup and made a mess of trying to setup the AMD RAID. I used a Windows10 install disk (USB flash) to run 'diskpart' to clear out the old information before trying again to create a new array.

Good news: It appeared to work and I no longer get the fatal error from the installation GUI.

Bad news: The installation GUI appears to recognize both drives as independent entities (sda1 & sdb1)

(Mostly just a learning exercise at this point as I'm going to remove the array and go back to AHCI to continue installation. The general consensus from the Internet appears to be that unless you've got an expensive add-on RAID controller, using virtual RAID by way of motherboard firmware or OS software is a bit of a crapshoot anyway.)
 
"AMD Raid" is software raid and is absolute rubbish. As such, you'll see zero penalty using the properly built-in mdraid in linux. Turn off the BIOS raid and then create the linux raid via mdadm (and read the bloody howtos first)
 
You must log in or register to reply here.
Back
Top