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

/home directary data loss(SOLVED)



>Date: Mon, 12 Jan 2009 15:39:11 -0500
>From: Bill Davidsen <davidsen tmr com>
>Subject: Re: /home directary data loss
>To: fedora-list redhat com
>Message-ID: <gkg9pf$dkf$2 ger gmane org>
>Content-Type: text/plain; charset=UTF-8; format=flowed
>
>Craig White wrote:
>> On Mon, 2009-01-12 at 12:35 +0800, 王�峰 wrote:
>>>> Date: Sat, 10 Jan 2009 22:09:56 -0700
>>>> From: Craig White <craigwhite azapple com>
>>>> Subject: Re: /home directary data loss
>>>> To: "Community assistance, encouragement,    and advice for using
>>>>>     Fedora." <fedora-list redhat com>
>>>> Message-ID: <1231650596 4520 650 camel lin-workstation azapple com>
>>>> Content-Type: text/plain; charset="UTF-8"
>>>
>>> On Sun, 2009-01-11 at 12:41 +0800, 王�峰 wrote:
>>>> Help!
>>>> I used "yum update" updated my system the other day, then I
>>  restarted
>>>> the computer, but it couldn't get in!
>>>> So I used the DVD containing Fedora ISO to rescue the system, but I
>>>> still saw nothing in /home/houghes which stores all my important
>>>> files!
>>>> But then my first aim was to get the system up, and I used the DVD and
>>>> chose "update existing sytem" hoping to get back to the point where I
>>>> hadn't updated Fedora using "yum update". Though this is not the
>>>> result, I got it!
>>>> But I still couldn't see anything in /home/houghes !
>>>> And since the system start-up process is so different from before, I
>>>> covered /boot/grub/grub.conf with /boot/grub/grub.conf~ , and the
>>>> start-up is normal now!
>>>> But how Can I Get My /home/houghes data back?! Help!
>>> ----
>>> Is it possible that /home was on a separate partition and isn't mounted?
>>>
>>> what do you get when run
>>  the following commands?
>>> fdisk -l /dev/sda
>>> mount
>>>
>>> Craig
>>>
>>>
>> following is got by running fdisk -l /dev/sda and mount:
>> [root joggerwang ~]# fdisk -l /dev/sda
>>
>> Disk /dev/sda: 160.0 GB, 160041885696 bytes
>> 255 heads, 63 sectors/track, 19457 cylinders
>> Units = cylinders of 16065 * 512 = 8225280 bytes
>> Disk identifier: 0x662db0cb
>>
>>    Device Boot      Start        End      Blocks  Id  System
>> /dev/sda1  *          1          25      200781  83  Linux
>> /dev/sda2              26        8948    71673997+  83  Linux
>> /dev/sda3            8949      10860    15358140  83  Linux
>> /dev/sda4          10861      19457    69055402+  5  Extended
>> /dev/sda5          10861      12772    15358108+  83  Linux
>> /dev/sda6          12773      14684    15358108+  83  Linux
>> /dev/sda7          14685      15703    8185086  83  Linux
>> /dev/sda8          15704      16340    5116671  83  Linux
>> /dev/sda9          16341      19457    25037271  8e  Linux LVM
>> [root joggerwang ~]# mount
>> /dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
>> /proc on /proc type proc (rw)
>> sysfs on /sys type sysfs (rw)
>> devpts on /dev/pts type devpts (rw,gid=5,mode=620)
>> /dev/sda6 on /usr type ext3 (rw)
>> /dev/sda5 on /var type ext3 (rw)
>> /dev/sda3 on /opt type ext3 (rw)
>> /dev/sda1 on /boot type ext3 (rw)
>> tmpfs on /dev/shm type tmpfs (rw)
>> none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
>> sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
>> gvfs-fuse-daemon on /root/.gvfs type fuse.gvfs-fuse-daemon
>> (rw,nosuid,nodev)
>>
>>
>> /dev/sda2 ought to be the partition I seperated for /home,
>> and /dev/sda7, /dev/sda8 are seperated for /usr/local and /tmp
>> respectively, so I tried to  add three lines in /etc/mtab for them as
>> follows:
>> /dev/sda2 /home ext3 rw 0 0
>> /dev/sda7 /usr/local ext3 rw 0 0
>> /dev/sda8 /tmp ext3 rw 0 0
>> and in /etc/fstab as follows:
>> UUID=61b8990c-043e-4d1f-9a37-7f330cc49eb5 /home
>> ext3    defaults        1 1
>> UUID=0cf03423-386b-407b-a60b-54c076692d77 /usr/local
>> ext3    defaults        1 1
>> UUID=d8297ee9-bd48-4b2c-a81a-ba0afdf42d0d /tmp
>> ext3    defaults        1 1
>> but my files in /home/houghes still don't come out!
>> What should I do?
> ----
> first, take a looksee at /dev/sda2 and see if that really is your
>> old /home...
>>
>> mkdir /home/oldhome
>> mount /dev/sda2 /home/oldhome
>> ls -l /home/oldhome
>
>> if it is, you can figure out the UUID of /dev/sda2, probably just by
>> doing...
>>
>> # ls -l /dev/disk/by-uuid/
>>
>> and putting that UUID into /etc/fstab for a /home mount
>>
>> I don't think that editing mtab is going to be useful.
>>
>May I suggest 'blkid' for stuff like this? Far easier to understand.
>
>--
>Bill Davidsen <davidsen tmr com>
>  "We have more to fear from the bungling of the incompetent than from
>the machinations of the wicked."  - from Slashdot



Thanks all! The problem is finally solved!
I add below lines in /etc/fstab, then it's OK!
UUID=47612fc6-286d-4c3f-b5c1-32abf7b3c9f3 /home                   ext3    defaults        1 2
UUID=07cfacc5-564d-4113-af74-eec8576bfe12 /usr/local              ext3    defaults        1 2
UUID=1cfbb0d5-4192-468a-b6ae-f3a4603dedc8 /tmp                    ext3    defaults        1 2
then UUID here is got from 'blkid', not /dev/disk/by-uuid/, as following:
# blkid
/dev/sda2: UUID="61b8990c-043e-4d1f-9a37-7f330cc49eb5" TYPE="crypt_LUKS"
/dev/sda7: UUID="0cf03423-386b-407b-a60b-54c076692d77" TYPE="crypt_LUKS"
/dev/sda8: UUID="d8297ee9-bd48-4b2c-a81a-ba0afdf42d0d" TYPE="crypt_LUKS"
/dev/mapper/luks-61b8990c-043e-4d1f-9a37-7f330cc49eb5: UUID="47612fc6-286d-4c3f-b5c1-32abf7b3c9f3" TYPE="ext3" SEC_TYPE="ext2"
/dev/mapper/luks-d8297ee9-bd48-4b2c-a81a-ba0afdf42d0d: UUID="1cfbb0d5-4192-468a-b6ae-f3a4603dedc8" TYPE="ext3" SEC_TYPE="ext2"
/dev/mapper/luks-0cf03423-386b-407b-a60b-54c076692d77: UUID="07cfacc5-564d-4113-af74-eec8576bfe12" TYPE="ext3" SEC_TYPE="ext2"




好玩贺卡等你发,邮箱贺卡全新上线!
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]