LINUX LITE 7.2 FINAL RELEASED - SEE RELEASE ANNOUNCEMENTS SECTION FOR DETAILS


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Gparted not working: "Invalid partition table on /dev/sda --wrong signature 0"
#1
I have an LL3.4/Win7 dual-boot setup on a single 250GB SSD, for a Dell Latitude D630.
However, I needed a bigger drive for more data files and also a Windows recovery partition, the latter apparently needing a significant about of disk space.

So, I cloned the above set-up onto a 500GB SSD using the 'dd' command:
Code:
sudo dd if=/dev/sdd of=/dev/sdc

Then, I replaced the laptop's 250GB drive with the 500GB one, and was able to boot into either Win7 or LL3.4 on the larger drive, without any apparent problem. So far, so good  Smile

Next, I tried to open gparted in order to resize some of the partitions on the new larger drive. However, gparted remained stuck indefinitely, the blue progress bar just bobbing repeatedly to the left and right, without anything appearing within the gparted window.  A notification popped up with the following message:
Code:
Libparted Error
Invalid partition table on /dev/sda --wrong signature 0.

Because of this, I'm unable to resize the new disk's partitions  Sad
Any help much appreciated ...

Mike
64bit OS (32-bit on Samsung[i] netbook) installed in [i]Legacy mode on MBR-formatted SSDs (except pi which uses a micro SDHC card):
2017 - Raspberry pi 3B (4cores) ~ [email protected] - LibreElec, used for upgrading our Samsung TV (excellent for the task)  
2012 - Lenovo G580 2689 (2cores; 4threads] ~ [email protected] - LL3.8/Win8.1 dual-boot (LL working smoothly)
2011 - Samsung NP-N145 Plus (1core; 2threads) ~ Intel Atom [email protected] - LL 3.8 32-bit (64-bit too 'laggy')
2008 - Asus X71Q (2cores) ~ Intel [email protected] - LL4.6/Win8.1 dual-boot, LL works fine with kernel 4.15
2007 - Dell Latitude D630 (2cores) ~ Intel [email protected] - LL4.6, works well with kernel 4.4; 4.15 doesn't work
Reply
#2
Solved it  Smile

First, I can get into gparted by pressing the ignore button on the Libparted Error notification - silly me!
Within gparted, I then discovered the source of the Libparted Error: when I cloned the dual-boot system from the smaller to the larger drive, the extended partition remained at its former size.  So, I therefore extended this to the rest of the drive, which includes the new unallocated space on the larger drive.

Gparted now opens as normal, without any signature error or any other issues - problem solved - oh happy days ...
64bit OS (32-bit on Samsung[i] netbook) installed in [i]Legacy mode on MBR-formatted SSDs (except pi which uses a micro SDHC card):
2017 - Raspberry pi 3B (4cores) ~ [email protected] - LibreElec, used for upgrading our Samsung TV (excellent for the task)  
2012 - Lenovo G580 2689 (2cores; 4threads] ~ [email protected] - LL3.8/Win8.1 dual-boot (LL working smoothly)
2011 - Samsung NP-N145 Plus (1core; 2threads) ~ Intel Atom [email protected] - LL 3.8 32-bit (64-bit too 'laggy')
2008 - Asus X71Q (2cores) ~ Intel [email protected] - LL4.6/Win8.1 dual-boot, LL works fine with kernel 4.15
2007 - Dell Latitude D630 (2cores) ~ Intel [email protected] - LL4.6, works well with kernel 4.4; 4.15 doesn't work
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)