RE: [LUG] Problem with disk array.

["James Wonnacott" <jwon@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>]

> First off can you mount the device after creating the ext3 
> file system but before rebooting? ("mount /home")

Yes, no problem

> 
> If you can, can you unmount it and fsck the device before 
> rebooting? "umount /home ; e2fsck /dev/sda1"

[root@server01 root]# umount /home
[root@server01 root]# e2fsck /dev/sda1
e2fsck 1.35 (28-Feb-2004)
/dev/sda1: clean, 252791/48726016 files, 4932064/97424176 blocks (check
after next mount)

Why the "check after next mount" I don't know??????

> I'd have thought if it presents and lets you newfs and fsck 
> it correctly, and mounts correctly, but fails after 
> rebooting, it suggests either hardware issues, or a driver 
> problem. As such I'd be staring closely at the "dmesg" (or 
> boot messages) when it comes up, 

dmesg               [----]  0 L:[310+21 331/354] *(13998/15336b)= R  82
0x52
3ware Storage Controller device driver for Linux v1.26.00.039.
scsi0 : Found a 3ware Storage Controller at 0xe400, IRQ: 20, P-chip: 1.3
scsi0 : 3ware Storage Controller
  Vendor: 3ware     Model: Logical Disk 0    Rev: 1.2
  Type:   Direct-Access                      ANSI SCSI revision: 00
imm: Version 2.05 (for Linux 2.4.0)
SCSI device sda: 781439744 512-byte hdwr sectors (400097 MB)
SCSI device sda: drive cache: write back
parport0: PC-style at 0x378 (0x778)<6>
/dev/scsi/host0/bus0/target0/lun0: p1
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
 [PCSPP,TRISTATE]
parport0: irq 7 detected
ppa: Version 2.07 (for Linux 2.4.x)
Adding 2097104k swap on /dev/hda10.  Priority:-1 extents:1
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Supermount version 2.0.4 for kernel 2.6
ReiserFS: hda9: found reiserfs format "3.6" with standard journal

> and checking any
> documentation for the device. Also worth checking if the 
> behaviour is different with a cold reboot (Switch off for at 
> least 5 seconds) and a warm reboot.

No, it behaves the same in both cases.

I think there must be something flagging to check after each boot
but I don't know what.

It worked fine under Mandrake 10.0 but has done this since I upgraded
to 10.1

Many thanks

James


--
The Mailing List for the Devon & Cornwall LUG
Mail majordomo@xxxxxxxxxxxxx with "unsubscribe list" in the
message body to unsubscribe. FAQ: www.dcglug.org.uk/linux_adm/list-faq.html