please help raid0 no files

C

chalan

Member
Mar 16, 2015
119
3
16
after power failure i got problem with one of my pool...

Code: 
root@pve-klenova:~# zpool status -v
  pool: public
 state: ONLINE
status: One or more devices are faulted in response to IO failures.
action: Make sure the affected devices are connected, then run 'zpool clear'.
   see: http://zfsonlinux.org/msg/ZFS-8000-HC
  scan: scrub repaired 0 in 2h3m with 0 errors on Sun Nov 12 02:27:18 2017
config:

   NAME                        STATE     READ WRITE CKSUM
   public                      ONLINE       9    15     0
     ata-MB0500EBZQA_Z1M0EHYH  ONLINE       3    32     0
     ata-MB0500EBZQA_Z1M0EGEJ  ONLINE       0     0     0

errors: List of errors unavailable (insufficient privileges)

  pool: rpool
 state: ONLINE
  scan: scrub repaired 0 in 16h41m with 0 errors on Sun Nov 12 17:05:48 2017
config:

   NAME                                                STATE     READ WRITE CKSUM
   rpool                                               ONLINE       0     0     0
     mirror-0                                          ONLINE       0     0     0
       ata-WDC_WD10EFRX-68PJCN0_WD-WCC4J2021886-part2  ONLINE       0     0     0
       ata-WDC_WD10EFRX-68JCSN0_WD-WMC1U6546808-part2  ONLINE       0     0     0
     mirror-1                                          ONLINE       0     0     0
       ata-WDC_WD10EFRX-68FYTN0_WD-WCC4J2AK75T9        ONLINE       0     0     0
       ata-WDC_WD10EFRX-68FYTN0_WD-WCC4J1JE0SFR        ONLINE       0     0     0

errors: No known data errors

Code: 
Disk /dev/sda: 931,5 GiB, 1000204886016 bytes, 1953525168 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: DA4DF415-1828-4A7E-B5E9-D23A72B64DB5

Device          Start        End    Sectors   Size Type
/dev/sda1          34       2047       2014  1007K BIOS boot
/dev/sda2        2048 1953508749 1953506702 931,5G Solaris /usr & Apple ZFS
/dev/sda9  1953508750 1953525134      16385     8M Solaris reserved 1

Partition 1 does not start on physical sector boundary.
Partition 9 does not start on physical sector boundary.


Disk /dev/sdb: 931,5 GiB, 1000204886016 bytes, 1953525168 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: 7CB80B83-8CDE-4605-9FA8-69E84A54E5ED

Device          Start        End    Sectors   Size Type
/dev/sdb1          34       2047       2014  1007K BIOS boot
/dev/sdb2        2048 1953508749 1953506702 931,5G Solaris /usr & Apple ZFS
/dev/sdb9  1953508750 1953525134      16385     8M Solaris reserved 1

Partition 1 does not start on physical sector boundary.
Partition 9 does not start on physical sector boundary.


Disk /dev/sdd: 465,8 GiB, 500107862016 bytes, 976773168 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: gpt
Disk identifier: DC8504ED-AECF-6A42-9104-C0B9B7EA3A85

Device         Start       End   Sectors   Size Type
/dev/sdd1       2048 976756735 976754688 465,8G Solaris /usr & Apple ZFS
/dev/sdd9  976756736 976773119     16384     8M Solaris reserved 1


Disk /dev/sde: 931,5 GiB, 1000204886016 bytes, 1953525168 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: 40E61999-2F35-FD42-BAE0-A423E7A0F896

Device          Start        End    Sectors   Size Type
/dev/sde1        2048 1953507327 1953505280 931,5G Solaris /usr & Apple ZFS
/dev/sde9  1953507328 1953523711      16384     8M Solaris reserved 1


Disk /dev/sdf: 931,5 GiB, 1000204886016 bytes, 1953525168 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: 0002CC45-C2D6-524B-9EC7-9E4FE9659547

Device          Start        End    Sectors   Size Type
/dev/sdf1        2048 1953507327 1953505280 931,5G Solaris /usr & Apple ZFS
/dev/sdf9  1953507328 1953523711      16384     8M Solaris reserved 1


Disk /dev/sdg: 698,7 GiB, 750156374016 bytes, 1465149168 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: 0x000f2830

Device     Boot     Start        End    Sectors   Size Id Type
/dev/sdg1  *            1  205123583  205123583  97,8G 83 Linux
/dev/sdg2       205123584 1465149167 1260025584 600,8G 83 Linux


Disk /dev/zd0: 1 TiB, 1099511627776 bytes, 2147483648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 8192 bytes
I/O size (minimum/optimal): 8192 bytes / 8192 bytes
Disklabel type: dos
Disk identifier: 0x19f23cf4

Device     Boot Start        End    Sectors  Size Id Type
/dev/zd0p1       2048 2147483647 2147481600 1024G 83 Linux


Disk /dev/zd16: 100 GiB, 107374182400 bytes, 209715200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 8192 bytes
I/O size (minimum/optimal): 8192 bytes / 8192 bytes
Disklabel type: dos
Disk identifier: 0x0006fc55

Device      Boot Start       End   Sectors  Size Id Type
/dev/zd16p1       2048 209713151 209711104  100G 83 Linux


Disk /dev/zd32: 100 GiB, 107374182400 bytes, 209715200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 8192 bytes
I/O size (minimum/optimal): 8192 bytes / 8192 bytes
Disklabel type: dos
Disk identifier: 0x294acf2e

Device      Boot Start       End   Sectors  Size Id Type
/dev/zd32p1       2048 209715199 209713152  100G 83 Linux


Disk /dev/zd48: 10 GiB, 10737418240 bytes, 20971520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 8192 bytes
I/O size (minimum/optimal): 8192 bytes / 8192 bytes
Disklabel type: dos
Disk identifier: 0x644c7a42

Device      Boot    Start      End  Sectors  Size Id Type
/dev/zd48p1 *        2048 19922943 19920896  9,5G 83 Linux
/dev/zd48p2      19924990 20969471  1044482  510M  5 Extended
/dev/zd48p5      19924992 20969471  1044480  510M 82 Linux swap / Solaris

Partition 2 does not start on physical sector boundary.


Disk /dev/zd64: 8 GiB, 8589934592 bytes, 16777216 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/zd80: 871 GiB, 935229128704 bytes, 1826619392 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 8192 bytes
I/O size (minimum/optimal): 8192 bytes / 8192 bytes
Disklabel type: dos
Disk identifier: 0xe457ab58

Device      Boot Start        End    Sectors  Size Id Type
/dev/zd80p1       2048 1826619391 1826617344  871G 83 Linux

isnt there any chance to rebuild that pool and rescue lost fieles?
 
chalan said:
isnt there any chance to rebuild that pool and rescue lost fieles?
Click to expand...
Hi,
with an raid-0?? Good joke!

No, the data is gone... this is the reason why nobody use raid-0 for data which is important.

The only thing, where I use raid-0 is as spool-disk for backup - if the raid-0 fails, the backup must run again and the data are for a few minutes/hour on the disks only.

Udo
 
ok this means that one of the disk is BAD, HW is gone em i right? what will happen if i have raid0 and new 100% working disks and a power failure will occure? will i also lost my data?
 
chalan said:
ok this means that one of the disk is BAD, HW is gone em i right?
Click to expand...
Perhaps you can try to disconnect the defect hdd, and try to copy them with ddrescue (or similliar - better safecopy) on an new disk. Sometimes it's possible, if you cool the hdd or use another position (up side down). If you can copy all (or most) data to the new hdd, you can try to bring up your raid-0 with the new hdd.
what will happen if i have raid0 and new 100% working disks and a power failure will occure? will i also lost my data?
Click to expand...
that should not damage anything, because zfs is an cow-filesystem.

Udo
 
Last edited:
i need to buy two new hdds as replace. i would mirror them. can somebody please advise my fast and reliable disks? 2-4TB... normaly i would buy WD RED drives, but i have thous disks in my servers and the performance is poor, i dont know if its disk problem but both servers have the same problem... thank you...
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back