Pro/Forums - View Single Post

rpmurray · 12-03-2008, 09:08 AM

Follow up:

Didn't think I'd be back so soon.

A hard shutdown (pulled the power plug), and restart did not solve the issue. I'm still seeing the same LED pattern.

I am now able to access via the web browser and here's what it's telling me in the server log:

E File System Check : Cannot Read: Blk 32960 Disk (Priv) 12/3/2008 8:54:40 AM
E Disk Driver : Cannot Read Device 80070006 Block 32960 Disk FFFFFFFF 12/3/2008 8:54:40 AM
E File System Check : Cannot Read: Blk 32960 Disk (Priv) 12/3/2008 8:54:32 AM
E Disk Driver : Cannot Read Device 80070006 Block 32960 Disk FFFFFFFF 12/3/2008 8:54:32 AM

It only seems to be logging the last 50 lines, everything prior to that gets removed when the log updates. The following is the slightly more detailed info I get when doing an "info log t", and it repeats over and over also.

12/03/2008 8:38:57 37 E L00 | File System Check : Cannot Read: Blk 32960
12/03/2008 8:39:01 37 D SYS | DISK: req=0x428AAC dev=0xC0000 fn=1 blk=0xA0F0 sts=20
12/03/2008 8:39:05 37 D SYS | DISK: req=0x428AAC dev=0xC0000 fn=1 blk=0xA0F0 sts=20
12/03/2008 8:39:05 37 D SYS | DISK: req=0x428AAC dev=0x80000 fn=1 blk=0xA0F0 sts=20
12/03/2008 8:39:05 37 E D[80070006] | Disk Driver : Cannot Read Device 80070006 Block 32960
12/03/2008 8:39:05 37 E L00 | File System Check : Cannot Read: Blk 32960
12/03/2008 8:39:09 37 D SYS | DISK: req=0x428AAC dev=0xC0000 fn=1 blk=0xA0F0 sts=20
12/03/2008 8:39:13 37 D SYS | DISK: req=0x428AAC dev=0xC0000 fn=1 blk=0xA0F0 sts=20
12/03/2008 8:39:13 37 D SYS | DISK: req=0x428AAC dev=0x80000 fn=1 blk=0xA0F0 sts=20
12/03/2008 8:39:13 37 E D[80070006] | Disk Driver : Cannot Read Device 80070006 Block 32960

"info dev" shows this:

Logical Device: 10006 Position: 0 JBOD Size (KB): 32768 Free (KB): 0 Private Unmounted
Label:Private Contains system files only
Unique Id: 0x07E172C1151F56A0 Mount: /priv Index: 12 Order: 255
Partition: 10006 Physical: 10007 FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 10007 Drive Slot: 0 IDE Size (KB): 134217216 Fixed

Logical Device: 1000E Position: 0 JBOD Size (KB): 32768 Free (KB): 0 Private Unmounted
Label:Private Contains system files only
Unique Id: 0x5DE062EE74C7D817 Mount: /pri2 Index: 13 Order: 255
Partition: 1000E Physical: 1000F FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 1000F Drive Slot: 1 IDE Size (KB): 134217216 Fixed

Logical Device: 60000 Position: 1 RAID Size (KB): 400329600 Free (KB): 0 Public Unmounted
Label:RAID5 Large data protection disk
Unique Id: 0x343BC2672C5DC315 Mount: /0 Index: 0 Order: 255
Partition: 10000 Physical: 10007 R 60000 Size (KB): 133443200 Starting Blk: 96624 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 134217216 Fixed
Partition: 10008 Physical: 1000F R 60000 Size (KB): 133443200 Starting Blk: 96624 Public
Physical: 1000F Drive Slot: 1 IDE Size (KB): 134217216 Fixed
Partition: 10010 Physical: 10017 R 60000 Size (KB): 133443200 Starting Blk: 96624 Public
Physical: 10017 Drive Slot: 2 IDE Size (KB): 134217216 Fixed
Partition: 10018 Physical: 1001F R 60000 Size (KB): 133443200 Starting Blk: 96624 Public
Physical: 1001F Drive Slot: 3 IDE Size (KB): 134217216 Fixed

And when I do an "info log p" I get this bit of wisdom:

Sorry, the 'Private Partition' does not exist, so no 'Permanent Log' can be stored.
HINT: If you reformat the first drive, the private partition will be created.

At the moment I'm mulling my options. I can do as it suggests and try reformatting Disk 1 (drive slot 0), or I can open it up and pull the power and data cable for the disk and see if it'll come up in degraded mode.

Any suggestions?

Any ideas on if there's a command I can issue to tell it to ignore disk 1 and come up using the other disks? Or to use the redundant info on the 'Private Partition' on Disk 2 (drive slot 1)?

12-03-2008, 09:08 AM	#2
rpmurray Cooling Savant Join Date: Apr 2006 Location: Tennessee Posts: 157	Re: Snap Server 4100 Lockup Follow up: Didn't think I'd be back so soon. A hard shutdown (pulled the power plug), and restart did not solve the issue. I'm still seeing the same LED pattern. I am now able to access via the web browser and here's what it's telling me in the server log: E File System Check : Cannot Read: Blk 32960 Disk (Priv) 12/3/2008 8:54:40 AM E Disk Driver : Cannot Read Device 80070006 Block 32960 Disk FFFFFFFF 12/3/2008 8:54:40 AM E File System Check : Cannot Read: Blk 32960 Disk (Priv) 12/3/2008 8:54:32 AM E Disk Driver : Cannot Read Device 80070006 Block 32960 Disk FFFFFFFF 12/3/2008 8:54:32 AM It only seems to be logging the last 50 lines, everything prior to that gets removed when the log updates. The following is the slightly more detailed info I get when doing an "info log t", and it repeats over and over also. 12/03/2008 8:38:57 37 E L00 \| File System Check : Cannot Read: Blk 32960 12/03/2008 8:39:01 37 D SYS \| DISK: req=0x428AAC dev=0xC0000 fn=1 blk=0xA0F0 sts=20 12/03/2008 8:39:05 37 D SYS \| DISK: req=0x428AAC dev=0xC0000 fn=1 blk=0xA0F0 sts=20 12/03/2008 8:39:05 37 D SYS \| DISK: req=0x428AAC dev=0x80000 fn=1 blk=0xA0F0 sts=20 12/03/2008 8:39:05 37 E D[80070006] \| Disk Driver : Cannot Read Device 80070006 Block 32960 12/03/2008 8:39:05 37 E L00 \| File System Check : Cannot Read: Blk 32960 12/03/2008 8:39:09 37 D SYS \| DISK: req=0x428AAC dev=0xC0000 fn=1 blk=0xA0F0 sts=20 12/03/2008 8:39:13 37 D SYS \| DISK: req=0x428AAC dev=0xC0000 fn=1 blk=0xA0F0 sts=20 12/03/2008 8:39:13 37 D SYS \| DISK: req=0x428AAC dev=0x80000 fn=1 blk=0xA0F0 sts=20 12/03/2008 8:39:13 37 E D[80070006] \| Disk Driver : Cannot Read Device 80070006 Block 32960 "info dev" shows this: Logical Device: 10006 Position: 0 JBOD Size (KB): 32768 Free (KB): 0 Private Unmounted Label:Private Contains system files only Unique Id: 0x07E172C1151F56A0 Mount: /priv Index: 12 Order: 255 Partition: 10006 Physical: 10007 FS Size (KB): 32768 Starting Blk: 515 Private Physical: 10007 Drive Slot: 0 IDE Size (KB): 134217216 Fixed Logical Device: 1000E Position: 0 JBOD Size (KB): 32768 Free (KB): 0 Private Unmounted Label:Private Contains system files only Unique Id: 0x5DE062EE74C7D817 Mount: /pri2 Index: 13 Order: 255 Partition: 1000E Physical: 1000F FS Size (KB): 32768 Starting Blk: 515 Private Physical: 1000F Drive Slot: 1 IDE Size (KB): 134217216 Fixed Logical Device: 60000 Position: 1 RAID Size (KB): 400329600 Free (KB): 0 Public Unmounted Label:RAID5 Large data protection disk Unique Id: 0x343BC2672C5DC315 Mount: /0 Index: 0 Order: 255 Partition: 10000 Physical: 10007 R 60000 Size (KB): 133443200 Starting Blk: 96624 Public Physical: 10007 Drive Slot: 0 IDE Size (KB): 134217216 Fixed Partition: 10008 Physical: 1000F R 60000 Size (KB): 133443200 Starting Blk: 96624 Public Physical: 1000F Drive Slot: 1 IDE Size (KB): 134217216 Fixed Partition: 10010 Physical: 10017 R 60000 Size (KB): 133443200 Starting Blk: 96624 Public Physical: 10017 Drive Slot: 2 IDE Size (KB): 134217216 Fixed Partition: 10018 Physical: 1001F R 60000 Size (KB): 133443200 Starting Blk: 96624 Public Physical: 1001F Drive Slot: 3 IDE Size (KB): 134217216 Fixed And when I do an "info log p" I get this bit of wisdom: Sorry, the 'Private Partition' does not exist, so no 'Permanent Log' can be stored. HINT: If you reformat the first drive, the private partition will be created. At the moment I'm mulling my options. I can do as it suggests and try reformatting Disk 1 (drive slot 0), or I can open it up and pull the power and data cable for the disk and see if it'll come up in degraded mode. Any suggestions? Any ideas on if there's a command I can issue to tell it to ignore disk 1 and come up using the other disks? Or to use the redundant info on the 'Private Partition' on Disk 2 (drive slot 1)?