On 08/29/2013 02:12 PM, g issued this missive:
On 08/29/2013 01:32 PM, Greg Woods wrote:
<>
Notice the pound sign prompt in my example? Yes, you have to run tune2fs
as root (or use sudo).
now that you mention it. ;=)
[geo@localhost Documents]$ su
Password:
[root@localhost Documents]# tune2f
On 08/29/2013 01:32 PM, Greg Woods wrote:
<>
Notice the pound sign prompt in my example? Yes, you have to run tune2fs
as root (or use sudo).
now that you mention it. ;=)
[geo@localhost Documents]$ su
Password:
[root@localhost Documents]# tune2fs -l /dev/sdb3
tune2fs 1.41.12 (17-May-2010)
Fil
On Thu, 2013-08-29 at 12:16 -0500, g wrote:
>
> On 08/29/2013 09:26 AM, Greg Woods wrote:
> <>
>
> > If the file system is ext2, ext3, or ext4, then the UUID for a file
> > system on a physical or LVM device can be printed with UUID:
> >
> > # tune2fs -l /dev/sda1
> >
> > or
> >
> > # tune2fs -l
On 08/29/2013 09:26 AM, Greg Woods wrote:
<>
If the file system is ext2, ext3, or ext4, then the UUID for a file
system on a physical or LVM device can be printed with UUID:
# tune2fs -l /dev/sda1
or
# tune2fs -l /dev/mapper/ROOT-ROOT
(change device names as appropriate for your system)
On 08/29/2013 03:55 PM, g wrote:
>
>
> On 08/29/2013 06:46 AM, Mark Haney wrote:
> <<>>
>>
>>> My first guess would be to check that you're using the exact same UUID in
>>> the boot parameter as on the drive partition. Check the partition UUID is
>>> what you thought it is. Check for typos in t
On Thu, 2013-08-29 at 08:55 -0500, g wrote:
>
> On 08/29/2013 06:46 AM, Mark Haney wrote:
> <<>>
> >
> >> My first guess would be to check that you're using the exact same UUID in
> >> the boot parameter as on the drive partition. Check the partition UUID is
> >> what you thought it is. Check fo
On 08/29/2013 06:46 AM, Mark Haney wrote:
<<>>
My first guess would be to check that you're using the exact same UUID in
the boot parameter as on the drive partition. Check the partition UUID is
what you thought it is. Check for typos in the boot configuration.
So how exactly would I be
My first guess would be to check that you're using the exact same UUID
in the boot parameter as on the drive partition. Check the partition
UUID is what you thought it is. Check for typos in the boot
configuration.
So how exactly would I be able to do that from dracut? I simply can't imagine
On Tue, 2013-08-27 at 12:08 +, Mark Haney wrote:
> for whatever reason the system can see the HDD and install just fine
> on my Gateway (Samsung) netbook but won't boot after install using the
> UUID
My first guess would be to check that you're using the exact same UUID
in the boot parameter a
On Aug 27, 2013 5:08 AM, "Mark Haney" wrote:
>
> Hi all, I've had this problem with Fedora since I got this netbook, and
have been able to fix it until F19 came along. Here's my problem, for
whatever reason the system can see the HDD and install just fine on my
Gateway (Samsung) netbook but won't
Hi all, I've had this problem with Fedora since I got this netbook, and have
been able to fix it until F19 came along. Here's my problem, for whatever
reason the system can see the HDD and install just fine on my Gateway (Samsung)
netbook but won't boot after install using the UUID. With F16 a
11 matches
Mail list logo
