On Sat, 2004-07-03 at 17:32, Ed Mack wrote:
> Hi, I received in my magazine (Linux Format, UK) a dvd copy of the FC2
> release, and eagerly installed it.
>
> Previously I had installed test3 of FC2, but it was unable to properly
> read/write on my second hard drive:
>
> [root@localhost root]# hdparm -i /dev/hdb
>
> /dev/hdb:
>
> Model=SAMSUNG SP1604N, FwRev=TM100-23, SerialNo=0651J1FW881398
> Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
> RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
> BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
> CurCHS=4047/16/255, CurSects=16511760, LBA=yes, LBAsects=268435455
> IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
> PIO modes: pio0 pio1 pio2 pio3 pio4
> DMA modes: mdma0 mdma1 mdma2
> UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
> AdvancedPM=no WriteCache=enabled
> Drive conforms to: (null):
>
> Usage:
>
> [root@localhost root]# df
> Filesystem 1K-blocks Used Available Use% Mounted on
>
> /dev/hdb1 153834852 79450276 66570160 55% /mnt/home
>
>
>
>
> It's a new(ish) ~200gig drive, I use to hold all of /home so that
> upgrades are painless.
>
> Anyway, when using FC2 test3, I couldn't use the drive at all really, so
> gave up and fresh-installed FC1. This worked perfectly, and during all
> my non FC2 time, the drive has worked 100% perfectly - never any data
> loss or problems. I really do _not_ feel the disk is dying at all
>
> Anyway, firing up FC2 and adjusting /etc/fstab to the following:
>
> /dev/hdb1 /home auto defaults,noauto,rw
> 0 0
>
> Anway, I created a user EdMack to match the uid and user-dir on the
> drive, and logged in.
>
> So, logging in fails. Here's a directory listing from
> /home/edmond (edmack's home dir.. I know..)
>
> bash-2.05b$ ls -l
> total 8
> drwxr-xr-x 5 edmack 503 4096 Jul 3 13:37 Desktop
> drwx------ 10 edmack 503 4096 Jun 23 19:00 evolution
> ?--------- ? ? ? ? ? fonts
> ?--------- ? ? ? ? ? skype
> ?--------- ? ? ? ? ? Templates
>
> Trying to visit Templates (once a dir..)
>
> bash-2.05b$ cd Templates
> bash: cd: Templates: Input/output error
>
> When trying to write a file:
> [ Could not open file for writing: Read-only file system ]
> (due to below..)
>
> Here's the dmesg errors (many many times):
>
> kjournald starting. Commit interval 5 seconds
> EXT3-fs warning (device hdb1): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure
> EXT3-fs warning (device hdb1): ext3_clear_journal_err: Marking fs in need of filesystem check.
> EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
> EXT3 FS on hdb1, internal journal
> EXT3-fs: recovery complete.
> EXT3-fs: mounted filesystem with ordered data mode.
> ...
> attempt to access beyond end of device
> hdb1: rw=0, want=274989144, limit=268413957
> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode block - inode=17187087, block=34373642
> ...
> Aborting journal on device hdb1.
> ext3_abort called.
> EXT3-fs abort (device hdb1): ext3_journal_start: Detected aborted journal
> Remounting filesystem read-only
>
> Runnig badblocks -nsv gives me clear (didn't test 100% of disk)
>
> Any information you need I'll try my best to obtain - please help :) I'm
> kinda stuck here with no access to about 80gigs of personal data (I've
> backed up to cds a lot, but nowhere near all - especially not my most
> recent projects..) Any ingenious ways to back up about 80gigs in a home (I'm a student, no techie job)
> situation are greatly appreciated ;)
>
> Anyway, Thank you very much for your time and efforts
> Ed Mack
>
What type filesystem is on hdb1?
This type error was seen a short time ago when the drive was being
mounted as vfat, even though it was actually an ext3 filesystem.
IIRC the poster in that case had used a drive that was originally
partitioned using M$, then all he did was change the partiton type and
formatted the filesystem. It mounted the drive as vfat automatially.
When he manually told it to mount as ext3 it worked.
You might try unmounting it, then doing a "mount -t ext3 /dev/hdb1
/home" to see if that gives anything different.
"# fdisk -l /dev/hdb" and "mount" may also give some useful information
Good luck.
Jeff
