Greyhole pool is missing
-
-
Did the drive fail?
-
The drive did not fail, at least I don't think so. Using putty I can cd to the drive, although it's contents are strange:
Coderoot@openmediavault:/media/7fb5cc61-3820-4cc5-868c-d458bf383370# ls ls: reading directory .: Input/output error
In the OMV gui -> Storage -> file systems all of my drives are online. They are all nearly full though, which I think is also strange.
In terms of restoring data, I wonder if the trash is full, amongst other things. Reading about the greyhole trash, I keep seeing references to .gh_trash folders. I can't find anything like this on my drives. I have trash enabled.
I really have no idea what to do.
thanks
-
The input/output error when executing ls is a bad sign that drive has probably failed. What is the output of: mount
-
Code
Alles anzeigenroot@openmediavault:/media/7fb5cc61-3820-4cc5-868c-d458bf383370# ls ls: reading directory .: Input/output error root@openmediavault:/media/7fb5cc61-3820-4cc5-868c-d458bf383370# mount /dev/sde1 on / type ext4 (rw,errors=remount-ro) tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) udev on /dev type tmpfs (rw,mode=0755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) tmpfs on /tmp type tmpfs (rw) /dev/sda1 on /media/8307d85e-116f-466b-bb84-366f9028fa08 type ext4 (rw,noexec,_netdev,acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0) /dev/sdb1 on /media/8b48f1c6-de36-454f-9427-90fb1953b794 type ext4 (rw,noexec,_netdev,acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0) /dev/sdc1 on /media/7fb5cc61-3820-4cc5-868c-d458bf383370 type ext4 (rw,noexec,_netdev,acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0) /dev/sdd1 on /media/97516248-60be-46bc-8528-5eb3d1708497 type ext4 (rw,noexec,_netdev,acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0) /dev/sdf1 on /media/d9c99781-65cb-4d40-8f3e-914be59ca694 type ext4 (rw,noexec,_netdev,acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0)
-
Well, the drive is still mounted read/write but there is something wrong with it. Look in the output of dmesg for errors.
-
There are many output errors like below:
Code
Alles anzeigen[2865893.679585] sd 2:0:0:0: [sdc] CDB: Read(10): 28 00 00 01 29 08 00 00 08 00 [2865893.679592] end_request: I/O error, dev sdc, sector 76040 [2865893.679620] EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 [2865895.780355] sd 2:0:0:0: [sdc] Unhandled error code [2865895.780367] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DR IVER_OK [2865895.780376] sd 2:0:0:0: [sdc] CDB: Read(10): 28 00 00 01 29 08 00 00 08 00 [2865895.780394] end_request: I/O error, dev sdc, sector 76040 [2865895.780441] EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 [2865934.862999] sd 2:0:0:0: [sdc] Unhandled error code [2865934.863010] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DR IVER_OK [2865934.863020] sd 2:0:0:0: [sdc] CDB: Read(10): 28 00 00 01 29 08 00 00 08 00 [2865934.863038] end_request: I/O error, dev sdc, sector 76040 [2865934.863090] EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0
If the drive is lost, so be it. However, shouldn't I have access to the smb share (or the files that were on the drive) somehow? I have Greyhole setup for each smb share to have 2 file copies. I thought this meant that each file is saved on 2 different drives for redundancy. Clearly something is happening with Greyhole because my drives used to be something like 60% full and now they are 92% full.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!