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

Re: live-snapshot question (2)



Op 20100222 om 00:22 schreef Romeo Theriault:
> 
> > How does the partition table of the USBmemorystick look?
> >
> 
> Here is what the partition table on the USB stick looks like:
> 
> MONSTERMASH:~# fdisk -l /dev/sda
> 
> Disk /dev/sda: 8019 MB, 8019509248 bytes
> 64 heads, 44 sectors/track, 5562 cylinders
> Units = cylinders of 2816 * 512 = 1441792 bytes
> Disk identifier: 0x000d6bec
> 
>    Device Boot      Start         End      Blocks   Id  System
> /dev/sda1   *           1         110      154623+  83  Linux
> /dev/sda2             110        1530     1999616   83  Linux
> 

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


> > Can you mount the /dev/sdX2? I say sdX because the testcomputer may have
> > a /dev/sda (and a /dev/sdb ( and /dev/sdc)) for itself?
> 
> Yes, I can mount the sda2 partition fine, when I do it manually. Also, this
> is the only sdX device in the box, the HD's are showing up as hdX devices.

Acknowledge


> MONSTERMASH:~# mount /dev/sda2 /mnt
> MONSTERMASH:~# ls /mnt
> live-sn.cpio.gz  lost+found

Look good

> When in the live system, what shows `mount`?
> >
> 
> MONSTERMASH:~# mount
> aufs on / type aufs (rw)
> tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
> proc on /proc type proc (rw,noexec,nosuid,nodev)
> sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
> procbususb on /proc/bus/usb type usbfs (rw)
> udev on /dev type tmpfs (rw,mode=0755)
> tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
> devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
> /dev/sda1 on /live/image type vfat (ro,noatime,fmask=0022,dmask=0022,allow_utime=177777,codepage=cp437,iocharset=utf8)
> tmpfs on /live/cow type tmpfs (rw,noatime,mode=755)
> tmpfs on /live type tmpfs (rw)
> tmpfs on /tmp type tmpfs (rw,nosuid,nodev)

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

> > When in the live system, what is the output of `cat /proc/cmdline`?
> >
> 
> MONSTERMASH:~# cat /proc/cmdline
> initrd=/live/initrd1.img boot=live noautologin nouser persistent=nofiles
> quickreboot persistent-path=/dev/sda2 username=romeo hostname=MONSTERMASH
> union=aufs  BOOT_IMAGE=/live/vmlinuz1

The 'persistent=nofiles' looks odd..

> I'll be happy to provide any other info that may be useful.

The output of `e2label /dev/sda2`

The output of `cat /proc/partitions` on the live system.



HtH
GSt


Reply to: