[SOLVED] All drives show up as unformatted

Ah, I found out how to uninstall unmenu. Just removed the line invoking it in the go script. But how do I get rid of all the stuff it left over?

BTW... Thank you so much for the great support!!!

Unmenu is not the problem. It's package manager would give you the ability to uninstall any packages you installed through unmenu. I am unsure if uninstalling unmenu automatically uninstalls packages you installed with it or not.

No, it didn't. I ended up deleteing all packages and letting the plugins redownload them. After that the deluge plugin worked again. I still have two versions of python install which worries me a little. I know that the newer one is installed by deluge, but python-2.6.6-i486-1 is not being installed by any of my plugins I believe. Where could it come from?

Any package could have installed the 2nd Python as a dependency.

One thing you can do is DELETE the 2nd Python from your Flash.

(browse ALL the folders...you need to delete the tgz, and ANY and ALL sign of the 2nd python).

SAVE YOUR FLASH to LOCAL DRIVE so you can go back.

Then restart unRAID...your syslog will show who is downloading the 2nd python.

Its even possible an old and already deleted plugin did it a long long time ago...and never cleaned up after itself.

It is the dropbox plugin... Lets see how I can get that fixed. Anyhow thank you very much for your support!

I'm late to the party here, but couldn't help feeling your problem was somewhat interesting, possibly unique.  All syslog links are gone or empty now.  Would it be possible to zip and attach your syslog one more time, so I could take a peek?  I'd like to see if there's anything useful for troubleshooting purposes, if something like this occurs again.  If too late, no problem.

It would also be helpful if you had a copy of a syslog from before all of this, when things worked without issue, just for comparison.

Here is the syslog of the broken system:

https://www.dropbox.com/s/bf7bxeqin3121ve/Archive.zip

And here is one after I removed the Dropbox plugin and therefore fixed the issue:

https://www.dropbox.com/s/6pf5k46g6t5fres/syslog

Thank you very much for the syslogs.  I didn't really expect to find much, especially with the quality of support I saw above (I was very impressed!), and your own discoveries and troubleshooting (very good by the way), but I did find a problem, one sufficiently serious that I believe requires a bug report.

I particularly wanted to figure out why drives were marked as Unformatted, so examined the drive mounting, and discovered that all attempts to mkdir any folder within /mnt were failing.  That explains why the mounts were failing, since you can't mount a drive to a non-existent folder.

Apr 18 16:19:02 Tower emhttp: Mounting disks...

Apr 18 16:19:02 Tower emhttp: shcmd (19): mkdir /mnt/disk1

Apr 18 16:19:02 Tower emhttp: _shcmd: shcmd (19): exit status: 1

Apr 18 16:19:02 Tower emhttp: shcmd (20): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md1 /mnt/disk1 |& logger

Apr 18 16:19:02 Tower logger: mount: mount point /mnt/disk1 does not exist

Apr 18 16:19:02 Tower emhttp: _shcmd: shcmd (20): exit status: 32

Apr 18 16:19:02 Tower emhttp: disk1 mount error: 32

Apr 18 16:19:02 Tower emhttp: shcmd (21): rmdir /mnt/disk1

Apr 18 16:19:02 Tower emhttp: _shcmd: shcmd (21): exit status: 1

Apr 18 16:19:02 Tower emhttp: shcmd (22): mkdir /mnt/disk2

Apr 18 16:19:02 Tower emhttp: _shcmd: shcmd (22): exit status: 1

...

Apr 18 16:19:03 Tower emhttp: shcmd (28): mkdir /mnt/user

Apr 18 16:19:03 Tower emhttp: _shcmd: shcmd (28): exit status: 1

Apr 18 16:19:03 Tower emhttp: shcmd (29): /usr/local/sbin/shfs /mnt/user -disks 16777214 -o noatime,big_writes,allow_other -o remember=0  |& logger

Apr 18 16:19:03 Tower shfs/user: fuse_main exit: 1

Apr 18 16:19:03 Tower logger: fuse: bad mount point `/mnt/user': No such file or directory

Apr 18 16:19:03 Tower emhttp: shcmd (30): crontab -c /etc/cron.d -d &> /dev/null

Apr 18 16:19:03 Tower emhttp: shcmd (31): /usr/local/sbin/emhttp_event disks_mounted

Apr 18 16:19:03 Tower emhttp_event: disks_mounted            ummm...  really?!?!

Side point: looks like we need to check the return code from mkdir.

This points to a problem with /mnt, either it doesn't exist or it has the wrong permissions and/or owner.  I took a look back through the syslog, and look what I found!

Apr 18 16:18:10 Tower logger:  --> Deleting empty directory /usr/lib/python2.6/site-packages/deluge/

Apr 18 16:18:10 Tower logger:  --> Deleting empty directory /usr/lib/python2.6/site-packages/deluge-1.3.5-py2.6.egg-info/

Apr 18 16:18:10 Tower logger:  --> Deleting empty directory /usr/doc/deluge-1.3.5/

Apr 18 16:18:10 Tower logger:  --> Deleting empty directory /mnt/cache/.apps/deluge/

Apr 18 16:18:10 Tower logger:  --> Deleting empty directory /mnt/cache/.apps/

Apr 18 16:18:10 Tower logger:  --> Deleting empty directory /mnt/cache/

Apr 18 16:18:10 Tower logger:  --> Deleting empty directory /mnt/

Apr 18 16:18:10 Tower logger:  --> Deleting empty directory /lib/systemd/system/

Apr 18 16:18:10 Tower logger:  --> Deleting empty directory /lib/systemd/

I think we can all agree that this is a VERY undesirable action!  No /mnt --> no UnRAID array!

This occurred as part of the re-installation of deluge.  As you found, deluge-1.3.5 was first installed, then deluge-1.3.6, which caused deluge-1.3.5 to be backed out, resulting in the lines above.

Two issues here, one is that package management still needs work, but we know that, as it still is in transition.  The other is that drives should never be marked as unformatted unless a checklist has been tested first - drive exists, is accessible, has valid MBR and partition table, has first partition and it's Linux, has valid ReiserFS in first partition.  I would rather see a status of 'Mount failure' than 'Unformatted', unless it meets the exact criteria of a truly unformatted drive/partition.  I agree with the comments about this earlier.  out of time at the moment for more comments...

I've added a bug report here.

Interseting...

Yes, I have found the report of an unformatted disc very drastic for the fact that I only installed a plugin that did something wrong but not something that bad. I also think that is worth a fix.

It would be nice to fix the bug itself in the deluge plugin as well. Could you explain the bug here? http://lime-technology.com/forum/index.php?topic=32457.msg300081#msg300081