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.

Device Missing following power failure

Featured Replies

Hi all, I'm pretty new to this so please be patient. 

 

I had a power failure today and my server went down. When I booted it back up, I'm unable to restart my array because it looks like a disk is missing. (Added a screenshot)

 

I can't seem to find any information on ways to fix my issue aside from starting a new configuration and removing the disk from the array. 

 

Any help is more than welcome! 

 

image.thumb.png.81bfaa1a759102d4c367038a713c9f98.png

  • Community Expert

Go to Tools - Diagnostics and attach the complete Diagnostics zip file to your next post. 

 

Can you see the disk in the BIOS?

  • Author

Attached is the diagnostics file. I couldn't find the location in the BIOS to see the drives but will check that tomorrow. Any help you can provide would be awesome! 

tower-diagnostics-20190121-0009.zip

That missing drive doesnt seem to show up in your syslog at all nor in the device list. Have you tried shutting down and doing a power cycle? Also recheck the power cables on the drives.

 


[0:0:0:0]    disk    Kingston DataTraveler 3.0       /dev/sda   /dev/sg0 
  state=running queue_depth=1 scsi_level=7 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/0:0:0:0  [/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/host0/target0:0:0/0:0:0:0]
[3:0:0:0]    disk    ATA      Samsung SSD 850  3B6Q  /dev/sdb   /dev/sg1 
  state=running queue_depth=32 scsi_level=6 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/3:0:0:0  [/sys/devices/pci0000:00/0000:00:1f.2/ata3/host3/target3:0:0/3:0:0:0]
[8:0:0:0]    disk    ATA      ST4000DM004-2CV1 0001  /dev/sdc   /dev/sg2 
  state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/8:0:0:0  [/sys/devices/pci0000:00/0000:00:02.0/0000:03:00.0/host8/port-8:0/end_device-8:0/target8:0:0/8:0:0:0]
[8:0:1:0]    disk    ATA      WDC WD20EARS-22M AB51  /dev/sdd   /dev/sg3 
  state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/8:0:1:0  [/sys/devices/pci0000:00/0000:00:02.0/0000:03:00.0/host8/port-8:1/end_device-8:1/target8:0:1/8:0:1:0]
[8:0:2:0]    disk    ATA      ST4000DM004-2CV1 0001  /dev/sde   /dev/sg4 
  state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/8:0:2:0  [/sys/devices/pci0000:00/0000:00:02.0/0000:03:00.0/host8/port-8:2/end_device-8:2/target8:0:2/8:0:2:0]
[8:0:3:0]    disk    ATA      ST4000DM004-2CV1 0001  /dev/sdf   /dev/sg5 
  state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/8:0:3:0  [/sys/devices/pci0000:00/0000:00:02.0/0000:03:00.0/host8/port-8:3/end_device-8:3/target8:0:3/8:0:3:0]
[8:0:4:0]    disk    ATA      ST4000DM000-1F21 CC54  /dev/sdg   /dev/sg6 
  state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/8:0:4:0  [/sys/devices/pci0000:00/0000:00:02.0/0000:03:00.0/host8/port-8:4/end_device-8:4/target8:0:4/8:0:4:0]
[8:0:5:0]    disk    ATA      ST4000DM005-2DP1 0001  /dev/sdh   /dev/sg7 
  state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/8:0:5:0  [/sys/devices/pci0000:00/0000:00:02.0/0000:03:00.0/host8/port-8:5/end_device-8:5/target8:0:5/8:0:5:0]
[8:0:6:0]    disk    ATA      ST4000DM005-2DP1 0001  /dev/sdj   /dev/sg9 
  state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/8:0:6:0  [/sys/devices/pci0000:00/0000:00:02.0/0000:03:00.0/host8/port-8:6/end_device-8:6/target8:0:6/8:0:6:0]
[9:0:0:0]    disk    ATA      ST8000DM004-2CX1 0001  /dev/sdi   /dev/sg8 
  state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/9:0:0:0  [/sys/devices/pci0000:00/0000:00:03.0/0000:06:00.0/host9/port-9:0/end_device-9:0/target9:0:0/9:0:0:0]
[9:0:2:0]    disk    ATA      ST4000DM004-2CV1 0001  /dev/sdk   /dev/sg10
  state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/9:0:2:0  [/sys/devices/pci0000:00/0000:00:03.0/0000:06:00.0/host9/port-9:2/end_device-9:2/target9:0:2/9:0:2:0]
[9:0:3:0]    disk    ATA      ST4000DM004-2CV1 0001  /dev/sdl   /dev/sg11
  state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/9:0:3:0  [/sys/devices/pci0000:00/0000:00:03.0/0000:06:00.0/host9/port-9:3/end_device-9:3/target9:0:3/9:0:3:0]
[9:0:4:0]    disk    ATA      ST4000DM004-2CV1 0001  /dev/sdm   /dev/sg12
  state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/9:0:4:0  [/sys/devices/pci0000:00/0000:00:03.0/0000:06:00.0/host9/port-9:4/end_device-9:4/target9:0:4/9:0:4:0]
[9:0:5:0]    disk    ATA      ST4000DM004-2CV1 0001  /dev/sdn   /dev/sg13
  state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/9:0:5:0  [/sys/devices/pci0000:00/0000:00:03.0/0000:06:00.0/host9/port-9:5/end_device-9:5/target9:0:5/9:0:5:0]

  • Author

I’ve tried a power cycle a couple of times and have tried pulling the drive and putting it in another bay. Neither has worked. I’ll check the cables next. 

  • Author

So I just pulled the drive and connected it to my Windows PC. It shows up in Device Manager. 

 

I'm going to check the power cables on my Unraid box to see if there may be an issue there. 

  • Community Expert
21 hours ago, Celtic said:

I'm unable to restart my array because it looks like a disk is missing. (Added a screenshot)

Just noticed you don't have parity. If you did then you would have been able to start the array with the disk emulated by the parity calculation. And you would be able to rebuild to another disk if necessary.

 

That's a lot of disks to not have parity. Any reason why you don't?

 

Do you have another copy of anything important and irreplaceable? That should be your first priority.

  • Author

Yeah, I was putting that off and clearly for too long. 

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.