Hi all, I have 8G -CF cards that I have been putting linux on. Everything was working fine till yesterday when I got a new batch of CF cards. The size has changed. The original CF card was 7637M (255 heads/63 sectors/928 cylinders) The new CF card is 8019M (255 heads/63 sectors/974 cylinders) I would have thought putting the smaller image file onto the larger CF card would be ok. However its not. centos boots but there are journal issues and everything is mounted read-only. Any ideas why this doesnt work or how I can keep my smaller image and "succecssfully" put it on the larger CF card? I simply do "dd if=cf.img of=/dev/sde" to copy the images to CF. Thanks, Jerry
At Tue, 30 Nov 2010 09:46:03 -0500 CentOS mailing list <centos at centos.org> wrote:> > Hi all, > > I have 8G -CF cards that I have been putting linux on. > Everything was working fine till yesterday when I got a new batch of CF > cards. > > The size has changed. The original CF card was 7637M (255 heads/63 > sectors/928 cylinders) > The new CF card is 8019M (255 heads/63 sectors/974 cylinders) > > I would have thought putting the smaller image file onto the larger CF > card would be ok. > However its not. centos boots but there are journal issues and > everything is mounted read-only. > > Any ideas why this doesnt work or how I can keep my smaller image and > "succecssfully" put it > on the larger CF card? > > I simply do "dd if=cf.img of=/dev/sde" to copy the images to CF.ARG!!! Don't do this! You really, really don't want to dd a raw disk image (including mbr/partition table) to a *different* geometry disk -- it does not matter what the 'disk' tech is (IDE. SCSI, SATA, SSD, etc.). Partition the new disk with fdisk (or something like that), then use mkfs to make the file systems than use dump/restore to move the file systems. Finally use grub-install (or lilo) to install the boot loader.> > Thanks, > > Jerry > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > >-- Robert Heller -- 978-544-6933 / heller at deepsoft.com Deepwoods Software -- http://www.deepsoft.com/ () ascii ribbon campaign -- against html e-mail /\ www.asciiribbon.org -- against proprietary attachments
On Tuesday, November 30, 2010 09:46:03 am Jerry Geis wrote:> However its not. centos boots but there are journal issues and > everything is mounted read-only.Can you get log snippets showing why the journal had issues?> Any ideas why this doesnt work or how I can keep my smaller image and > "succecssfully" put it > on the larger CF card? > > I simply do "dd if=cf.img of=/dev/sde" to copy the images to CF.I've done this before with regular disk drives (going from a 200G to a 500G SATA in this laptop I'm using right now; I used dd to copy, then I booted just fine. I then rebooted with a liveCD and did the partition moving/enlargement that I needed to do. Geometry issues used to be bears, but in the days of LBA (and with SCSI drives) there really isn't a 'geometry' to speak of at the OS or partition level. The 'geometry' you quoted has the standard 255 heads and 63 sectors pseudo-geometry for both devices, and even in the days of real chs geometry issues those issues revolved around the number of heads and the number of sectors per track rather than the number of cylinders on the volume. The dd way of copying to CF is pretty standard these days, and works almost all the time. But this is all speculation without seeing what is causing the filesystem to go read-only.
On Tuesday, November 30, 2010 02:13:17 pm Robert Heller wrote:> Right. clonezilla is much more than dd. I would suspect that > clonezilla is a bundling of sfdisk, dump/restore, and grub-install, or > something link that.According to the clonezilla website, dd is one of the supported methods: "Based on Partclone (default), Partimage (optional), ntfsclone (optional), or dd to image or clone a partition. However, Clonezilla, containing some other programs, can save and restore not only partitions, but also a whole disk. " I have yet to have a dd clone go awry; not that it can't happen, but in years of doing this sort of thing, on multiple different Unix-type OS's (and real AT&T Unix) I have yet to have issues there. But that reminds me that I need to get a newer clonezilla live anyway....
On Tuesday, November 30, 2010 01:10:14 pm Brunner, Brian T. wrote:> Even if the two disks have the same manufacturer and manufacturer part > number, different firmware revisions can fail to boot after > dd if=/dev/spinpoint.partnumber.fwrev1 of=/dev/spinpoint.partnumber.fwrev2> Been there, done that, got bit where the sun doesn't shine.Care to share specifics? This would be interesting information.