Zobrazit příspěvky
1
Server / Obnovení svazku QNAP LUN na Linuxu
« kdy: 25. 03. 2021, 15:15:52 »
Dobry den,
V predchadzajucej teme sme riesili rozpadnuty raid ktory sa nastastie podarilo opravit a aj sa dostat k pozadovanym suborom. Jedna sa o 2 sobory qnap iscsi. Qnap zial umrel uplne a tak by som to rad rozbehnut na linuxe kde mam aj image povodnych diskov.
Config qnapu je nasledovny.
pravdupovediac neviem co je to za konfig. Vyznam sa v targetcli ale toto ho teda ani nepripomina.
skusil som zostavit ten lun v linuxe a precitat ale zatial bez znamok uspechu.
este som zabudol
Vidim dve moznosti. - prist na to co qnap pouziva na iscsi target a skusit to tak postavit na nohy alebo tie dva disky nejako spojit a s offsetom mountnut avsak zatial moje pokusy zlyhali.
Nemate pani prosim Vas nejaky napad?
vdaka
V predchadzajucej teme sme riesili rozpadnuty raid ktory sa nastastie podarilo opravit a aj sa dostat k pozadovanym suborom. Jedna sa o 2 sobory qnap iscsi. Qnap zial umrel uplne a tak by som to rad rozbehnut na linuxe kde mam aj image povodnych diskov.
Config qnapu je nasledovny.
Kód: [Vybrat]
[iSCSIPortal]
targetIQNPrefix=iqn.2004-04.com.qnap:ts-469u-rp:iscsi.
bServiceEnable=TRUE
servicePort=3260
initiatorBitmap00=00000001
targetBitmap00=00000001
LUNBitmap00=00000001
bSupportMultiACL=1
log=TRUE
logFlags=1
[init0Info]
initiatorIndex=0
initiatorIQN=iqn.2004-04.com.qnap:all:iscsi.default.ffffff
initiatorAlias=Default Policy
initiatorTargetBitmap00=00000001
initiatorLUNBitmap00=00000001
[InitiatorKey]
iqn.2004-04.com.qnap:all:iscsi.default.ffffff=0
[TargetKey]
target_iqn.2004-04.com.qnap:ts-469u-rp:iscsi.company.d48e82=0
[LUNKey]
LUN_storage=0
[target0Info]
targetIndex=0
targetName=server
targetIQN=iqn.2004-04.com.qnap:ts-469u-rp:iscsi.company.d48e82
targetAlias=storageqnap01
bTargetDataDigest=FALSE
bTargetHeaderDigest=FALSE
targetStatus=0
targetInitBitmap00=00000001
targetLUNNumBitmap00=00000001
targetLUNBitmap00=00000001
bTargetClusterEnable=TRUE
[target0Init0Info]
targetIndex=0
initiatorIndex=0
bCHAPEnable=FALSE
bMutualCHAPEnable=FALSE
CHAPUserName=
CHAPPasswd=
mutualCHAPUserName=
mutualCHAPPasswd=
[LUN0Info]
LUNIndex=0
LUNName=storage
LUNPath=/share/MD0_DATA
LUNMetaPath=/share/MD0_DATA/.@iscsi.img/iSCSI-storage-517a7d86:002
LUNCapacity=1885102
LUNFileCount=2
LUNThinAllocate=FALSE
LUNStatus=2
LUNBackupStatus=0
LUNBackupPid=-1
LUNBackupJob=-1
LUNInitBitmap00=00000001
LUNAttachedTarget=-1
LUNEnable=FALSE
FBNumber=0
LUNSerialNum=a87ad731-252c-4e86-8b69-dc0f959700b4
bRemoving=FALSE
LUNTargetBitmap00=00000001
LUNAllocated=1976678060032
WCEnable=0
FUAEnable=1
[LUN0Init0Info]
LUNIndex=0
initiatorIndex=0
initiatorLUNNumber=-1
accessMode=1
[LUN0Target0Info]
LUNIndex=0
targetIndex=0
LUNNumber=0
LUNEnable=TRUE
pravdupovediac neviem co je to za konfig. Vyznam sa v targetcli ale toto ho teda ani nepripomina.
skusil som zostavit ten lun v linuxe a precitat ale zatial bez znamok uspechu.
Kód: [Vybrat]
-rw------- 1 root root 1.0T Mar 25 11:50 iSCSI-Networker-517a7d86.000
-rw------- 1 root root 817G Apr 26 2013 iSCSI-Networker-517a7d86.001
fdisk -l iSCSI-Networker-517a7d86.000
You must set cylinders.
You can do this from the extra functions menu.
Disk iSCSI-Networker-517a7d86.000: 0 MB, 0 bytes
197 heads, 8 sectors/track, 0 cylinders
Units = cylinders of 1576 * 512 = 806912 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xffa599a5
Device Boot Start End Blocks Id System
iSCSI-Networker-517a7d86.000p1 2 2449676 1930343424 83 Linux
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(0, 32, 33) logical=(1, 59, 1)
Partition 1 has different physical/logical endings:
phys=(700, 196, 8) logical=(2449675, 136, 8)
fdisk -l iSCSI-Networker-517a7d86.001
Disk iSCSI-Networker-517a7d86.001: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x5d0504f9
sgdisk -p iSCSI-Networker-517a7d86.000
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************
Warning! Secondary partition table overlaps the last partition by
1713205281 blocks!
You will need to delete this partition or resize it in another utility.
Disk iSCSI-Networker-517a7d86.000: 2147483648 sectors, 1024.0 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 32BCB0C7-6D89-4F31-9924-D648D9F89DEE
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 2147483614
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 3860688895 1.8 TiB 8300 Linux filesystem
sgdisk -p iSCSI-Networker-517a7d86.001
Creating new GPT entries.
Disk iSCSI-Networker-517a7d86.001: 1713205248 sectors, 816.9 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 245D6FCA-020B-4F3C-A11C-D6D858804664
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1713205214
Partitions will be aligned on 2048-sector boundaries
Total free space is 1713205181 sectors (816.9 GiB)
Number Start (sector) End (sector) Size Code Name
este som zabudol
Kód: [Vybrat]
file iSCSI-Networker-517a7d86.000
iSCSI-Networker-517a7d86.000: x86 boot sector; partition 1: ID=0x83, starthead 32, startsector 2048, 3860686848 sectors, extended partition table (last)\011, code offset 0x0
[root@recovery-dom .@iscsi.img]# file iSCSI-Networker-517a7d86.001
iSCSI-Networker-517a7d86.001: data
[root@recovery-dom .@iscsi.img]#
Vidim dve moznosti. - prist na to co qnap pouziva na iscsi target a skusit to tak postavit na nohy alebo tie dva disky nejako spojit a s offsetom mountnut avsak zatial moje pokusy zlyhali.
Nemate pani prosim Vas nejaky napad?
vdaka
