Latest interface: 0.3.1
Latest system: 010
GamingUnleashed
User

24 posts

Posted on 15 November 2011 @ 03:41edited 14:51 09s
Ok the Story
I had a pool called tank and tank2 HDD's were formated as GEOM
so I had to redo them as GPT so I could install RootOnZFS for boot able backup system

everything was running sweet I copied 4tb worth of data onto the array and was soaking the LAN connection full 100meg a sec and scrubing took less then 2 hrs

I then rebooted back to my 9-Current system where for some reason it picked up the OLD ZFS system and fsck / ZFS somehow ended up recovering tank ( tank2 remained unmountable ) and corrupted all my newly added data

not to mention I was only getting 1/4 speed max that the live disk offered !!! took all night just to replace the 350gig of corrupt data

I had even selected Destroy for the Tank / Tank2 systems yet they still keep remaining

I was unable to mount the new ZFS because it was loaded via the old config
( the only way I had out was disable Zfs reboot and change a few settings so I could manually mount the correct new zfs )

ZFS on Root
GEOM: da3: the primary GPT table is corrupt or invalid.
GEOM: da3: using the secondary instead -- recovery strongly advised.
GEOM: da4: the primary GPT table is corrupt or invalid.
GEOM: da4: using the secondary instead -- recovery strongly advised.
GEOM: da5: the primary GPT table is corrupt or invalid.
GEOM: da5: using the secondary instead -- recovery strongly advised.

My Main 9-Current install that started all this loading what should have been a dead Tank setup


GEOM: da3: the primary GPT table is corrupt or invalid.
GEOM: da3: using the secondary instead -- recovery strongly advised.
GEOM: da2: the primary GPT table is corrupt or invalid.
GEOM: da2: using the secondary instead -- recovery strongly advised.
GEOM: da4: the primary GPT table is corrupt or invalid.
GEOM: da4: using the secondary instead -- recovery strongly advised.
GEOM: da5: the primary GPT table is corrupt or invalid.
GEOM: da5: using the secondary instead -- recovery strongly advised.
GEOM_LABEL: Cannot create slice SAS1P0C3D8.
GEOM_LABEL: Cannot create slice 1b2426b0-f30f-11e0-96f0-0010181a4d85.
GEOM_LABEL: Cannot create slice SAS1P0C3D8.
GEOM_LABEL: Cannot create slice 1b2426b0-f30f-11e0-96f0-0010181a4d85.


how do I go about fixing these errors .. even new data being copied onto the array gets picked up as perminate errors

scrubbing now takes twice as long also


I am planing on starting from scratch again but would like to know what went wrong and how zfs keeps refinding the dead array that was destroyed a hundred times now ( i destroy it from the GUI and from the terminal , but they still stay


da0 GPT: SAS1P1C0D1 1 TB 931.5 GiB 512 B <ATA WDC WD10EAVS-00D 1A01> Fixed Direct Access SCSI-5 device
da1 GPT: SAS1P1C1D2 1 TB 931.5 GiB 512 B <ATA WDC WD10EAVS-00D 1A01> Fixed Direct Access SCSI-5 device
da2 GPT: SAS1P1C2D3 1 TB 931.5 GiB 512 B <ATA WDC WD10EAVS-00D 1A01> Fixed Direct Access SCSI-5 device
da3 GPT: SAS1P1C3D4 1 TB 931.5 GiB 512 B <ATA WDC WD10EAVS-00D 1A01> Fixed Direct Access SCSI-5 device
da4 GPT: SAS1P0C0D5 1 TB 931.5 GiB 512 B <ATA WDC WD10EAVS-00D 1A01> Fixed Direct Access SCSI-5 device
da5 GPT: SAS1P0C1D6 1 TB 931.5 GiB 512 B <ATA WDC WD10EAVS-00D 1A01> Fixed Direct Access SCSI-5 device
da6 GPT: SAS1P0C2D7 1 TB 931.5 GiB 512 B <ATA WDC WD10EAVS-00D 1A01> Fixed Direct Access SCSI-5 device
da7 GPT: SAS1P0C3D8 1 TB 931.5 GiB 512 B <ATA WDC WD10EAVS-00D 1A01> Fixed Direct Access SCSI-5 device

I need to get this old array running so I can get by until this HDD price rise goes away I am hoping 6tb will give me another 6mnths

da0 Healthy 30°C &#8226; 86°F 473 1649 0 0 active &#8226; 0 passive 5.5 months
da1 Healthy 30°C &#8226; 86°F 473 1648 0 0 active &#8226; 0 passive 5.5 months
da2 Healthy 30°C &#8226; 86°F 511 1690 158 0 active &#8226; 0 passive 5.9 months
da3 Healthy 32°C &#8226; 89.6°F 510 1685 0 0 active &#8226; 0 passive 5.9 months
da4 Healthy 39°C &#8226; 102.2°F 537 1712 0 0 active &#8226; 0 passive 6.4 months
da5 Healthy 43°C &#8226; 109.4°F 537 1713 0 0 active &#8226; 0 passive 6.4 months
da6 Healthy 46°C &#8226; 114.8°F 445 1620 0 0 active &#8226; 0 passive 5.9 months
da7 Healthy 46°C &#8226; 114.8°F 501 1671 0 0 active &#8226; 0 passive 5.9 months

I am pretty sure the cable error was from ages ago but I thought it was 140 ish

danswartz
User

252 posts

Posted on 15 November 2011 @ 16:04
I believe there is a backup GPT label at the end of the disk. Try zeroing the first and last MB of each disk?
CiPHER
Developer

1199 posts

Posted on 15 November 2011 @ 18:16
What do you mean with "rebooted back to my 9-Current system". Is that ZFSguru 9.0-001 image or a normal FreeBSD system? What ZFS version does it have, what did you do?

You will need to tell us more about how you ended up with a corrupted /different pool. I can't really make heads or tails of your story, other than that something went very wrong.

The GPT label errors mean that the beginning of the disks were overwritten, so the first GPT label is damaged but GPT is redundant and has a backup of the data at the end of the disk as well. This is why you get those messages.

What would you like to do now? Do you want to reformat your disks and start over fresh? Do you want to recover data? Do you just want to know what happened? I would love to help, but i require more data to help you properly.
GamingUnleashed
User

24 posts

Posted on 1 December 2011 @ 01:53edited 02:24 11s
CiPHER wrote: What do you mean with "rebooted back to my 9-Current system". Is that ZFSguru 9.0-001 image or a normal FreeBSD system? What ZFS version does it have, what did you do?

Q: "rebooted back to my 9-Current system"
A: I meant 9-Current the FreeBSD distro
Q: "What ZFS version does it have" same as the 9 ZFS Guru live disk
A: ZFS version SPA: 28, ZPL: 5

I use ZFSguru live / rooton ZFS as a fail safe so that I can access data when I stuff around with FreeBSD and kill it ( data storage is the most important option )
Currently now using 9.0RC2 FreeBSD still trying to source out the speed issue live is wicked fast networking

You will need to tell us more about how you ended up with a corrupted /different pool. I can't really make heads or tails of your story, other than that something went very wrong.

Pretty much booted up ZFSGuru 1.9 live disk so I could use the new 0.1.9
destroyed Tanks repartitioned with the other file system so rooton would work
booted up with rooton ZFSGuru set it all up as a backup bootable system Transfered 4tb of data onto it

then booted into FreeBSD 9-Current setup that I had been using for the last yr
where it annihilated the freshly setup ZFS restoring the old tank1 ( 4 disks)

The GPT label errors mean that the beginning of the disks were overwritten, so the first GPT label is damaged but GPT is redundant and has a backup of the data at the end of the disk as well. This is why you get those messages.

What would you like to do now? Do you want to reformat your disks and start over fresh? Do you want to recover data? Do you just want to know what happened? I would love to help, but i require more data to help you properly.


more or less just want to know why after the old zfs was destroyed that they still remained
if they were indeed destroyed the other old install would not have seeked them out and tried recovering them

I have tried
FreeBSD#
gpart recover da2
da2 recovered
FreeBSD# gpart recover da3
da3 recovered
FreeBSD# gpart recover da4
da4 recovered
FreeBSD# gpart recover da5
da5 recovered


so hopefully this worked



Jhone
User

22 posts

Posted on 19 February 2019 @ 16:38
Project IGI 3 PC Game Full Version Free Download

If your kids get tired of games quickly, rent them instead of buying them. You will save quite a bit of money this way. In addition to local renting options, you can also get a subscription to an online service that lets you get a game or two at a time, depending on what type of subscription that you buy. Then, your kids can simply swap out titles when they get tired of one.
Last Page

Valid XHTML 1.1