ilciumbia

Members
  • Content Count

    28
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ilciumbia

  • Rank
    Junior Member
  1. Hi all, I have just purchased a 4TB HDD which I would like to use purely for backup purposes. I have an XPEnology box with DSM5.2.5644.5 and a 3 volumes: RAID1, RAID5 and no RAID (actually they are all SHR, I used standard nomenclature to explain the redundancy). My question is: should I install the new disk inside the XPEnology box, create a new volume (volume4) and use this as the backup destination or should I insert the HDD into a USB external box and backup everything there? My thoughts: Internal: no space on desk, as fast as it can get, protected from power surges and sho
  2. Hi, thanks for the reply! I sounds very interesting, it has to be seen if then I can access the mounted drive from any of the available backup tools... I think it is worth a try, I will keep you informed!
  3. Hi all, I realise my need for a backup disk for all my data, so I've been wondering lately: if I connect an internal hard drive to a SATA port (so not USB), is there a way to convince DSM not to initialize it as part of an array but keep it standalone and access it as if it were an external USB disk? This would have two reasons: 1- Since it would only serve a backup purpose, I would like to format it to NTFS, it would make things easier should I ever need to recover data; 2- since I often have Download Station running, disks never go to sleep; if one of the disks is not part of an arr
  4. Same reply to me, too... Sent from my Nexus 10
  5. Hi Trantor, My board, AsRock N3150M, uses the NCT6792; will it be compatible with the nct6775 drivers?... Thanks for your invaluable work!
  6. Er... it does not... ??? root@DiskStation:~>parted /dev/sda align opt 1 1 aligned root@DiskStation:~>parted /dev/sda align opt 2 2 not aligned root@DiskStation:~>parted /dev/sda align opt 5 5 not aligned root@DiskStation:~>parted /dev/sdc align opt 1 1 aligned root@DiskStation:~>parted /dev/sdc align opt 2 2 not aligned root@DiskStation:~>parted /dev/sdc align opt 3 3 aligned Ouch... I am lost again... hdparm -I /dev/sda reports: Logical Sector size: 512 bytes Physical Sector size: 4096 b
  7. Wow, how right you were! I did as you suggested: Model: HGST HDN724040ALE640 (scsi) Disk /dev/hda: 4000787030016B Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1048576B 2551054335B 2550005760B ext4 raid 2 2551054336B 4698537983B 2147483648B linux-swap(v1) raid 5 4840079360B 4000681082879B 3995841003520B raid So in fact partitions ARE 4k aligned! 1048576/4096 = 256 2551054336/4096
  8. Hi all, thanks for your replies. Absolutely agree. The datasheet for the HGST https://www.hgst.com/products/hard-drives/nas-desktop-drive-kit drives in question are silent on the topic though. Exactly. WD EARS are indeed Advanced Format, while HGST says nothing about it, but, according to Linux, it does have 4k sectors. I must gently disagree. For all operating systems and disk arrangements, sector size matters. For single disks, the minimum file system allocation unit must be a multiple of the sector size. Otherwise, misaligned allocation units will cause two sectors to
  9. Can you please publish here what you wrote them?
  10. Hi all, I have recently set up my system, starting with a pair of 4TB HSGT Deskstar NAS and then adding 1 TB WD green disks. Now I wonder if DSM is capable of correctly recognizing and aligning 4k-sector disks. I don't know if the HGST are in fact 4k-sector disks, but if I run: cat /sys/class/block/sda/queue/physical_block_size I get: 4096 However, if I run parted on /dev/sda and I press p I get: Model: HGST HDN724040ALE640 (scsi) Disk /dev/sda: 4001GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size Fil
  11. Did You solve it? Inviato dal mio Nexus 10 utilizzando Tapatalk
  12. Have You tried running smart checks on the drives? Sometimes fake errors get cleared... Inviato dal mio Nexus 10 utilizzando Tapatalk
  13. Have You tried running smart checks on the drives? Sometimes fake errors get cleared... Inviato dal mio Nexus 10 utilizzando Tapatalk