LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   Brand new HDD and reiser meltdown (https://www.linuxquestions.org/questions/linux-hardware-18/brand-new-hdd-and-reiser-meltdown-369495/)

generic_genus 10-03-2005 05:49 PM

Brand new HDD and reiser meltdown
 
Long time since I've had to ask for help here (so long ago I forgot my username/pwd), and a happy time it was. Anyways down to business...

I just bought a nice Seagate 200GB HDD and used gparted to create a 100GB reiserfs partition, all went well mounted the drive fine, moved 30GB of my data accross to the new partition. Great I thought job done, browsed the internet for a bit then came the reboot...

On boot when disc checks were running boot stopped and I'm told /dev/hda1 can't be checked and must be fixed manually, it is suggested that I run:

Code:

reiserfsck --sb-rebuild
and I've since run
Code:

fsck.reiserfs --rebuild-tree --scan-whole-partition /dev/hda1
with no luck

so I do and receive I few error messages I should have written down :(. Anyways dmesg has this to say:

Code:

ReiserFS: hda1: found reiserfs format "3.6" with standard journal
ReiserFS: hda1: using ordered data mode
ReiserFS: hda1: journal params: device hda1, size 8192, journal first block 18,                  max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda1: checking transaction log (hda1)
ReiserFS: warning: is_tree_node: node level 17989 does not match to the expected                  one 65534
ReiserFS: hda1: warning: vs-5150: search_by_key: invalid format found in block 0                  . Fsck?
ReiserFS: hda1: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occur                  red trying to find stat data of [1 2 0x0 SD]
ReiserFS: hda1: Using r5 hash to sort names
ReiserFS: hda1: warning: xattrs/ACLs enabled and couldn't find/create .reiserfs_                  priv. Failing mount.

Distro: gentoo
Drive: 200GB Seagate Barracuda 8MB Cache 7200rpm ATA100

My fstab:
Code:

# <fs>                  <mountpoint>    <type>          <opts>                  <dump/pass>

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/hdb1              /              reiserfs        noatime,notail,user_xattr              1 1
/dev/hdb3              /home          ext3            noatime,user_xattr                      1 1
/dev/hda1              /mp3s          reiserfs        noatime,notail,user_xattr              1 1
/dev/hdb4              none            swap            sw                      0 0

/dev/hdc                /mnt/dvd        iso9660        noauto,ro,user          0 0
/dev/hdd                /mnt/cdrw      iso9660        noauto,ro,user          0 0

/dev/sda1              /mnt/usb        auto            noauto,user,rw,gid=100  0 0
/dev/sdb1              /mnt/usb2      auto            noauto,user,rw,gid=100  0 0

/dev/fd0                /mnt/floppy    auto            noauto,user            0 0

# NOTE: The next line is critical for boot!
none                    /proc          proc            defaults                0 0

# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
#  use almost no memory if not populated with files)
# Adding the following line to /etc/fstab should take care of this:

none                    /dev/shm        tmpfs          defaults                0 0

and finally debugreiserfs returns:
Code:

debugreiserfs 3.6.19 (2003)
Filesystem state: consistency is not checked after last mounting

Reiserfs super block in block 16 on 0x301 of format 3.6 with standard journal
Count of blocks on the device: 48840240
Number of bitmaps: 1491
Blocksize: 4096
Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 48840240
Root block: 0
Filesystem is NOT clean
Tree height: 65535
Hash function used to sort names: "r5"
Objectid map size 2, max 972
Journal parameters:
        Device [0x0]
        Magic [0x0]
        Size 8193 blocks (including 1 for journal header) (first block 18)
        Max transaction length 1024 blocks
        Max batch size 900 blocks
        Max commit age 30
Blocks reserved by journal: 0
Fs state field: 0xfa02:
        FATAL corruptions exist.
sb_version: 2
inode generation number: 0
UUID: a3c204c0-e9fe-41d5-b41e-cc276cf4e3dc
LABEL:
Set flags in SB:


combatwombat 10-05-2005 03:59 AM

Don't assume that because the drive is new it's good.
I build PCs for a living, and the highest failure rate comes from harddisks, some DOA, some die in the first month.
I've noticed that there is a general rule; if it lasts past a month then it'll go at least 3 years.

Also, Seagate has a diagnostic program that you can download(as an .ISO), burn to CD, boot to it, and check the disk. You can also then print a report for warranty claim.

Linux is unforgiving to disk problems, which is good and bad, depending on your viewpoint.

generic_genus 10-05-2005 06:33 AM

Thanks for the pointer, one angle of attack I hadn't thought of blame the manufacturer :). I'll report back to you once I've got the chance to repair the disk.

Cheers,


All times are GMT -5. The time now is 05:36 PM.