Hello community,

this is my first post unfortunately.

Apologies for my english as i am not english, lol.

 

I am testing unraid on my futur rig based on a gigabytes B450M-DS3H rev0.1 with a ryzen 3 2200G.

Also have a pci-e to sata 6 extender 8 ports, based on a Marvell 9215 + JMB575

( this card is fully supported by Ubuntuserver, have one running in production on my diy nextcloud server for over 3 years now )

 

day one: 

- created the USB media and choose stable 6.9.1

- on my futur rig, installed unraid, claim a test license for 30 days.

- created a test array with 3 storages device, no cache disk yet.

- basic config successfully done ( ipv6, virtual network, plugins, dockers container ( cloudcommander, swag, nextcloud ... )

- access from internal network and from other external device ok.

 

Day two:

- sanity check on the morning ok.

- using GUI, did a shutdown

 

- hardware stop.

- Hardware reboot.

 

- USB key is missing boot sector. dead.

 

- reinstall 6.9.1 on USB.

 

- Hardware reboot.

- 6.9.1 kernel panic:

VFS cannot open root devicee "(null)" or unknown-block(0,0): error -6

follow by 

Kernel pacnic -- not syncing : VFS: Unable to mount root fs on unknown-block(0,0)
call trace
dump_stach+0xx6b/0x83
panix+0xff/0x2a1
mount_block_root+0x131/0x160
? rest_init+0xxaf/0xaf
kernel_init+0x5/0xaf
ret_from_fork+0x22/0x30
Kernel Offset disabled
---[ end kernel pacnic ]

 

My guess is a  locked array from the first test.

 

The usb stcik dying a hardware reboot is not a good sign !!! The key is new. bought it via amazon in a promotional package, and this is not the stick i am planning to use.

Q1? --> is this a "bad stick" behavior ??

 

Kernel pacnic: am i stuck or not ? Don't remember seen any XFS or else format type been shown yesterday.

Q2? --> As i cannot even boot unraid in safe mode, is there a way to troubleshoot my rig... or should i use external tools to destroy the array leftover from day 1...

 

Thank 

 

 

 

Please open a topic under General Support, it appears you have a hardware related problem.

 

4 minutes ago, bonienl said:

Please open a topic under General Support, it appears you have a hardware related problem.

 

Hi,

 

As I am new here, a moderator will have to move my post.

 

Hardware related: do you mean bad usb  stick or else ? 

Quote

JorgeB said: This is usually a flash drive problem, try re-creating it using the USB tool or using a different one, and please continue discussion here:....

 

The stick was created using unraid usb tool, of course.

I am testing it's reliability ( some kind of low brand from china ) . So far so good. But noneless, i will re-partitioning it to a fresh fat32 status, and re-use unraind usb tool....

I will also test a Kingston DTSE9 16G stick to be sure.

 

Thx for help.

OK, update and closure.

 

My low quality usb stick from ENUODA USB 3.0 64GB is unreliable. 

After repartitioning with specific tools and recreating with unraid, i was able to reboot without error, and also reproduce hardware failure when unraid shutdown throught GUI.

 

The Kingston DTSE9 is much better and did not suffer data lost when unraid goes boom ... like electric reboot or genuine GUI shutdown.

 

Thx for help pointing to the good direction ( my first guess ) .

 

Consider as CLOSED