"deleted inode referenced" after re-image

Raccoon1400 · 2009-09-11 04:33:45

I upgraded my hard drive and re-imaged it with dd.

When I boot arch, I get this error many times, and it fails the check and gives me a maintenance shell.
EXT4-fs error (device sda6): ext4_lookup: deleted inode referenced: 696988

drtoki · 2009-09-11 07:40:18

That inode probably got corrupted during the imaging process. I've experienced a similar problem and found that just deleting the link solved everything. To be on the safe side though, could you post the output of the following?

# debugfs /dev/sda6
debugfs: stat <696988>

sand_man · 2009-09-11 09:46:29

Did you dd the whole hdd or just the partition? From memory, dd'ing the whole hard drive can cause problems.

Raccoon1400 · 2009-09-11 13:31:44

drtoki wrote:

That inode probably got corrupted during the imaging process. I've experienced a similar problem and found that just deleting the link solved everything. To be on the safe side though, could you post the output of the following?
# debugfs /dev/sda6
debugfs: stat <696988>

EXT4-fs error (device sda6): ext4_lookup: deleted inode referenced: 696988
debugfs 1.41.8 (11-july-2009)
debugfs:

seems to stop there, if it does more I'll change this soon.

dd'd the whole drive.

FeatherMonkey · 2009-09-11 13:37:22

It's a command prompt you need the other bit now
stat <696988>

Raccoon1400 · 2009-09-11 14:03:53

Inode: 696988 Type: regular Mode: 0644 Flags: 0x80000
Generation 1716015439 Version: 0x00000001
User: 0 Group: 0 Size: 0
File ACL: 0 Blockcount: 0
Fragment: Adrerss: 0 Number:0 Size: 0
ctime: 0x4aa4284 -- Sun Sept 6 17:07:16 2009
atime: 0x4aa4284 -- Sun Sept 6 17:07:16 2009
mtime: 0x4aa4284 -- Sun Sept 6 17:07:16 2009
dtime: 0x4aa4284 -- Sun Sept 6 17:07:16 2009
BLOCKS:

R00KIE · 2009-09-11 14:55:53

sand_man wrote:

Did you dd the whole hdd or just the partition? From memory, dd'ing the whole hard drive can cause problems.

I would say that dd'in only one partition can cause more problems, if you dd the entire disk and restore the image to a disk of the same size or larger no problems should arrise, this of course if you do the image when the system is not running from disk. And just reading from disk should not cause any harm whatsoever.

The only problem I see with dd'ing the whole is the the huge amount of time and storage it takes

Raccoon1400 · 2009-09-11 15:40:51

R00KIE wrote:

sand_man wrote:
Did you dd the whole hdd or just the partition? From memory, dd'ing the whole hard drive can cause problems.
I would say that dd'in only one partition can cause more problems, if you dd the entire disk and restore the image to a disk of the same size or larger no problems should arrise, this of course if you do the image when the system is not running from disk. And just reading from disk should not cause any harm whatsoever.
The only problem I see with dd'ing the whole is the the huge amount of time and storage it takes

it took about 2 days to make the image and another 2 to put it back. I did make the image when the system was running. Oops.

sand_man · 2009-09-11 22:51:13

Raccoon1400 wrote:

R00KIE wrote:
sand_man wrote:
Did you dd the whole hdd or just the partition? From memory, dd'ing the whole hard drive can cause problems.
I would say that dd'in only one partition can cause more problems, if you dd the entire disk and restore the image to a disk of the same size or larger no problems should arrise, this of course if you do the image when the system is not running from disk. And just reading from disk should not cause any harm whatsoever.
The only problem I see with dd'ing the whole is the the huge amount of time and storage it takes
it took about 2 days to make the image and another 2 to put it back. I did make the image when the system was running. Oops.

All I have to say is, you are a patient man.

Raccoon1400 · 2009-09-12 05:03:28

I'm planning on reformating the partition on the new disk and rsyncing the files. I want a fresh filesystem anyway.
I fixed the original issue by having gparted repair it, but there are still other issues, like my inbox in evolution doesn't show messages.

R00KIE · 2009-09-13 14:15:31

How big is your drive? I can backup to/from usb an 80GB drive in about 2h30m I think, I went to play a game on another pc while doing that
I wouldn't use gparted that much if I were you, I have always had a bad time recovering from problems gparted creates
Now I always partition with cfdisk and at most I use gparted to format the partitions, cfdisk does a clean job at creating the partitions, gparted doesn't.

Raccoon1400 · 2009-09-13 17:41:13

I used rsync to copy the files from the old hard drive onto the new disk so I could have a fresh filesystem, and it worked.

ROOKIE: btw, old drive is 160, new one is 320

Arch Linux

#1 2009-09-11 04:33:45

"deleted inode referenced" after re-image

#2 2009-09-11 07:40:18

Re: "deleted inode referenced" after re-image

#3 2009-09-11 09:46:29

Re: "deleted inode referenced" after re-image

#4 2009-09-11 13:31:44

Re: "deleted inode referenced" after re-image

#5 2009-09-11 13:37:22

Re: "deleted inode referenced" after re-image

#6 2009-09-11 14:03:53

Re: "deleted inode referenced" after re-image

#7 2009-09-11 14:55:53

Re: "deleted inode referenced" after re-image

#8 2009-09-11 15:40:51

Re: "deleted inode referenced" after re-image

#9 2009-09-11 22:51:13

Re: "deleted inode referenced" after re-image

#10 2009-09-12 05:03:28

Re: "deleted inode referenced" after re-image

#11 2009-09-13 14:15:31

Re: "deleted inode referenced" after re-image

#12 2009-09-13 17:41:13

Re: "deleted inode referenced" after re-image

Board footer