I can''t seem to mount the local disk image:
[root@basket mapper]# losetup -f /var/lib/xen/images/vutil.img
[root@basket mapper]# losetup -a
/dev/loop0: [fd00]:79331424 (/var/lib/xen/images/vutil.img)
[root@basket mapper]# mount -o loop -t ext4 /dev/loop0 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/loop2,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
--
Robert Threet
http://yesistilluseperl.blogspot.com/
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
just do ''mount /dev/loop0 /mnt'' -- once you''ve done losetup you don''t need the -o loop anymore. --igor On Mon, May 09, 2011 at 03:57:16PM -0500, Robert Threet wrote:> I can''t seem to mount the local disk image: > > [root@basket mapper]# losetup -f /var/lib/xen/images/vutil.img > [root@basket mapper]# losetup -a > /dev/loop0: [fd00]:79331424 (/var/lib/xen/images/vutil.img) > > [root@basket mapper]# mount -o loop -t ext4 /dev/loop0 /mnt > mount: wrong fs type, bad option, bad superblock on /dev/loop2, > missing codepage or other error > In some cases useful info is found in syslog - try > dmesg | tail or so > > -- > Robert Threet > http://yesistilluseperl.blogspot.com/ > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Still having issues. I ran losetup twice - problem? Also - I did not
creat a separate LVM filesystem for vutil - it just created the flat
file in /var/lib/xen/images/vutil.img. vutil is down.
[root@basket ~]# losetup -a
/dev/loop0: [fd00]:79331424 (/var/lib/xen/images/vutil.img)
/dev/loop1: [fd00]:79331424 (/var/lib/xen/images/vutil.img)
[root@basket ~]# mount /dev/loop0 /mnt
mount: /dev/loop0 already mounted or /mnt busy
[root@basket ~]# umount /dev/loop0
umount: /dev/loop0: not mounted
[root@basket ~]# mount /dev/loop1 /mnt
mount: you must specify the filesystem type
[root@basket ~]# mount -t ext4 /dev/loop1 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/loop1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
[root@basket ~]# mount -t ext3 /dev/loop1 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/loop1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
[root@basket ~]# xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 9333 4 r----- 91413.4
lnximag1 4 1027 1 -b---- 2355.5
vauction 16 1024 1 -b---- 3029.8
vlists 19 1026 1 -b---- 746.2
vpipelin 20 1027 1 -b---- 518.8
On 05/09/2011 04:41 PM, Igor Serebryany wrote:> just do ''mount /dev/loop0 /mnt'' -- once you''ve
done losetup you don''t
> need the -o loop anymore.
>
> --igor
>
> On Mon, May 09, 2011 at 03:57:16PM -0500, Robert Threet wrote:
>> I can''t seem to mount the local disk image:
>>
>> [root@basket mapper]# losetup -f /var/lib/xen/images/vutil.img
>> [root@basket mapper]# losetup -a
>> /dev/loop0: [fd00]:79331424 (/var/lib/xen/images/vutil.img)
>>
>> [root@basket mapper]# mount -o loop -t ext4 /dev/loop0 /mnt
>> mount: wrong fs type, bad option, bad superblock on /dev/loop2,
>> missing codepage or other error
>> In some cases useful info is found in syslog - try
>> dmesg | tail or so
>>
>> --
>> Robert Threet
>> http://yesistilluseperl.blogspot.com/
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
--
Robert Threet
Systems Manager
USI Computer Center
(812) 465-1082
Confidentiality Statement: This email message, including any
attachments, is for the sole use of the intended recipient(s) and may
contain confidential and privileged information.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
You probably have dos partitions on your disk images to make them aviable : #rmmod loop #modprobe loop max_part=63 Mount your images with losetup you will now have devices like : /dev/loop0p0 /dev/loop0p1 Wich are the dos partitions on your disk images You should be able to mount them. If you have lvm partitions, instead of mounting the loop device : #vgscan #vgchange -ay your lvs should be avaible in /dev/<vgname>/ unless you named your guest vg like an existing vg on the host in wich case you have to rename the vg on the host ( it seems it can be done without unmounting , don''t forget to revert ) Le 10/05/2011 17:33, Robert Threet a écrit :> Still having issues. I ran losetup twice - problem? Also - I did not > creat a separate LVM filesystem for vutil - it just created the flat > file in /var/lib/xen/images/vutil.img. vutil is down. > > [root@basket ~]# losetup -a > /dev/loop0: [fd00]:79331424 (/var/lib/xen/images/vutil.img) > /dev/loop1: [fd00]:79331424 (/var/lib/xen/images/vutil.img) > [root@basket ~]# mount /dev/loop0 /mnt > mount: /dev/loop0 already mounted or /mnt busy > [root@basket ~]# umount /dev/loop0 > umount: /dev/loop0: not mounted > [root@basket ~]# mount /dev/loop1 /mnt > mount: you must specify the filesystem type > [root@basket ~]# mount -t ext4 /dev/loop1 /mnt > mount: wrong fs type, bad option, bad superblock on /dev/loop1, > missing codepage or other error > In some cases useful info is found in syslog - try > dmesg | tail or so > > [root@basket ~]# mount -t ext3 /dev/loop1 /mnt > mount: wrong fs type, bad option, bad superblock on /dev/loop1, > missing codepage or other error > In some cases useful info is found in syslog - try > dmesg | tail or so > > [root@basket ~]# xm list > Name ID Mem(MiB) VCPUs State Time(s) > Domain-0 0 9333 4 r----- 91413.4 > lnximag1 4 1027 1 -b---- 2355.5 > vauction 16 1024 1 -b---- 3029.8 > vlists 19 1026 1 -b---- 746.2 > vpipelin 20 1027 1 -b---- 518.8 > > > On 05/09/2011 04:41 PM, Igor Serebryany wrote: >> just do ''mount /dev/loop0 /mnt'' -- once you''ve done losetup you don''t >> need the -o loop anymore. >> >> --igor >> >> On Mon, May 09, 2011 at 03:57:16PM -0500, Robert Threet wrote: >>> I can''t seem to mount the local disk image: >>> >>> [root@basket mapper]# losetup -f /var/lib/xen/images/vutil.img >>> [root@basket mapper]# losetup -a >>> /dev/loop0: [fd00]:79331424 (/var/lib/xen/images/vutil.img) >>> >>> [root@basket mapper]# mount -o loop -t ext4 /dev/loop0 /mnt >>> mount: wrong fs type, bad option, bad superblock on /dev/loop2, >>> missing codepage or other error >>> In some cases useful info is found in syslog - try >>> dmesg | tail or so >>> >>> -- >>> Robert Threet >>> http://yesistilluseperl.blogspot.com/ >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xensource.com >>> http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, Apparently I can''t find back the original question, but if the problem is in the lost root password as the subj suggests, there is a nice trick: set Boot OS parameters (XenCenter, VM Properties, Startup Options) to ''init=/bin/sh'' and reboot -- you will get root prompt on your console. You''ll have to remount your root file system in rw mode (mount -o remount,rw /) before you can make any changes on the file system. Just my 2 cents. Cheers, Alex www.gremwell.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I normally start the domU using xm -c , edit the grub menu and add ''single'' or ''1'' at the end then it will boot to the single mode . Then change the password. Paras. On Wed, May 11, 2011 at 6:57 AM, Alexandre Bezroutchko <abb@gremwell.com> wrote:> Hi, > > Apparently I can''t find back the original question, but if the problem is in > the lost root password as the subj suggests, there is a nice trick: set Boot > OS parameters (XenCenter, VM Properties, Startup Options) to ''init=/bin/sh'' > and reboot -- you will get root prompt on your console. You''ll have to > remount your root file system in rw mode (mount -o remount,rw /) before you > can make any changes on the file system. Just my 2 cents. > > Cheers, > Alex > www.gremwell.com > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Still cannot mount filessystem. I *can* mount loop0p1 - it''s the /boot
partition.
[root@basket ~]# losetup -a
/dev/loop0: [fd00]:79331424 (/var/lib/xen/images/vutil.img)
[root@basket ~]# mount /dev/loop0 /mnt
mount: you must specify the filesystem type
[root@basket ~]# mount -o loop /dev/loop0 /mnt
mount: you must specify the filesystem type
[root@basket ~]# mount -o loop -t ext3 /dev/loop0 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/loop1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
You have new mail in /var/spool/mail/root
[root@basket ~]# kpartx -av /dev/loop0
add map loop0p1 : 0 208782 linear /dev/loop0 63
add map loop0p2 : 0 51183090 linear /dev/loop0 208845
[root@basket ~]# mount /dev/mapper/loop0p2 /mnt
mount: you must specify the filesystem type
[root@basket ~]# mount -t ext3 /dev/mapper/loop0p2 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/mapper/loop0p2,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
--
Robert Threet
Systems Manager
USI Computer Center
(812) 465-1082
Confidentiality Statement: This email message, including any
attachments, is for the sole use of the intended recipient(s) and may
contain confidential and privileged information.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Ok - not sure why that didn''t work but thanks so much for the xm -c idea. Combined with the other ideas I was able to resolve the issue. Gory details: http://myratnest.blogspot.com/2011/05/more-fun-with-xen.html On 05/11/2011 10:12 AM, Robert Threet wrote:> Still cannot mount filessystem. I *can* mount loop0p1 - it''s the /boot > partition. > > [root@basket ~]# losetup -a > /dev/loop0: [fd00]:79331424 (/var/lib/xen/images/vutil.img) > [root@basket ~]# mount /dev/loop0 /mnt > mount: you must specify the filesystem type > [root@basket ~]# mount -o loop /dev/loop0 /mnt > mount: you must specify the filesystem type > [root@basket ~]# mount -o loop -t ext3 /dev/loop0 /mnt > mount: wrong fs type, bad option, bad superblock on /dev/loop1, > missing codepage or other error > In some cases useful info is found in syslog - try > dmesg | tail or so > > You have new mail in /var/spool/mail/root > [root@basket ~]# kpartx -av /dev/loop0 > add map loop0p1 : 0 208782 linear /dev/loop0 63 > add map loop0p2 : 0 51183090 linear /dev/loop0 208845 > [root@basket ~]# mount /dev/mapper/loop0p2 /mnt > mount: you must specify the filesystem type > [root@basket ~]# mount -t ext3 /dev/mapper/loop0p2 /mnt > mount: wrong fs type, bad option, bad superblock on /dev/mapper/loop0p2, > missing codepage or other error > In some cases useful info is found in syslog - try > dmesg | tail or so >-- Robert Threet Systems Manager USI Computer Center (812) 465-1082 Confidentiality Statement: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Alexandre Bezroutchko
2011-May-11 16:21 UTC
Re: [Xen-users] Re: lost root password in guest
In XCP/XenServer it is supposed to be possible too, with ''xe-edit-bootloader'' command. I tried it, but somehow it can''t find a partition to open... I thought ''single user mode'' requires root password still, at least for some Linux distros like Ubuntu. On 05/11/2011 04:33 PM, Paras pradhan wrote:> I normally start the domU using xm -c , edit the grub menu and add > ''single'' or ''1'' at the end then it will boot to the single mode . > Then change the password. > > Paras. > > > On Wed, May 11, 2011 at 6:57 AM, Alexandre Bezroutchko<abb@gremwell.com> wrote: >> Hi, >> >> Apparently I can''t find back the original question, but if the problem is in >> the lost root password as the subj suggests, there is a nice trick: set Boot >> OS parameters (XenCenter, VM Properties, Startup Options) to ''init=/bin/sh'' >> and reboot -- you will get root prompt on your console. You''ll have to >> remount your root file system in rw mode (mount -o remount,rw /) before you >> can make any changes on the file system. Just my 2 cents. >> >> Cheers, >> Alex >> www.gremwell.com >> >> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >>_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users