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

Re: live-snapshot question (2)

Hi Geert,

Strange, the end of sda1 is 110 and 110 is also the start of sda2.

This is from a disk over here:
|# fdisk -l /dev/hda
|Disk /dev/hda: 6448 MB, 6448619520 bytes
|240 heads, 63 sectors/track, 833 cylinders
|Units = cylinders of 15120 * 512 = 7741440 bytes
|Disk identifier: 0xcd9ec9d4
|   Device Boot      Start         End      Blocks   Id  System
|/dev/hda1   *           1          36      272128+  83  Linux
|/dev/hda2              37         833     6025320    5  Extended
|/dev/hda5              37         332     2237728+  83  Linux
|/dev/hda6             333         471     1050808+  83  Linux
|/dev/hda7             472         515      332608+  82  Linux swap / Solaris
|/dev/hda8             516         539      181408+  83  Linux
|/dev/hda9             540         833     2222608+  83  Linux

Hmm, I just took the default that fdisk presented, maybe I should have given it a nudge up one. I'll have to look into if this.

There is a /dev/sda1, which is good.
That /dev/sda1 is type vfat is so what strange to me.

Just took the default on this. Here's an exerpt from the manual:

syslinux for HDD or USB drive boot from a VFAT partition...

The 'persistent=nofiles' looks odd..

This is an option, that I needed to use because right now the box has ufs filesystems and when debian live would traverse those filesystems looking for the live-sn.cpio.gz file it panics.

Here is what the live-initramfs man page says about the nofiles options:

 If "nofiles" is specified, only filesystems with matching labels will be searched; no
           filesystems will be traversed looking for archives or image files. This results in shorter boot times.

I thought that since the /dev/sda2 filesystem has a "live-sn" label that this would work very nicely. But it's still not finding the partition with the snapshot file. I'm wondering if "live-sn" is not one of the labels that it recognizes.

I also realize now that I was using the "persistent-path" option wrong. Right now I'm passing in the device name but I think it's actually looking for a directory structure. After re-re-reading the man page for this option I think I finally understand that it's intended to allow you to have different directories on a partition so you can have different snapshot images going on. So this was not doing me any good. I've removed it but it still did not get me persistence.

The output of `e2label /dev/sda2`

MONSTERMASH:~# e2label /dev/sda2
The output of `cat /proc/partitions` on the live system.

MONSTERMASH:~# cat /proc/partitions
major minor  #blocks  name

   3     0  976762584 hda
   3     1  976762550 hda1
   3    64  976762584 hdb
   3    65  976762550 hdb1
   8     0    7831552 sda
   8     1     154623 sda1
   8     2    1999616 sda2
   7     0     140656 loop0

I *think* what is happening is that live-sn is not being matched as a label that live-initramfs should use, thus since I have the "nofiles" option, it just passes right by it. The other possible work-around I see would be to remove my ufs partitions and put partitions on the box that debian-live likes, this way I could remove the "nofiles" option. But I don't want to remove the ufs partitions which and put ext* until I know deb live will work well for me.

Do you know if "live-sn" is one of the filesystem labels that live-initramfs looks for?

Thanks again for the help.

Romeo Theriault

Reply to: