First time boot stuck

[dfrontiera]

Hi all,

I'm attempting to run Unraid for the first time and my server keeps getting stuck on bootup. 

It stops on the line "amdgpu: topology add node"

 

My server is an AMD 5600G with 32 gigs of ram, 24TB's HDD and 1 260 gig nvme.

I also added an old Nvidia MSI 980 ti for video encoding.

 

I previously installed Proxmox but am not a fan and after all the video's I've seen of Unraid I plan to purchase a key but can't get it boot so I can setup an account and get that far. 

 

My technical experience is pretty high but my server knowledge is low. My linux even lower. 

 

I know I haven't given much to go on so please let me know what info you need. I'd really like to get on my server as my OS. 

 

-D

[JorgeB]

If booting UEFI try legacy or vice versa. 

 

 

[dfrontiera]

I managed to get it working. 

What I did was I went through the bios item by item.

I found 1 more hidden virtualization (beyond SVM) so I enabled that.

I disabled the onboard graphics.

and I set all the sata ports to hotports.

I was then able to boot into Unraid.

 

The problem I'm having now is that it says my 250 gig nvme cache is unmountable and says it's unsupported or no file system. 

I tried to format it but keeps coming back with the same thing. I'm gonna wait for the array to build and then was thinking about running the bios erase program on it to see if that works. But any help or suggestions on getting my cache drive to work would be much appreciated!

[JorgeB]

Try wiping it with "blkdiscard -f /dev/xxx", if that doesn't help post the diagnostics after a format attempt.

[dfrontiera]

54 minutes ago, JorgeB said:

Try wiping it with "blkdiscard -f /dev/xxx", if that doesn't help post the diagnostics after a format attempt.

 

Okay really sorry for these newbie questions... 

1. Can I do this while the array is still building?

2. If I do the command in the terminal this command knows I want it to run for the Cache drive or is there something more I have to do to define it? (Sorry I know almost nothing about linux right now, plan to start watching some videos soon)

[JorgeB]

Array should be stopped.

 

10 minutes ago, dfrontiera said:

knows I want it to run for the Cache drive

/xxx must be replaced with correct device, like /dev/sdb or /dev/nvme0n1, if you want post the diags and I can tell you the complete command.

[dfrontiera]

1 hour ago, JorgeB said:

Array should be stopped.

 

/xxx must be replaced with correct device, like /dev/sdb or /dev/nvme0n1, if you want post the diags and I can tell you the complete command.

 

So I followed your command in the terminal and got the following 

 

But then nothing happened.

I tried to do another format through the array but no luck 

I attempted to run the SMART short quick self test (The longer one is grayed out) but I click the button and it seems like nothing happens.

 

When I open the error log for the under the same test tab I see this

 

You mentioned me sending you the diagnostics. So I did the format and then ran the diagnostics and have attached them.

I hope this is what you are looking for but let me know if you need anything else.

 

Also I really appreciate your help!

executor-server-diagnostics-20220929-1127.zip

[JorgeB]

Sep 28 19:06:49 Executor-Server  emhttpd: shcmd (740): /sbin/wipefs -a /dev/nvme0n1
Sep 28 19:06:49 Executor-Server root: wipefs: error: /dev/nvme0n1: probing initialization failed: Device or resource busy
Sep 28 19:06:49 Executor-Server  emhttpd: shcmd (740): exit status: 1
Sep 28 19:06:49 Executor-Server  emhttpd: writing MBR on disk (nvme0n1) with partition 1 offset 2048, erased: 0
Sep 28 19:06:49 Executor-Server  emhttpd: re-reading (nvme0n1) partition table
Sep 28 19:06:50 Executor-Server  emhttpd: error: mkmbr, 2196: Device or resource busy (16): ioctl BLKRRPART: /dev/nvme0n1
Sep 28 19:06:50 Executor-Server  emhttpd: shcmd (741): udevadm settle
Sep 28 19:06:50 Executor-Server  emhttpd: shcmd (742): /sbin/wipefs -a /dev/nvme0n1p1
Sep 28 19:06:50 Executor-Server  emhttpd: shcmd (743): mkfs.btrfs -f /dev/nvme0n1p1
Sep 28 19:06:50 Executor-Server root: ERROR: '/dev/nvme0n1p1' is too small to make a usable filesystem

 

It's saying device in use, so it's not wiping it completely and then using the existing partition 1 which is too small, try rebooting and running blkdiscard right after boot, if it still doesn't format post new diags.

[dfrontiera]

That worked! I'm up and running thank you so much for all your help and patience!