npierce, Karl Godt,
Thanks very much, fixes applied.
Blog:
http://bkhome.org/blog2/?viewDetailed=00265
3 TB (GPT), HD problem, impossible to identify a partition
npierce, I had no solution that time as the output formatted looks like
and all the other "Partition" lines except for the "Partition 1:" line don't start with ^Partition .
But the loop seems to eliminate the preceding spaces, does not even squeezes them to one space .
Learned something new
Also the grep -E ..? option is something new to me. Was wondering why such " -e, --regexp=PATTERN use PATTERN for matching" did not work for me many times . Now I am able to understand
much better .
Code: Select all
- - - - disktype /dev/sda
--- /dev/sda
Block device, size 2.729 TiB (3000592982016 bytes)
DOS/MBR partition map
Partition 1: 2.000 TiB (2199023255040 bytes, 4294967295 sectors from 1)
Type 0xEE (EFI GPT protective)
GPT partition map, 128 entries
Disk size 2.729 TiB (3000592982016 bytes, 5860533168 sectors)
Disk GUID B50762CF-A490-D244-B71B-4F3B7566A89B
Partition 1: 2.681 TiB (2948162650112 bytes, 5758130176 sectors from 2048)
Type Basic Data (GUID A2A0D0EB-E5B9-3344-87C0-68B6B72699C7)
Partition Name ""
Partition GUID D1F83576-69C7-D34D-8C15-D32626745ED6
Ext4 file system
Volume name "SAYAN_DISK"
UUID 652BDBEA-CB51-492F-B4DD-0EA0517071D6 (DCE, v4)
Last mounted at "/home"
Volume size 2.681 TiB (2948162650112 bytes, 719766272 blocks of 4 KiB)
But the loop seems to eliminate the preceding spaces, does not even squeezes them to one space .
Learned something new
Also the grep -E ..? option is something new to me. Was wondering why such " -e, --regexp=PATTERN use PATTERN for matching" did not work for me many times . Now I am able to understand
http://www.gnu.org/software/grep/manual ... s-ExtendedIn basic regular expressions the meta-characters ‘?’, ‘+’, ‘{’, ‘|’, ‘(’, and ‘)’ lose their special meaning; instead use the backslashed versions ‘\?’, ‘\+’, ‘\{’, ‘\|’, ‘\(’, and ‘\)’.
much better .