![]() ![]() I still have the disk and apparently all the files are still there but "df -k" output for free space is all wrong. I started getting messages about "Free blocks count wrong for group " and at first thought it might be ok but I did not let e2fsck complete (ctrl-c) after about > 2000 of these messages. I did "e2fsck -n /dev/sdb1" to get the superblocks and then tried "e2fsck -b /dev/sdb1". I took this as an indication that something had been written to the partition. ![]() I saw the "created a DOS disklabel." msg and panicked. Fdisk should bail out if it can't handle this situation, right? I don't know if this was the problem though. I did, mistakenly, use fdisk because it's a HUGE disk, I should have used gdisk since it's a GPT partition. I did not use any other tools on this disk. dev/sdc1: device contains a valid 'ext4' signature, it's strongly recommended to wipe the device by command wipefs(8) if this setup is unexpected to avoid possible collisions.Ĭreated a new DOS disklabel with disk identifier 0xef3c6559.Īnyway, it's strange and really unexpected that fsck.ext4 segfauls (CC: e2fsprogs maintainer) * extN filesystem does not use the begin of the device (where is DOS label), you have to use logical partitions to write to area where is extNĠ0000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |.| * "Created a new DOS disklabel." means in-memory, it does not write anything to the device * fdisk does not write anything to device if you not type 'w' Hi George, I understand the pain and frustration, but are you really sure that you did not touch the partition by some another tools? > quit from fdisk but it WROTE TO THIS PARTITION damaging/destroying a 5.5 TB > I mistakenly entered "fdisk /dev/sdb1" and got error messages and tried to ******? yesįree blocks count wrong for group #1 (31743, counted=0).įree blocks count wrong for group #2 (32768, counted=0).įree blocks count wrong for group #3 (31743, counted=0). Use GUID partition table format (GPT).Ĭreated a new DOS disklabel with disk identifier 0x7c9f38a4. DOS partition table format can not be used on drives for volumes larger than 2199023255040 bytes for 512-byte sectors. dev/sdb1: device contains a valid 'ext4' signature, it's strongly recommended to wipe the device by command wipefs(8) if this setup is unexpected to avoid possible collisions.ĭevice does not contain a recognized partition table. I did NOT expect fdisk to write to this partition as it has in the past.Ĭhanges will remain in memory only, until you decide to write them.īe careful before using the write command. fsck with -n produces unexpected behavior. The filesystem in /dev/sdb1 is destroyed now. Version-Release number of selected component (if applicable):Īre you kidding? I won't be doing this again soon.Ģ.*** FDISK TOOK OVER AND WROTE A DOS disk label on this filesystem. I mistakenly entered "fdisk /dev/sdb1" and got error messages and tried to quit from fdisk but it WROTE TO THIS PARTITION damaging/destroying a 5.5 TB filesystem! ![]()
0 Comments
Leave a Reply. |