Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - MasterCATZ

Pages: [1] 2 3 ... 5
1
RAID-F on Linux / Re: Another Upgrade another configuration fail
« on: February 04, 2017, 08:22:59 pm »
that was already attached a few messages ago ... back in May

here is another as I have used one of the flexraid PU drives to replace a failed zfs drive recently


really need to work this out soon

needing to go kernel 4.10 soon for my new Ryzen CPU



2
Buying Recommendations / Re: SAS 9201-16e and FlexRAID
« on: December 03, 2016, 02:39:24 pm »
thinking about getting those as well

3
RAID-F Feature Requests / Re: Offsite Backup into Cloud (e.g Amazon S3)
« on: December 03, 2016, 02:27:35 pm »
I use glusterfs

4
RAID-F on Linux / Re: Another Upgrade another configuration fail
« on: December 03, 2016, 01:16:03 pm »
no

still can not get them to show
and my SSD's that used to always show don't anymore either ... need to work something out soon down to last 200 gig and need to expand soon , I have been cheating just using the last drive that was beeing filled and planning on using my old 3Tb  ZFS drives for Flexraid and get some 8 Tb drives for the new ZFS array 
the only reason I use FlexRaid is I rather have a file based system for my multimedia so if a failure does happen I can still access my files normally , or only lose a small % of DATA which can easily be replaced from backups

One thing I would like some script / log during a scan that keeps track of all the files on each drive
which can help us identify what files used to be on a drive so you know what has been lost if full redundancy fails

I was just literally in the GUI and it just showed dru1,5,8,2 and the old un re-formatted dru8

ran mount - l

and now its doubled them up ... took screenshot

LSB Version:   core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
Distributor ID:   Ubuntu
Description:   Ubuntu 16.04.1 LTS
Release:   16.04
Codename:   xenial
kernel 4.7.3-040703-generic
FlexRAID-2.1-Final-2015-11-01.bin



its been so long since I did this can not even remember how I reformatted them

but I DD zero'd everything apart from the drives that will be used as PPU this time around

what I have been meaning to try and working out what drives are on what controller incase this is the problem
but I doubt it as every other program accesses the drives just fine ...

01:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 02)
05:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 02)






5
RAID-F on Linux / Re: Another Upgrade another configuration fail
« on: June 10, 2016, 03:44:24 pm »
can we please do a team viewer session so this can be sorted
I still have not gotten flexraid to pick up all the drives again


6
RAID-F on Linux / Re: Another Upgrade another configuration fail
« on: May 02, 2016, 10:35:24 pm »
just got me beat why so random

the S.M.A.R.T system inside flexraid See's them all as well

I think it might be something inside the latest version

as I have same results with live CD that only had what ever version it pulls of the site

I do still have 3x old versions I could test with now that my zfs system is running again
 which is the whole reason this saga started as I needed to go 16.04 for the new zfs system to run as its now built into the kernel 4 series




7
RAID-F on Linux / Re: Another Upgrade another configuration fail
« on: May 01, 2016, 03:24:06 pm »
new reply due to 4x attachment restriction

and then testing with mounted fstab via LABEL instead of UUID

LABEL=Raid-F.HDD1.DRU1 /mnt/Raid-F.HDD1.DRU1 auto nosuid,nodev,nofail 0 0
LABEL=Raid-F.HDD2.DRU2 /mnt/Raid-F.HDD2.DRU2 auto nosuid,nodev,nofail 0 0
LABEL=Raid-F.HDD3.DRU3 /mnt/Raid-F.HDD3.DRU3 auto nosuid,nodev,nofail 0 0
LABEL=Raid-F.HDD4.DRU4 /mnt/Raid-F.HDD4.DRU4 auto nosuid,nodev,nofail 0 0
LABEL=Raid-F.HDD5.DRU5 /mnt/Raid-F.HDD5.DRU5 auto nosuid,nodev,nofail 0 0
LABEL=Raid-F.HDD6.DRU6 /mnt/Raid-F.HDD6.DRU6 auto nosuid,nodev,nofail 0 0
LABEL=Raid-F.HDD7.DRU7 /mnt/Raid-F.HDD7.DRU7 auto nosuid,nodev,nofail 0 0
LABEL=Raid-F.HDD8.DRU8 /mnt/Raid-F.HDD8.DRU8 auto nosuid,nodev,nofail 0 0


= NONE of them show
and the drives are indeed mounted and accessible ...

Exact same settings another reboot
some of them show ??

and flexraid is on trace but nothing reported ..

8
RAID-F on Linux / Re: Another Upgrade another configuration fail
« on: May 01, 2016, 02:55:14 pm »
fresh reboot yet again random pick ups fstab

UUID=a63e3d1f-0a2d-4309-b7d4-7ebfbe260601 /mnt/Raid-F.HDD1.DRU1 ext4 defaults 0 0
UUID=788d06e9-d51e-444e-8cf3-740900ea15fc /mnt/Raid-F.HDD2.DRU2 ext4 defaults 0 0
UUID=9940c644-ecca-4364-a5b2-07e31381a657 /mnt/Raid-F.HDD3.DRU3 ext4 defaults 0 0
UUID=a2176ea6-1787-477b-8dde-af9f0b14587d /mnt/Raid-F.HDD4.DRU4 ext4 defaults 0 0
UUID=bb37cf5e-b0c6-4e4b-bd63-d36d51489a4c /mnt/Raid-F.HDD5.DRU5 ext4 defaults 0 0
UUID=a60cb301-8939-4752-9d50-6c1f1c6002bb /mnt/Raid-F.HDD6.DRU6 ext4 defaults 0 0
UUID=a38e47e4-aebf-43c4-8041-d8b81442c924 /mnt/Raid-F.HDD7.DRU7 ext4 defaults 0 0
UUID=43ca34ed-5611-4220-beef-550bc1d30cc8 /mnt/Raid-F.HDD8.DRU8 ext4 defaults 0 0


I could also provide boot sector / partition table  images etc if you want to check them

I will also do other reboots with it all mounted via GUI like you said without fstab
 ( fstab is what I used to use sucsessfully.. )

= ALMOST all of them show but DRU3 ...







9
RAID-F on Linux / Re: Another Upgrade another configuration fail
« on: April 29, 2016, 06:51:30 am »
/dev/sdh1 on /mnt/Raid-F.HDD7.DRU7 type ext4 (rw,relatime,data=ordered) [Raid-F.HDD7.DRU7]
/dev/sdg1 on /mnt/Raid-F.HDD5.DRU5 type ext4 (rw,relatime,data=ordered) [Raid-F.HDD5.DRU5]
/dev/sdf1 on /mnt/Raid-F.HDD1.DRU1 type ext4 (rw,relatime,data=ordered) [Raid-F.HDD1.DRU1]
/dev/sde1 on /mnt/Raid-F.HDD2.DRU2 type ext4 (rw,relatime,data=ordered) [Raid-F.HDD2.DRU2]
/dev/sdj1 on /mnt/Raid-F.HDD8.DRU8 type ext4 (rw,relatime,data=ordered) [Raid-F.HDD8.DRU8]
/dev/sdi1 on /mnt/Raid-F.HDD6.DRU6 type ext4 (rw,relatime,data=ordered) [Raid-F.HDD6.DRU6]
/dev/sdn1 on /mnt/Raid-F.HDD4.DRU4 type ext4 (rw,relatime,data=ordered) [Raid-F.HDD4.DRU4]
/dev/sdp1 on /mnt/Raid-F.HDD3.DRU3 type ext4 (rw,relatime,data=ordered) [Raid-F.HDD3.DRU3]


flexraid not picking all of them up

all drives and mount options are identically done I have spent all week erasing drives and coping data onto them so they are fresh

I am fresh out of idea's

every other program picks up the mounted drives

root@aio:~# fdisk -l
Disk /dev/ram0: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram1: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram2: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram3: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram4: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram5: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram6: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram7: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram8: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram9: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram10: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram11: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram12: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram13: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram14: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram15: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0001c56c

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1  *         2048     20479     18432     9M 83 Linux
/dev/sda2           22526 250068991 250046466 119.2G  5 Extended
/dev/sda5           22528   1973699   1951172 952.7M 83 Linux
/dev/sda6         1976320 114894288 112917969  53.9G 83 Linux
/dev/sda7       114896896 217296895 102400000  48.8G 83 Linux
/dev/sda8       217298944 233682943  16384000   7.8G 83 Linux
/dev/sda9       233684992 250068991  16384000   7.8G 83 Linux


Disk /dev/sdb: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0001c56c

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sdb1  *         2048     20479     18432     9M 83 Linux
/dev/sdb2           22526 250068991 250046466 119.2G  5 Extended
/dev/sdb5           22528   1974271   1951744   953M 83 Linux
/dev/sdb6         1976320 109391871 107415552  51.2G 83 Linux
/dev/sdb7       109393920 232273919 122880000  58.6G 83 Linux
/dev/sdb8       232484864 250060799  17575936   8.4G 83 Linux


Disk /dev/sdc: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000309bd

Device     Boot Start       End   Sectors   Size Id Type
/dev/sdc1        2048 250068991 250066944 119.2G 83 Linux


Disk /dev/sdd: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000b8eb1

Device     Boot    Start       End   Sectors  Size Id Type
/dev/sdd1  *        2048    206847    204800  100M  7 HPFS/NTFS/exFAT
/dev/sdd2         206848  61646847  61440000 29.3G  7 HPFS/NTFS/exFAT
/dev/sdd3       61646848 250068991 188422144 89.9G 83 Linux


Disk /dev/sdf: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 5ACC1FFC-4759-4EB1-8BC4-15DF846B98D3

Device     Start        End    Sectors  Size Type
/dev/sdf1   2048 5860532223 5860530176  2.7T Linux filesystem


Disk /dev/sdi: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 1B1A9091-4ECC-4994-8907-08A75A5ED375

Device     Start        End    Sectors  Size Type
/dev/sdi1   2048 5860532223 5860530176  2.7T Linux filesystem


Disk /dev/sde: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: A9D27798-BAE1-4EA4-B923-40EF98403C39

Device     Start        End    Sectors  Size Type
/dev/sde1   2048 5860532223 5860530176  2.7T Linux filesystem


Disk /dev/sdh: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: D9F1ABFA-ABDA-4573-890F-1AE7C0DD7577

Device     Start        End    Sectors  Size Type
/dev/sdh1   2048 5860532223 5860530176  2.7T Linux filesystem


Disk /dev/sdg: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: D413F3B8-35CA-4982-A164-E53FF6AE6A67

Device     Start        End    Sectors  Size Type
/dev/sdg1   2048 5860532223 5860530176  2.7T Linux filesystem


Disk /dev/sdj: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 74A8CD21-47FA-4F5D-8816-94807C35F9CE

Device     Start        End    Sectors  Size Type
/dev/sdj1   2048 5860532223 5860530176  2.7T Linux filesystem


Disk /dev/sdm: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 3E5149E1-5010-4042-9E7B-B787F75E3E3F

Device          Start        End    Sectors  Size Type
/dev/sdm1        2048 5860515839 5860513792  2.7T Solaris /usr & Apple ZFS
/dev/sdm9  5860515840 5860532223      16384    8M Solaris reserved 1


Disk /dev/sdr: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: F57E6C2D-A2D4-C540-BF3D-46C88BFBF416

Device          Start        End    Sectors  Size Type
/dev/sdr1        2048 5860515839 5860513792  2.7T Solaris /usr & Apple ZFS
/dev/sdr9  5860515840 5860532223      16384    8M Solaris reserved 1


Disk /dev/sdq: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: BDD60C72-549E-4452-AC52-84C8E295759A

Device     Start        End    Sectors  Size Type
/dev/sdq1   2048 5860530175 5860528128  2.7T Microsoft basic data


Disk /dev/sdp: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: ACB90F6D-F850-448C-8DCE-F23BA43EE095

Device     Start        End    Sectors  Size Type
/dev/sdp1   2048 5860532223 5860530176  2.7T Linux filesystem


Disk /dev/sdk: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 6AA7FB05-FC06-AE45-A3C6-90148D1C4C69

Device          Start        End    Sectors  Size Type
/dev/sdk1        2048 5860515839 5860513792  2.7T Solaris /usr & Apple ZFS
/dev/sdk9  5860515840 5860532223      16384    8M Solaris reserved 1


Disk /dev/sdn: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 488F6522-FF4F-4EE3-AEAC-15FF008BA51A

Device     Start        End    Sectors  Size Type
/dev/sdn1   2048 5860532223 5860530176  2.7T Linux filesystem


Disk /dev/sdl: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 46919F2C-5E5A-B24B-93DD-E1DFAF79D056

Device          Start        End    Sectors  Size Type
/dev/sdl1        2048 5860515839 5860513792  2.7T Solaris /usr & Apple ZFS
/dev/sdl9  5860515840 5860532223      16384    8M Solaris reserved 1


Disk /dev/sds: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: ECF2293D-B432-F540-8EFC-C7FD1BC8DD20

Device          Start        End    Sectors  Size Type
/dev/sds1        2048 5860515839 5860513792  2.7T Solaris /usr & Apple ZFS
/dev/sds9  5860515840 5860532223      16384    8M Solaris reserved 1


Disk /dev/sdo: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 72B659AF-92DE-44FA-A8F4-4E83857B8B80

Device     Start        End    Sectors  Size Type
/dev/sdo1   2048 5860530175 5860528128  2.7T Microsoft basic data


Disk /dev/sdt: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: F5564151-7813-D349-B740-004C5D28672A

Device          Start        End    Sectors  Size Type
/dev/sdt1        2048 5860515839 5860513792  2.7T Solaris /usr & Apple ZFS
/dev/sdt9  5860515840 5860532223      16384    8M Solaris reserved 1
root@aio:~#


root@aio:~# parted -l
Model: ATA OCZ-AGILITY3 (scsi)
Disk /dev/sda: 128GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start   End     Size    Type      File system  Flags
 1      1049kB  10.5MB  9437kB  primary   ext2         boot
 2      11.5MB  128GB   128GB   extended
 5      11.5MB  1011MB  999MB   logical   ext4
 6      1012MB  58.8GB  57.8GB  logical   ext4
 7      58.8GB  111GB   52.4GB  logical   ext4
 8      111GB   120GB   8389MB  logical   ext4
 9      120GB   128GB   8389MB  logical   ext4


Model: ATA OCZ-AGILITY3 (scsi)
Disk /dev/sdb: 128GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start   End     Size    Type      File system  Flags
 1      1049kB  10.5MB  9437kB  primary   ext2         boot
 2      11.5MB  128GB   128GB   extended
 5      11.5MB  1011MB  999MB   logical   ext4
 6      1012MB  56.0GB  55.0GB  logical   ext4
 7      56.0GB  119GB   62.9GB  logical   ext4
 8      119GB   128GB   8999MB  logical   ext4


Model: ATA OCZ-AGILITY3 (scsi)
Disk /dev/sdc: 128GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start   End    Size   Type     File system  Flags
 1      1049kB  128GB  128GB  primary  btrfs


Model: ATA OCZ-AGILITY3 (scsi)
Disk /dev/sdd: 128GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  106MB   105MB   primary  ntfs         boot
 2      106MB   31.6GB  31.5GB  primary  ntfs
 3      31.6GB  128GB   96.5GB  primary  ext4


Model: ATA WDC WD30EZRX-00D (scsi)
Disk /dev/sde: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name              Flags
 1      1049kB  3001GB  3001GB  ext4         Raid-F.HDD2.DRU2


Model: ATA WDC WD30EZRX-00D (scsi)
Disk /dev/sdf: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name              Flags
 1      1049kB  3001GB  3001GB  ext4         Raid-F.HDD1.DRU1


Model: ATA WDC WD30EZRX-00D (scsi)
Disk /dev/sdg: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name              Flags
 1      1049kB  3001GB  3001GB  ext4         Raid-F.HDD5.DRU5


Model: ATA WDC WD30EZRX-00D (scsi)
Disk /dev/sdh: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name              Flags
 1      1049kB  3001GB  3001GB  ext4         Raid-F.HDD7.DRU7


Model: ATA WDC WD30EZRX-00D (scsi)
Disk /dev/sdi: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name              Flags
 1      1049kB  3001GB  3001GB  ext4         Raid-F.HDD6.DRU6


Model: ATA WDC WD30EZRX-00D (scsi)
Disk /dev/sdj: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name              Flags
 1      1049kB  3001GB  3001GB  ext4         Raid-F.HDD8.DRU8


Model: ATA WDC WD30EZRX-00D (scsi)
Disk /dev/sdk: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  3001GB  3001GB  zfs          zfs
 9      3001GB  3001GB  8389kB


Model: ATA WDC WD30EZRX-00D (scsi)
Disk /dev/sdl: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  3001GB  3001GB  zfs          zfs
 9      3001GB  3001GB  8389kB


Model: ATA WDC WD30EZRX-00D (scsi)
Disk /dev/sdm: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  3001GB  3001GB  zfs          zfs
 9      3001GB  3001GB  8389kB


Model: ATA WDC WD30EZRX-00D (scsi)
Disk /dev/sdn: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name              Flags
 1      1049kB  3001GB  3001GB  ext4         Raid-F.HDD4.DRU4


Model: ATA WDC WD30EZRX-00D (scsi)
Disk /dev/sdo: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  3001GB  3001GB  ext4               msftdata


Model: ATA WDC WD30EZRX-00D (scsi)
Disk /dev/sdp: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name              Flags
 1      1049kB  3001GB  3001GB  ext4         Raid-F.HDD3.DRU3


Model: ATA WDC WD30EZRX-00D (scsi)
Disk /dev/sdq: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  3001GB  3001GB  ext4               msftdata


Model: ATA WDC WD30EZRX-00D (scsi)
Disk /dev/sdr: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  3001GB  3001GB  zfs          zfs
 9      3001GB  3001GB  8389kB


Model: ATA WDC WD30EZRX-00D (scsi)
Disk /dev/sds: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  3001GB  3001GB  zfs          zfs
 9      3001GB  3001GB  8389kB


Model: ATA WDC WD30EZRX-00D (scsi)
Disk /dev/sdt: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  3001GB  3001GB  zfs          zfs
 9      3001GB  3001GB  8389kB


root@aio:~#




10
RAID-F on Linux / Re: Another Upgrade another configuration fail
« on: April 25, 2016, 10:53:05 pm »
onto more strangeness

just when I thought all was going well

the old PPU drives where Both DD  Wiped 100% Zero's partitioned to GPT / Formatted ext4 and data rsynced  from the DRU drives and now they will not get detected

1 drive only gets picked up if mounted via GUI ( /media/aio/Raid-F.HDD8.DRU8 )
and the other only picks up if  mounted via fstab (/mnt/Raid-F.HDD7.DRU7 )
 ( as long as x-gvfs-show is NOT used )
if I use the same settings its either one way or the other but never with both drives

*edit*
now they are both  picked up via fstab .. tried another reboot and back to square 1 ...
really need to verify they are going to work as intended before I wipe the next 2x DRU drives ..


one thing I did notice is when I tried unmounted the drive that flexraid did not pick up it said it was mounted by another user , so I will try and force mount them as root , I am assuming this would be the account flexraid would be using ?
*edit* but the other drive flexraid was seeing said the same thing ...


anyway to arrange team-viewer session ?

whats bugging me is all my small SSD drives are always showing

11
RAID-F on Linux / Re: Another Upgrade another configuration fail
« on: April 24, 2016, 03:32:16 pm »
Wiped the PPU drives

now all the DRU's are showing up

and the OLD PPU drives are being constantly seeked I am assuming flexraid is looking for something on them , as I have not changed their UUID yet I 0'd out every byte on the drives

12
RAID-F on Linux / Re: Another Upgrade another configuration fail
« on: April 23, 2016, 04:42:58 pm »
still got me beat even used 14.04 and 15.x live boot disks they would not even pick up my flexraid drives at all

yet any other drive I mounted after flexraid had been started worked

for now Ubuntu 16 has been randomly picking up drives mounted at boot ,
after 100+  reboots I only had 1x left to mount / swapout DRU4
but on reboot the ones that were swaped out where back to showing missing 

what ever it is its something on the partitions preventing flexraid to detect these drives

I recovered the files I accidentally deleted with R-Studio ,



root@aio:~# fsck /dev/sde
fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sde

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>


root@aio:~# fsck /dev/sdh
fsck from util-linux 2.27.1
If you wish to check the consistency of a BTRFS filesystem or
repair a damaged filesystem, see btrfs(8) subcommand 'check'.


still no idea why the partitions are running 2x types when they should all be ext4.. I might just have to start them again by scratch but would like to know why a perfectly working system stopped working after an OS update ...

I might try matching them up in the fstab as ext4 / btrfs and see what happens

*edit*

the only thing left is to see if FlexRAID-2.0-Final_u11b.bin works

as I know FlexRAID-2.0-Final_u12b.bin gave me problems last time

*edit*

now I can not get any old flexraid drive to show when mounted

I am at the stage I think my only solution is to blank out an PPU drive copy DRU content onto it rinse repeat and start again

I really do wish I knew what flexraid writes to the /Meta / MBR / GPT / Partition Tables to cause these issues ...

which would make this the third time I have had to start from scratch from an OS update

13
RAID-F on Linux / Re: Another Upgrade another configuration fail
« on: April 22, 2016, 12:41:24 am »
it must be an "GUID Partition Table" "Ubuntu 16.04" issue

fresh OS and now can not pick ANY of them up , with the updated OS at least some of them picked up


I have less then an hr to get our Multimedia running again for weekly shows , so I better get stuck into that ,
at least we can still browse the files manually

when I have time will whip up an Virtual machine and do some tests then log the bug


anyway to manually add them via folder path like you can do when importing existing configuration providing  PPU1 path?
so you don't have to reply on flex-raid seeking out mounted drives ?


*edit*

still no idea whats going on can not replicate

created virtual machine and used GPT partition tables , and mounted

flexraid picked these up

so why can I not get it to pick up pre existing drives that flexraid used to use ?

*edit* made an interesting discovery

half of the drives are being picked up as brtfs in gparted when they are ext4
from memory I first tried btrfs as I wanted better bitrot detection and file tools
but went back to ext4 due to no free space bug and poor speed

DRU2 was the only drive the live cd picked up

mean while Gparted reports these drives as btrfs with no partition tables
DRU5
DRU6
DRU7
DRU9

I just noticed live CD had btrfs installed while the installed OS did not so will see what happens
...
but even that makes no sense as even one of the so called btrfs drives was picked up this time DRU5

how ever DRU5 drive is also missing the _flxr_ folder that the other drives have ?
sadly I guess this means I did in fact loose 6% of my data from that drive when I went to remove FlexRaid mount points  ( at 90% and the rest of the used drives are 96% )

which has me really needing to try and get this sorted so I can attempt to recover data from PPU

I am wondering if their is anything flexraid looks for to not show the drives in the unpooled section ?



14
RAID-F on Linux / Re: Another Upgrade another configuration fail
« on: April 21, 2016, 11:09:21 am »
Ubuntu 16.04 LTS
how ever it was an upgrade not a fresh install


whats got me is why some are getting picked up as unpooled best I can get is 5 out of the 10 ...

definitely only picks up drives in fstab , I am pretty sure this is what i discovered last time as well

gives up ... fresh OS install and try again ( hopefully can still use my old home partition )

if not I'll roll-back to an old backup


testing on live cd first

 Unable to locate package sysv-rc-conf



but yet again none of the flex-raid drives are showing , yet other mounts are showing
could their be something stored on the partition causing it ?

as it seems like
"GUID Partition Table"
 is the issue because
 "Master Boot Record"
drives are showing  :-\


still going to push with fresh OS install




15
RAID-F on Linux / Re: Another Upgrade another configuration fail
« on: April 21, 2016, 01:40:18 am »
nope also a no go


drives are mounted , all the same manual  configuration /mnt/path .. only few picked up , and its random drives ...

if I have it set on auto mount /media/username/path flexraid picks up none of them ( assuming its because mounted for non root user ? )
yet picks up other drives mounted their


any idea's what to do to find the cause ?



Pages: [1] 2 3 ... 5