Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Array won't start

Featured Replies

I installed a new mobo. Then after that it was working. then added 4 new drives with a perc h310. formatted and now pre-clearing. But I can no longer start the array. I click it and the browser just says "waiting for 192....." cache is in unassigned for some reason as well. when I try to add it to cache drives, it does the same "waiting"

Diagnostics attached.

predator-diagnostics-20200228-1622.zip

Edited by dbinott

Can you do a graceful shutdown, if not then wait for one of the other guys to help, you don't want to repeatedly force shutdown.

 

My guess is that this has something to do with the Flash device, is it on a USB 3? If so use USB 2.0

  • [11:0:0:0]   disk    SanDisk  Cruzer Fit       1.00  /dev/sds   /dev/sg0 state=running queue_depth=1 scsi_level=7 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/11:0:0:0  [/sys/devices/pci0000:00/0000:00:14.0/usb3/3-11/3-11:1.0/host11/target11:0:0/11:0:0:0]

Also your 4TB Seagate with serial # Z1Z23XWV00009411RSUV seems to be disabled, I can't tell why

 

Finally, implement syslog server, this log is only since last 17 minutes...

 

Feb 28 15:07:02 Predator kernel: usb 3-11: USB disconnect, device number 4

Feb 28 15:07:02 Predator kernel: md: unRAID driver removed
Feb 28 15:07:02 Predator emhttpd: shcmd (70): modprobe md-mod super=/boot/config/super.dat
Feb 28 15:07:02 Predator kernel: FAT-fs (sda1): Directory bread(block 29976) failed
Feb 28 15:07:02 Predator kernel: FAT-fs (sda1): Directory bread(block 29977) failed
Feb 28 15:07:02 Predator kernel: FAT-fs (sda1): Directory bread(block 29978) failed
Feb 28 15:07:02 Predator kernel: FAT-fs (sda1): Directory bread(block 29979) failed
Feb 28 15:07:02 Predator kernel: FAT-fs (sda1): Directory bread(block 29980) failed
Feb 28 15:07:02 Predator kernel: FAT-fs (sda1): Directory bread(block 29981) failed
Feb 28 15:07:02 Predator kernel: FAT-fs (sda1): Directory bread(block 29982) failed
Feb 28 15:07:02 Predator kernel: FAT-fs (sda1): Directory bread(block 29983) failed
Feb 28 15:07:02 Predator kernel: FAT-fs (sda1): Directory bread(block 29984) failed
Feb 28 15:07:02 Predator kernel: FAT-fs (sda1): Directory bread(block 29985) failed
Feb 28 15:07:02 Predator kernel: md: unRAID driver 2.9.13 installed
Feb 28 15:07:02 Predator kernel: read_file: error 2 opening /boot/config/super.dat
Feb 28 15:07:02 Predator kernel: md: could not read superblock from /boot/config/super.dat
Feb 28 15:07:02 Predator kernel: md: initializing superblock
Feb 28 15:07:02 Predator emhttpd: Unregistered - flash device error (ENOFLASH3)

Feb 28 15:07:04 Predator unassigned.devices: Error: Cannot mount device '/dev/sds1' with label 'UNRAID'.

Edited by Dissones4U

  • Author

So I tried some different ports and getting the same bread issue. I am beyond frustrated right now. 

  • Author

Yes. Tried all ports. I had to go back to my original mobo. Must have been something wrong with the board.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.