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.

Unmountable Drives

Featured Replies

Hello I am new at this so need some assistance in trying to remedy this situation.

Sometimes this last weekend I installed 6.3.1 and then 6.3.2 where after reboot I noticed a couple of my drives are showing as Unmountable.

https://www.dropbox.com/s/452nla8h291031b/UnmountableHDs.JPG?dl=0

I checked FAQ and put array in Maintenance mode and ran checks

https://www.dropbox.com/s/5mhsk0xcnwl7gnr/Disk9-check.txt?dl=0

https://www.dropbox.com/s/ijnmfx51xu9j10a/Disk10-check.txt?dl=0

Then I used Putty and tried to repair disks but this is what I get for both.

https://www.dropbox.com/s/gr5a827syfvfr7k/repair.txt?dl=0

 

My parity is showing as Valid:

Parity is valid. Check will start Parity-Check. 
Write corrections to parity
  Last check completed on Mon 24 Oct 2016 11:17:06 PM EDT (120 days ago), finding 0 errors. 
Duration: 12 hours, 23 minutes, 2 seconds. Average speed: 89.7 MB/sec

 

I do have a couple spare HDs I can use to swap these out one at a time and then rebuilding?

Not really sure what's the correct way to go about this without loosing data.

 

Thanks

 

 

  • Community Expert

You need to use -L, usually there's no data loss.

Rebuilding won't fix file system corruption.

Edited by johnnie.black

  • Author
25 minutes ago, johnnie.black said:

You need to use -L, usually there's no data loss.

Rebuilding won't fix file system corruption.

Thanks

Just ran on both drives:

https://www.dropbox.com/s/fknypa5hz497d7d/Disk9-10-Fixwith-L.txt?dl=0

Looks like the drives were added back. Just scanned a few things...,thankfully had enough PAR files for 1 image recovery, Everything else seems ok so far.

I do have a Cache drive that is still Unmounted. Don't think I used it for anything since I just plugged it in originally and assigned it.

Guess I better do some kind of a Cloud Backup on this server.

  • Community Expert
1 minute ago, dimitriz said:

I do have a Cache drive that is still Unmounted. Don't think I used it for anything since I just plugged it in originally and assigned it.

Did you format it? It need to be formatted after initial assignment.

If yes and it contains important data that you want to try to recover post your diagnostics.

  • Author
8 minutes ago, johnnie.black said:

Did you format it? It need to be formatted after initial assignment.

If yes and it contains important data that you want to try to recover post your diagnostics.

It was added and Formatted previously, however I have never saw that it had anything on it at all. Usage never changed as was always at 0.

I only use this server for Plex and even then hardly ever, it's more for storage and backup of the media and whatever else.

Whats the command to recover Cache drive? It has to be in Maint mode, correct?

xfs_repair -vL /dev/?

Thanks!

  • Community Expert
xfs_repair -v /dev/sdX1

For XFS cache only, start in maintenance mode, note the 1 in the end.

Only use -L if needed.

 

 

  • Author
5 minutes ago, johnnie.black said:

xfs_repair -v /dev/sdX1

For XFS cache only, start in maintenance mode, note the 1 in the end.

Only use -L if needed.

 

 

root@Tower:/dev# ls
aer_inject       md3                 ptyp2   sg10     tty28  tty62
block/           md4                 ptyp3   sg11     tty29  tty63
bsg/             md5                 ptyp4   sg12     tty3   tty7
btrfs-control    md6                 ptyp5   sg13     tty30  tty8
bus/             md7                 ptyp6   sg2      tty31  tty9
char/            md8                 ptyp7   sg3      tty32  ttyS0
console          md9                 random  sg4      tty33  ttyp0
core@            mem                 rtc@    sg5      tty34  ttyp1
cpu/             memory_bandwidth    rtc0    sg6      tty35  ttyp2
cpu_dma_latency  mouse@              sda     sg7      tty36  ttyp3
disk/            mpt2ctl             sda1    sg8      tty37  ttyp4
fd@              mpt3ctl             sdb     sg9      tty38  ttyp5
fd0              nbd0                sdb1    shm/     tty39  ttyp6
full             nbd1                sdc     stderr@  tty4   ttyp7
fuse             nbd10               sdc1    stdin@   tty40  urandom
hpet             nbd11               sdd     stdout@  tty41  vcs
hwrng            nbd12               sdd1    tty      tty42  vcs1
initctl|         nbd13               sde     tty0     tty43  vcs2
input/           nbd14               sde1    tty1     tty44  vcs3
kmem             nbd15               sdf     tty10    tty45  vcs4
kmsg             nbd2                sdg     tty11    tty46  vcs5
log=             nbd3                sdg1    tty12    tty47  vcs6
loop-control     nbd4                sdh     tty13    tty48  vcsa
loop0            nbd5                sdh1    tty14    tty49  vcsa1
loop1            nbd6                sdi     tty15    tty5   vcsa2
loop2            nbd7                sdi1    tty16    tty50  vcsa3
loop3            nbd8                sdj     tty17    tty51  vcsa4
loop4            nbd9                sdj1    tty18    tty52  vcsa5
loop5            net/                sdk     tty19    tty53  vcsa6
loop6            network_latency     sdk1    tty2     tty54  vfio/
loop7            network_throughput  sdl     tty20    tty55  vga_arbiter
lp0              null                sdl1    tty21    tty56  vhost-net
mapper/          port                sdm     tty22    tty57  xconsole|
mcelog           ppp                 sdm1    tty23    tty58  zero
md1              ptmx                sdn     tty24    tty59
md10             pts/                sdn1    tty25    tty6
md11             ptyp0               sg0     tty26    tty60
md2              ptyp1               sg1     tty27    tty61
root@Tower:/dev# xfs_repair -v /dev/sdX1
/dev/sdX1: No such file or directory
/dev/sdX1: No such file or directory

fatal error -- couldn't initialize XFS library
 

  • Community Expert

sorry, forgot to mention, replace X with the correct identifier, the one report on the main page for your cache device, eg:

xfs_repair -v /dev/sdf1
  • Author
22 minutes ago, johnnie.black said:

sorry, forgot to mention, replace X with the correct identifier, the one report on the main page for your cache device, eg:


xfs_repair -v /dev/sdf1

Ahh ok, duh.,my bad! lol

There is no sdf1 on that list only sdf.

Wait a min, sdf = Flash Drive and sdd is Cache (from Unraid Main Menu)

so I should do:

xfs_repair -v /dev/sdd1

 

  • Community Expert
1 minute ago, dimitriz said:

so I should do:


xfs_repair -v /dev/sdd1

Yes, sdf was an example.

  • Author

root@Tower:/dev# xfs_repair -v /dev/sdd1
Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!!

attempting to find secondary superblock...
...............................................................................................................................

.....Sorry, could not find valid secondary superblock
Exiting now.
 

  • Community Expert

Are you sure the cache was xfs? default is btrfs.

  • Author

Ohh that I dunno..., it's whatever default is I guess btrfs.

So I take it should be:

btrfs scrub start -B /dev/sdd1

 

  • Community Expert

Post your diagnostics, Tools -> Diagnostics

  • Community Expert

hmmm, never seen this before:

cacheFsType="fuseblk"

With the array stopped, go to the main page, click on the cache disk take a screenshot of current setting for "file system type", then change it to "auto", start array, if it still doesn't mount post new diagnostics.

Edited by johnnie.black

  • Author
10 minutes ago, johnnie.black said:

hum, never seen this before:


cacheFsType="fuseblk"

With the array stopped, go to the main page, click on the cache disk take a screenshot of current setting for "file system type", then change it to "auto", start array, if it still doesn't mount post new diagnostics.

The File System was already set to Auto.

When I initially set it up I pluged this old 120GB SSD thinking it would speed up my Plex transcoding or whatever. I haven't messed with it besides assigning it as a Cache drive.

Cache-Stopped.JPG

  • Community Expert

Change it to any of the other settings, click apply, then back to auto, and apply again.

Edited by johnnie.black

  • Author

Still comes up as Unmountable.

Should I try starting array with it in something other then auto then stop and revert it back again?

tower-diagnostics-20170221-1035.zip

  • Community Expert

That fixed the setting:

cacheFsType="auto"

Now it's trying to mount correctly but it looks like there's no file system on the cache device, if it was empty probably best to just format it, whatever happened to change that setting may have damage the cache filesystem.

Feb 21 10:33:48 Tower emhttp: shcmd (39765): set -o pipefail ; mount -t btrfs,xfs,reiserfs -o noatime,nodiratime /dev/sdd1 /mnt/cache |& logger
Feb 21 10:33:48 Tower root: mount: wrong fs type, bad option, bad superblock on /dev/sdd1,
Feb 21 10:33:48 Tower root:        missing codepage or helper program, or other error
Feb 21 10:33:48 Tower root:
Feb 21 10:33:48 Tower root:        In some cases useful info is found in syslog - try
Feb 21 10:33:48 Tower root:        dmesg | tail or so.
Feb 21 10:33:48 Tower emhttp: err: shcmd: shcmd (39765): exit status: 32
Feb 21 10:33:48 Tower emhttp: mount error: No file system (32)

 

  • Author

Ok, cool. I formatted it and it's added back to array.

Everything seems cool.

Should I run Parity Check after all this?

 

Thanks

  • Community Expert

Parity should remain synced through all this, but it's always good to make sure.

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.