10 hours ago, txpenguin said:

Just upgraded to 6.8.0 a few days ago -- now, this morning, Disk7 (coincidence?) shows up with this exact problem. I did the xfs_repair command and restarted the array.

 

Disk 7 is now 'fixed' -- but Disk 10 now shows as "Unmountable: No File System" ... this is the first problem I've encountered with UNRAID .. and to have 2 drives. within minutes of each other, pop up with this problem only days after an update seems like a bug.

I Too Upgraded a few days ago to 6.8.0 and I had a "Unmountable: No File System" Error on my Cache Drive, At the time it had no important data on it so I shot off to Amazon bought a brand new Nvme Drive as I presumed it was a Failure of the Drive, Installed the New Drive Zero'd the Nvme Drive and Replaced it, Day 1 It showed "Unmountable: No File System" Error, I swapped it onto my PCIe NVme Adaptor and It started working fine, I then Presumed everything was TipTop, Invoked the Mover and it Moved my 1TB of VDisks into the cache and was working flawless until the 1st when it blew out a "Unmountable: No File System" I attempted to get it back but sadly I lost my VM and Very Important Data which I did backup on the second Cache Drive which also Blew out a "Unmountable: No File System" Error, 

 

Accepting Defeat I Proceeded to Invest 9 hours into rebuilding what I could from scraps of data left in my Shares and at 4am this morning Had a Working machine,  Until 6am, I Shut the VM down, Restarted the Unraid with the Shutdown button within Unraid and upon reboot "Unmountable: No File System" 

 

I give up 

43 minutes ago, ZaviiNet said:

upon reboot "Unmountable: No File System" 

If you want some help you need to post the diagnostics: Tools -> Diagnostics

10 hours ago, johnnie.black said:

If you want some help you need to post the diagnostics: Tools -> Diagnostics

Sorry about the Delay

tower-diagnostics-20200102-2031.zip

Split into its own thread so we can keep things straight

Board keeps crashing, looks USB related, look for a bios update:

 

Jan  2 19:21:39 Tower kernel: Call Trace:
Jan  2 19:21:39 Tower kernel: <IRQ>
Jan  2 19:21:39 Tower kernel: dump_stack+0x67/0x83
Jan  2 19:21:39 Tower kernel: __report_bad_irq+0x30/0xa5
Jan  2 19:21:39 Tower kernel: note_interrupt+0x1d8/0x229
Jan  2 19:21:39 Tower kernel: handle_irq_event_percpu+0x4f/0x6f
Jan  2 19:21:39 Tower kernel: handle_irq_event+0x34/0x51
Jan  2 19:21:39 Tower kernel: handle_fasteoi_irq+0x92/0xfc
Jan  2 19:21:39 Tower kernel: handle_irq+0x1c/0x1f
Jan  2 19:21:39 Tower kernel: do_IRQ+0x46/0xd0
Jan  2 19:21:39 Tower kernel: common_interrupt+0xf/0xf
Jan  2 19:21:39 Tower kernel: </IRQ>
Jan  2 19:21:39 Tower kernel: RIP: 0010:cpuidle_enter_state+0xe8/0x141
Jan  2 19:21:39 Tower kernel: Code: ff 45 84 f6 74 1d 9c 58 0f 1f 44 00 00 0f ba e0 09 73 09 0f 0b fa 66 0f 1f 44 00 00 31 ff e8 e0 99 bb ff fb 66 0f 1f 44 00 00 <48> 2b 2c 24 b8 ff ff ff 7f 48 b9 ff ff ff ff f3 01 00 00 48 39 cd
Jan  2 19:21:39 Tower kernel: RSP: 0018:ffffc900031c3e98 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffde
Jan  2 19:21:39 Tower kernel: RAX: ffff88880fcdfac0 RBX: ffff88880fcea400 RCX: 000000000000001f
Jan  2 19:21:39 Tower kernel: RDX: 0000000000000000 RSI: 0000000020000219 RDI: 0000000000000000
Jan  2 19:21:39 Tower kernel: RBP: 000000f200d191e5 R08: 000000f200d191e5 R09: 000000f1fe894337
Jan  2 19:21:39 Tower kernel: R10: 0000000000000000 R11: 071c71c71c71c71c R12: 0000000000000005
Jan  2 19:21:39 Tower kernel: R13: ffffffff81e5b1a0 R14: 0000000000000000 R15: ffffffff81e5b398
Jan  2 19:21:39 Tower kernel: ? cpuidle_enter_state+0xbf/0x141
Jan  2 19:21:39 Tower kernel: do_idle+0x17e/0x1fc
Jan  2 19:21:39 Tower kernel: cpu_startup_entry+0x6a/0x6c
Jan  2 19:21:39 Tower kernel: start_secondary+0x197/0x1b2
Jan  2 19:21:39 Tower kernel: secondary_startup_64+0xa4/0xb0
Jan  2 19:21:39 Tower kernel: handlers:
Jan  2 19:21:39 Tower kernel: [<00000000bf011852>] usb_hcd_irq
Jan  2 19:21:39 Tower kernel: [<00000000787a51ca>] vfio_intx_handler
Jan  2 19:21:39 Tower kernel: Disabling IRQ #16