Bug#607565: initramfs-tools: initramfs fails to assemble Intel RAID array
2011/2/5, martin f krafft madd...@debian.org: also sprach Roel Brook rainmake...@gmail.com [2011.02.04.0205 +0100]: It complains cannot find /proc/mdstat. If I modprobe the md module from the prompt, and then manually run /scripts/local-top/mdadm, it does assemble the array. I'm just not really sure where to tell local-top to load this module... It should do so automatically. Please uploade your initrd file to a downloadable location (do not send it by mail), or upload it to ftp://ftp.madduck.net/incoming. -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems one should never allow one's mind and one's foot to wander at the same time. -- edward perkins (yes, the librarian) Thank you, and sorry for the late response. After the latest aptitude dist-upgrade, I too got hit with bug #56782, which caused me to investigate the entire boot sequence again. After a couple of changes, update-grub2 and friends do not tell me no such file or directory, but just work as expected without error. This also seems to be causing the RAID array to be assembled correctly on boot (though I think it too got updated during the process). Without the DEVICES line in the mdadm.conf and with a correct and working devices.map, everything works. Thanks for your help. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607565: initramfs-tools: initramfs fails to assemble Intel RAID array
also sprach Roel Brook rainmake...@gmail.com [2011.02.04.0205 +0100]: It complains cannot find /proc/mdstat. If I modprobe the md module from the prompt, and then manually run /scripts/local-top/mdadm, it does assemble the array. I'm just not really sure where to tell local-top to load this module... It should do so automatically. Please uploade your initrd file to a downloadable location (do not send it by mail), or upload it to ftp://ftp.madduck.net/incoming. -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems one should never allow one's mind and one's foot to wander at the same time. -- edward perkins (yes, the librarian) digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#607565: initramfs-tools: initramfs fails to assemble Intel RAID array
On Tue, 2011-02-01 at 14:52 +0100, martin f krafft wrote: also sprach Rain Maker rainmake...@gmail.com [2011.02.01.1438 +0100]: This is the correct fix. Remove the DEVICE line. Will I be able to implement this fix? If so, how? As root, run /usr/share/mdadm/mkconf force-generate sed -i -e 's,^DEVICE,#,' /etc/mdadm/mdadm.conf update-initramfs -u Hmm, in contrast to my previous remark, this does NOT resolve the issue it seems. I can now succesfully start the array from the initrd prompt using mdadm -As, but the /scripts/local-top/mdadm script cannot. It complains cannot find /proc/mdstat. If I modprobe the md module from the prompt, and then manually run /scripts/local-top/mdadm, it does assemble the array. I'm just not really sure where to tell local-top to load this module... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607565: initramfs-tools: initramfs fails to assemble Intel RAID array
2011/1/30, NeilBrown ne...@suse.de: This is the correct fix. Remove the DEVICE line. Will I be able to implement this fix? If so, how? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607565: initramfs-tools: initramfs fails to assemble Intel RAID array
also sprach Rain Maker rainmake...@gmail.com [2011.02.01.1438 +0100]: This is the correct fix. Remove the DEVICE line. Will I be able to implement this fix? If so, how? As root, run /usr/share/mdadm/mkconf force-generate sed -i -e 's,^DEVICE,#,' /etc/mdadm/mdadm.conf update-initramfs -u -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems if god had meant for us to be naked, we would have been born that way. digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#607565: initramfs-tools: initramfs fails to assemble Intel RAID array
On Tue, 2011-02-01 at 14:52 +0100, martin f krafft wrote: also sprach Rain Maker rainmake...@gmail.com [2011.02.01.1438 +0100]: This is the correct fix. Remove the DEVICE line. Will I be able to implement this fix? If so, how? As root, run /usr/share/mdadm/mkconf force-generate sed -i -e 's,^DEVICE,#,' /etc/mdadm/mdadm.conf update-initramfs -u Thanks. Not sure if it is important or not, but update-iniramfs -u gives me an error: root@Medusa:~# update-initramfs -u update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64 mdadm: cannot open /dev/md/BootEnBackup: No such file or directory mdadm: cannot open /dev/md/Data: No such file or directory root@Medusa:~# ls -l /dev/md/ total 0 lrwxrwxrwx 1 root root 8 Feb 1 21:06 BootEnBackup_0 - ../md125 lrwxrwxrwx 1 root root 8 Feb 1 21:06 Data_0 - ../md126 lrwxrwxrwx 1 root root 8 Feb 1 21:06 imsm0 - ../md127 The initram seems to have been generated fine though, and works as expected :) Again, thanks. Roel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607565: initramfs-tools: initramfs fails to assemble Intel RAID array
retitle 607565 remove DEVICE line from generated mdadm.conf severity 607565 wishlist thanks Given Neil's explanation, I think I should change mdadm.conf generation to *not* include the DEVICE line. Thanks, -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems to me, vi is zen. to use vi is to practice zen. every command is a koan. profound to the user, unintelligible to the uninitiated. you discover truth everytime you use it. -- reddy ät lion.austin.ibm.com digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#607565: initramfs-tools: initramfs fails to assemble Intel RAID array
On Tue, 2011-01-25 at 22:22 +0100, martin f krafft wrote: also sprach Rainmaker rainmake...@gmail.com [2010.12.19.2047 +0100]: I did, however find a different workaround. Removing the /etc/mdadm/mdadm.conf and running mdadm -Ss mdadm -As also assembles the arrays correctly. Do you still have that mdadm.conf and could you please provide it with this bug report? Ofcourse. The /etc/mdadm/mdadm.conf orginally looks like this: DEVICE partitions HOMEHOST system ARRAY metadata=imsm UUID=5a17be47:4c36e982:9fd7aa92:6b23c688 ARRAY /dev/md/BootEnBackup container=5a17be47:4c36e982:9fd7aa92:6b23c688 member=0 UUID=9e35:67d59d42:043dbdde:fe757582 ARRAY /dev/md/Data container=5a17be47:4c36e982:9fd7aa92:6b23c688 member=1 UUID=8a981b80:aa2c2f06:e4ec50a5:9045f323 Looks pretty much OK though... A mdadm -Es gives me the same numbers: ARRAY metadata=imsm UUID=5a17be47:4c36e982:9fd7aa92:6b23c688 ARRAY /dev/md/BootEnBackup container=5a17be47:4c36e982:9fd7aa92:6b23c688 member=0 UUID=9e35:67d59d42:043dbdde:fe757582 ARRAY /dev/md/Data container=5a17be47:4c36e982:9fd7aa92:6b23c688 member=1 UUID=8a981b80:aa2c2f06:e4ec50a5:9045f323 I think the DEVICE actually has to be containers. Also, I'm not sure if the gethostname() call implied by system will work in initrd. I'll do some tests and see what works. Sincerely, Roel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607565: initramfs-tools: initramfs fails to assemble Intel RAID array
On Tue, 2011-01-25 at 22:22 +0100, martin f krafft wrote: also sprach Rainmaker rainmake...@gmail.com [2010.12.19.2047 +0100]: I did, however find a different workaround. Removing the /etc/mdadm/mdadm.conf and running mdadm -Ss mdadm -As also assembles the arrays correctly. Do you still have that mdadm.conf and could you please provide it with this bug report? OK. It's definably the DEVICE line which is stopping the arrays from being assembled and started. I changed DEVICE to containers, but it told me None of the devices in the configuration file could be found. Simply changing the DEVICE line to something wrong like foo, causes mdadm to give a warning (Invalid DEVICE line), but it assemble the arrays correctly. Removing the line has the same effect. Changing only the HOMEHOST line does nothing. Setting it to localhost or the hostname of the machine with the DEVICE partitions still in place, does not help. However, using the default configuration does give me a Container imsm assembled. The arrays themselves are not started. Sincerely, Roel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607565: initramfs-tools: initramfs fails to assemble Intel RAID array
On Sun, 30 Jan 2011 12:14:56 +0100 Roel Brook rainmake...@gmail.com wrote: OK. It's definably the DEVICE line which is stopping the arrays from being assembled and started. I changed DEVICE to containers, but it told me None of the devices in the configuration file could be found. Simply changing the DEVICE line to something wrong like foo, causes mdadm to give a warning (Invalid DEVICE line), but it assemble the arrays correctly. Removing the line has the same effect. This is the correct fix. Remove the DEVICE line. The default DEVICE line (which is in effect if no DEVICE line is explicitly given) is DEVICE partitions containers which essentially means feel free to use use anything in an md array. A DEVICE line is only needed if you want to explicitly list some smaller subset of things. There was a time when a DEVICE line was needed, but that is long gone now. Thanks, NeilBrown -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607565: initramfs-tools: initramfs fails to assemble Intel
Hi! I think I was facing the same problem the other day and I hope this is related. The array holding the root partition wouldn't be assembled and stay read-only due to the fact that mdadm couldn't start mdmon, which was not included in the ramdisk. Writing a quick'n'dirty hook for initramfs-tools adding mdmon auto-magically fixed that. --8--- /etc/initramfs-tools/hooks/mdmon: #!/bin/sh . /usr/share/initramfs-tools/hook-functions copy_exec /sbin/mdmon --8--- I can't shutdown the system in a clean way though, it stops at some point (magic SysRq keys still work). I guess it's trying to unmount the root after mdmon has been killed with all the other processes? Best regards, Alex -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607565: initramfs-tools: initramfs fails to assemble Intel
also sprach Alexander Hofbauer a...@derhofbauer.at [2011.01.25.1346 +0100]: The array holding the root partition wouldn't be assembled and stay read-only due to the fact that mdadm couldn't start mdmon, which was not included in the ramdisk. No, it is mounted auto-read-only as long as there are no writes to the device. This is a security measure. I see no reason why mdmon should help with this. -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#607565: initramfs-tools: initramfs fails to assemble Intel
Am Dienstag, den 25.01.2011, 13:53 +0100 schrieb martin f krafft: No, it is mounted auto-read-only as long as there are no writes to the device. This is a security measure. I see no reason why mdmon should help with this. Ext4 was complaining about a read-only device, initramfs did't continue booting and I couldn't enable write access (neither via mdadm --readwrite or /sys/class/block/md126/md/array_state). As I already said, adding mdmon to the initrd did the trick for me. Any ideas about what I might have done wrong? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607565: initramfs-tools: initramfs fails to assemble Intel RAID array
also sprach Rainmaker rainmake...@gmail.com [2010.12.19.2047 +0100]: I did, however find a different workaround. Removing the /etc/mdadm/mdadm.conf and running mdadm -Ss mdadm -As also assembles the arrays correctly. Do you still have that mdadm.conf and could you please provide it with this bug report? -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#607565: initramfs-tools: initramfs fails to assemble Intel RAID array
Package: initramfs-tools Version: 0.98.6 Severity: grave Tags: patch Justification: renders package unusable I just installed Debian (Sid) on my PC and was in for a nasty surprise; the system wouldn't boot after install. I have 2 disks setup in an ICH9R raid set, which devides these 2 disks in 2 arrays; 1 is a RAID0 array, and 1 is a RAID1 array. This is a completely valid configuration for an Intel RAID set. I installed Debian on a LVM setup, using a partition in the RAID0 set as a PV. The /boot partition is also an LV. As I found out, the Intel RAID system works with a container, which contains the arrays. The container was assembled during boot, but the arrays fail to assemble, giving a device or resource busy. The problem is almost exactly the same as seen in this URL: http://www.linux-archive.org/debian-user/454103-how- recreate-dmraid-raid-array-mdadm.html I did, however find a different workaround. Removing the /etc/mdadm/mdadm.conf and running mdadm -Ss mdadm -As also assembles the arrays correctly. For people stumbling into the same problem; here are steps to work around this problem: - Wait for the ramdisk to put you in a (initramfs) shell. - mdadm -Ss - rm /etc/mdadm/mdadm.conf - mdadm -As - lvm vgscan - vgchange -ay Now, mount the boot partition to a directory, e.g. /root - mount /dev/vgMain/lvBoot /root - mkdir /root/temp - cd /root/temp - gunzip ../initrd image | cpio -i - rm etc/mdadm/mdadm.conf - find . | cpio -H newc -o ../initrd.new - cd .. - gzip -9 initrd.new - cd - umount /root - reboot And use the edit option in grub to select /initrd.new.gz as your new initrd image. Some information on my particulair configuration: r...@medusa:~# mdadm -E -s ARRAY metadata=imsm UUID=5a17be47:4c36e982:9fd7aa92:6b23c688 ARRAY /dev/md/BootEnBackup container=5a17be47:4c36e982:9fd7aa92:6b23c688 member=0 UUID=9e35:67d59d42:043dbdde:fe757582 ARRAY /dev/md/Data container=5a17be47:4c36e982:9fd7aa92:6b23c688 member=1 UUID=8a981b80:aa2c2f06:e4ec50a5:9045f323 r...@medusa:~# mdadm -E /dev/sda /dev/sdb /dev/sda: Magic : Intel Raid ISM Cfg Sig. Version : 1.2.00 Orig Family : b68e12bc Family : b68e12bc Generation : 8053 UUID : 5a17be47:4c36e982:9fd7aa92:6b23c688 Checksum : 7f6d2eb4 correct MPB Sectors : 2 Disks : 2 RAID Devices : 2 Disk00 Serial : S13PJDWS255231 State : active Id : Usable Size : 1953520654 (931.51 GiB 1000.20 GB) [BootEnBackup]: UUID : 9e35:67d59d42:043dbdde:fe757582 RAID Level : 1 Members : 2 Slots : [UU] This Slot : 0 Array Size : 66056192 (31.50 GiB 33.82 GB) Per Dev Size : 66056456 (31.50 GiB 33.82 GB) Sector Offset : 0 Num Stripes : 258032 Chunk Size : 64 KiB Reserved : 0 Migrate State : idle Map State : normal Dirty State : clean [Data]: UUID : 8a981b80:aa2c2f06:e4ec50a5:9045f323 RAID Level : 0 Members : 2 Slots : [UU] This Slot : 0 Array Size : 3774918656 (1800.02 GiB 1932.76 GB) Per Dev Size : 1887459592 (900.01 GiB 966.38 GB) Sector Offset : 66060552 Num Stripes : 7372888 Chunk Size : 128 KiB Reserved : 0 Migrate State : idle Map State : normal Dirty State : clean Disk01 Serial : S13PJDWS255348 State : active Id : 0001 Usable Size : 1953520654 (931.51 GiB 1000.20 GB) /dev/sdb: Magic : Intel Raid ISM Cfg Sig. Version : 1.2.00 Orig Family : b68e12bc Family : b68e12bc Generation : 8053 UUID : 5a17be47:4c36e982:9fd7aa92:6b23c688 Checksum : 7f6d2eb4 correct MPB Sectors : 2 Disks : 2 RAID Devices : 2 Disk01 Serial : S13PJDWS255348 State : active Id : 0001 Usable Size : 1953520654 (931.51 GiB 1000.20 GB) [BootEnBackup]: UUID : 9e35:67d59d42:043dbdde:fe757582 RAID Level : 1 Members : 2 Slots : [UU] This Slot : 1 Array Size : 66056192 (31.50 GiB 33.82 GB) Per Dev Size : 66056456 (31.50 GiB 33.82 GB) Sector Offset : 0 Num Stripes : 258032 Chunk Size : 64 KiB Reserved : 0 Migrate State : idle Map State : normal Dirty State : clean [Data]: UUID : 8a981b80:aa2c2f06:e4ec50a5:9045f323 RAID Level : 0 Members : 2 Slots : [UU] This Slot : 1 Array Size : 3774918656 (1800.02 GiB 1932.76 GB) Per Dev Size : 1887459592 (900.01 GiB 966.38 GB) Sector Offset : 66060552 Num Stripes : 7372888 Chunk Size : 128 KiB Reserved : 0 Migrate State : idle Map State : normal Dirty State : clean Disk00 Serial : S13PJDWS255231 State : active Id : Usable Size : 1953520654 (931.51 GiB 1000.20 GB) -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 9.9M Dec 19 19:26
Bug#607565: initramfs-tools: initramfs fails to assemble Intel RAID array
reassign 607565 mdadm stop On Sun, Dec 19, 2010 at 08:47:28PM +0100, Rainmaker wrote: Package: initramfs-tools Version: 0.98.6 Severity: grave Tags: patch Justification: renders package unusable No, not booting on a specific setup is bad, but doesn't render it unusable for the big X nr of boxes, where it does work. Please reread the severity explanations. I just installed Debian (Sid) on my PC and was in for a nasty surprise; the system wouldn't boot after install. I have 2 disks setup in an ICH9R raid set, which devides these 2 disks in 2 arrays; 1 is a RAID0 array, and 1 is a RAID1 array. This is a completely valid configuration for an Intel RAID set. I installed Debian on a LVM setup, using a partition in the RAID0 set as a PV. The /boot partition is also an LV. As I found out, the Intel RAID system works with a container, which contains the arrays. The container was assembled during boot, but the arrays fail to assemble, giving a device or resource busy. The problem is almost exactly the same as seen in this URL: http://www.linux-archive.org/debian-user/454103-how- recreate-dmraid-raid-array-mdadm.html I did, however find a different workaround. Removing the /etc/mdadm/mdadm.conf and running mdadm -Ss mdadm -As also assembles the arrays correctly. For people stumbling into the same problem; here are steps to work around this problem: - Wait for the ramdisk to put you in a (initramfs) shell. - mdadm -Ss - rm /etc/mdadm/mdadm.conf - mdadm -As - lvm vgscan - vgchange -ay Now, mount the boot partition to a directory, e.g. /root - mount /dev/vgMain/lvBoot /root - mkdir /root/temp - cd /root/temp - gunzip ../initrd image | cpio -i - rm etc/mdadm/mdadm.conf - find . | cpio -H newc -o ../initrd.new - cd .. - gzip -9 initrd.new - cd - umount /root - reboot And use the edit option in grub to select /initrd.new.gz as your new initrd image. Some information on my particulair configuration: r...@medusa:~# mdadm -E -s ARRAY metadata=imsm UUID=5a17be47:4c36e982:9fd7aa92:6b23c688 ARRAY /dev/md/BootEnBackup container=5a17be47:4c36e982:9fd7aa92:6b23c688 member=0 UUID=9e35:67d59d42:043dbdde:fe757582 ARRAY /dev/md/Data container=5a17be47:4c36e982:9fd7aa92:6b23c688 member=1 UUID=8a981b80:aa2c2f06:e4ec50a5:9045f323 r...@medusa:~# mdadm -E /dev/sda /dev/sdb /dev/sda: Magic : Intel Raid ISM Cfg Sig. Version : 1.2.00 Orig Family : b68e12bc Family : b68e12bc Generation : 8053 UUID : 5a17be47:4c36e982:9fd7aa92:6b23c688 Checksum : 7f6d2eb4 correct MPB Sectors : 2 Disks : 2 RAID Devices : 2 Disk00 Serial : S13PJDWS255231 State : active Id : Usable Size : 1953520654 (931.51 GiB 1000.20 GB) [BootEnBackup]: UUID : 9e35:67d59d42:043dbdde:fe757582 RAID Level : 1 Members : 2 Slots : [UU] This Slot : 0 Array Size : 66056192 (31.50 GiB 33.82 GB) Per Dev Size : 66056456 (31.50 GiB 33.82 GB) Sector Offset : 0 Num Stripes : 258032 Chunk Size : 64 KiB Reserved : 0 Migrate State : idle Map State : normal Dirty State : clean [Data]: UUID : 8a981b80:aa2c2f06:e4ec50a5:9045f323 RAID Level : 0 Members : 2 Slots : [UU] This Slot : 0 Array Size : 3774918656 (1800.02 GiB 1932.76 GB) Per Dev Size : 1887459592 (900.01 GiB 966.38 GB) Sector Offset : 66060552 Num Stripes : 7372888 Chunk Size : 128 KiB Reserved : 0 Migrate State : idle Map State : normal Dirty State : clean Disk01 Serial : S13PJDWS255348 State : active Id : 0001 Usable Size : 1953520654 (931.51 GiB 1000.20 GB) /dev/sdb: Magic : Intel Raid ISM Cfg Sig. Version : 1.2.00 Orig Family : b68e12bc Family : b68e12bc Generation : 8053 UUID : 5a17be47:4c36e982:9fd7aa92:6b23c688 Checksum : 7f6d2eb4 correct MPB Sectors : 2 Disks : 2 RAID Devices : 2 Disk01 Serial : S13PJDWS255348 State : active Id : 0001 Usable Size : 1953520654 (931.51 GiB 1000.20 GB) [BootEnBackup]: UUID : 9e35:67d59d42:043dbdde:fe757582 RAID Level : 1 Members : 2 Slots : [UU] This Slot : 1 Array Size : 66056192 (31.50 GiB 33.82 GB) Per Dev Size : 66056456 (31.50 GiB 33.82 GB) Sector Offset : 0 Num Stripes : 258032 Chunk Size : 64 KiB Reserved : 0 Migrate State : idle Map State : normal Dirty State : clean [Data]: UUID : 8a981b80:aa2c2f06:e4ec50a5:9045f323 RAID Level : 0 Members : 2 Slots : [UU] This Slot : 1 Array Size : 3774918656 (1800.02 GiB 1932.76 GB) Per Dev Size : 1887459592 (900.01 GiB 966.38 GB) Sector Offset :
