Re: cloned sd card is not booting

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2014-08-06 at 08:16 -0400, Robert Moskowitz wrote:
> On 08/06/2014 05:26 AM, Louis Lagendijk wrote:
> > On Tue, 2014-08-05 at 23:44 -0400, Robert Moskowitz wrote:
> >
> >>            Starting File System Check on
> >> /dev/disk/by-uuid/1dc8...f055a32473b9...
> >> [   13.911063] systemd-fsck[368]: _/: The filesystem size (according to
> >> the superblock) is 3587707 blocks
> >> [  OK  ] Started dracut pre-mount hook.
> >> [   13.919598] systemd-fsck[368]: The physical size of the device is
> >> 3548795 blocks
> >> [   13.937109] systemd-fsck[368]: Either the superblock or the partition
> >> table is likely to be corrupt!
> >> [   13.944962] systemd-fsck[368]: _/: UNEXPECTED INCONSISTENCY; RUN fsck
> >> MANUALLY.
> > are the cards exactly the same size? It looks as if the card you copiued
> > to is smaller than the one you copied from... What does fdisk	-l report
> > for disk size for the "old" and "new" cards?
> 
> Well, yes they are different:
> 
> # fdisk -l /dev/sdb
> 
> Disk /dev/sdb: 14.7 GiB, 15720251392 bytes, 30703616 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: dos
> Disk identifier: 0xd42361d8
> 
> # fdisk -l /dev/sdc
> 
> Disk /dev/sdc: 14.5 GiB, 15560867840 bytes, 30392320 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: dos
> Disk identifier: 0xed0dd3b4
> 
> And nothing I can do about that.  Seems that the size is based on 
> whatever fits based on quality of the chip.
> 
> 
Do a resizefs <device/partition>  new-size 
to something smaller than what will fit on the new stick. After copying
the content over it should boot ok and then 
correct the partiton table (delete the partition and create it again,
fdisk should automatically set the size IIRC), then
do a resize2fs <device/partiton> 
without size ro enlarge the partion to it's max size.
The only problem: for the shrinking the partion must be unmounted.

Louis

-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org




[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux