Re: Advfs domain attached to MSA1000 does not mount after reboot: "I/O error"



Thanks Bob,

Now I got a reply from HP asking several things, see below.
I will see if they can analyze/fix the problem andwill let you know.

% /sbin/advfs/fixfdmn -n db3_domain
fixfdmn: Can't open device '/dev/disk/dsk14c'.
fixfdmn: Function not implemented
fixfdmn: No valid volumes found in domain 'db3_domain'.

fixfdmn found errors on disk it could not fix.
This domain should be restored from backup
tapes, or you can use the salvage tool to
pull what files it can find off of this domain.

% grep -i kitname /var/adm/patch/log/event.log
KITNAME><T64V51BB1AS0001-20021229> OSF540
KITNAME><T64V51BB26AS0005-20050502> OSF540

% grep "Driver Rev" /var/adm/messages |tail
Apr 10 22:07:17 mani vmunix: ee0: Driver Rev = V1.0.28, Chip Rev = 8,
hardware address: 00-08-02-DF-38-BA
Apr 10 22:07:18 mani vmunix: ee1: Driver Rev = V1.0.28, Chip Rev = 8,
hardware address: 00-08-02-DF-38-BB
Apr 10 22:07:18 mani vmunix: FCA-2354 : Driver Rev 2.17 : F/W Rev
3.92A2(1.30A1) : wwn 1000-0000-c931-4da9
Apr 10 22:07:18 mani vmunix: FCA-2354 : Driver Rev 2.17 : F/W Rev
3.92A2(1.30A1) : wwn 1000-0000-c931-4d7e
Apr 10 23:38:08 mani vmunix: Adaptec AIC-7899 Adapter: H/W Rev 1,
Driver Rev 2.278 CHIM V364A6
Apr 10 23:38:08 mani vmunix: Adaptec AIC-7899 Adapter: H/W Rev 1,
Driver Rev 2.278 CHIM V364A6
Apr 10 23:38:08 mani vmunix: ee0: Driver Rev = V1.0.28, Chip Rev = 8,
hardware address: 00-08-02-DF-38-BA
Apr 10 23:38:08 mani vmunix: ee1: Driver Rev = V1.0.28, Chip Rev = 8,
hardware address: 00-08-02-DF-38-BB
Apr 10 23:38:09 mani vmunix: FCA-2354 : Driver Rev 2.17 : F/W Rev
3.92A2(1.30A1) : wwn 1000-0000-c931-4da9
Apr 10 23:38:09 mani vmunix: FCA-2354 : Driver Rev 2.17 : F/W Rev
3.92A2(1.30A1) : wwn 1000-0000-c931-4d7e

% ls -Rl /etc/fdmns/db3_domain/
total 0
lrwxrwxr-x 1 root system 16 Aug 24 2005 dsk14c ->
/dev/disk/dsk14c

% hwmgr show scsi

SCSI DEVICE DEVICE DRIVER NUM DEVICE FIRST
HWID: DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID
PATH
-------------------------------------------------------------------------
58: 0 mani disk none 2 1 dsk0
[0/0/0]
59: 1 mani cdrom none 0 1 cdrom0
[2/0/0]
72: 2 mani disk none 2 1 dsk1
[0/1/0]
73: 3 mani tape none 0 1 tape0
[1/6/0]
81: 4 mani raid none 0 2 scp0
[4/0/0]
82: 5 mani disk none 0 1 (null)
83: 6 mani disk none 0 1 (null)
86: 7 mani disk none 0 2 (null)
87: 8 mani disk none 0 2 (null)
88: 9 mani disk none 0 2 (null)
89: 10 mani disk none 0 2 (null)
90: 11 mani disk none 0 2 (null)
92: 13 mani disk none 0 2 (null)
93: 14 mani disk none 0 2 (null)
94: 12 mani disk none 2 2 dsk12
[4/0/2]
95: 15 mani disk none 2 2 dsk13
[4/0/1]
98: 16 mani disk none 2 2 dsk14
[4/0/3]

% disklabel -r dsk14
# /dev/rdisk/dsk14c:
type: SCSI
disk: MSA1000 VOLUME
label:
flags:
bytes/sector: 512
sectors/track: 254
tracks/cylinder: 20
sectors/cylinder: 5080
cylinders: 21997
sectors/unit: 3440978415
rpm: 3600
interleave: 1
trackskew: 7
cylinderskew: 26
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0

Harald

.



Relevant Pages

  • CCD Issues
    ... sectors/track: 63 ... tracks/cylinder: 255 ... cylinders: 1105 ... disklabel: ioctl DIOCGDINFO: Invalid argument ...
    (freebsd-questions)
  • Problems with advfs-domain
    ... disk: -16U4P ... sectors/track: 128 ... tracks/cylinder: 128 ... cylinders: 14447 ...
    (Tru64-UNIX-Managers)
  • Disklabel again
    ... Interesting disklabel output though. ... sectors/track: 63 ... tracks/cylinder: 255 ... cylinders: 4405 ...
    (freebsd-questions)
  • Re: "Cannot find file system superblock" error - how to recover?
    ... FreeBSD 4.9, so I obtained a spare system which I installed FreeBSD ... sectors/track: 63 ... tracks/cylinder: 255 ... cylinders: 9731 ...
    (freebsd-questions)
  • Disklabel
    ... Interesting disklabel output though. ... sectors/track: 63 ... tracks/cylinder: 255 ... cylinders: 4405 ...
    (freebsd-questions)