![]() | ||
|
|
Snap Server / NAS / Storage Technical Goodies The Home for Snap Server Hacking, Storage and NAS info. And NAS / Snap Classifides |
![]() |
Thread Tools |
![]() |
#1 |
Cooling Neophyte
Join Date: Mar 2010
Location: NJ
Posts: 4
|
![]()
I had a drive seem like it has failed. These drives are now configured as JBOD in my Snap 4100 running 3.4.790. To try and remedy the problem, I ran a disk check. Well, that disk check has been going on for days now with no way to stop it. It is stuck at 5%. When trying to restart the server it won't let me, saying that a disk operation is occurring and that it can't be done now. Power off would give the same error. I also tried to hold down the power button, and that did not work. I was forced to disconnect the power. When I turned it back on, the disk check automatically started again, and is stuck at 5% again.
I'm not too concerned with the data , as it was just install files we use that can be downloaded again (although it would be nice to get it back). Should I just remove the drive, or can I submit some kind of debug command to stop the disk check? |
![]() |
![]() |
![]() |
#2 |
Cooling Savant
Join Date: Apr 2006
Location: Tennessee
Posts: 157
|
![]()
Do you see any of the disk LEDs flash occasionally on the front of the unit? Any of them flashing amber? How big are the hard drives?
I had a Snap 4100 with four 160GB hard drives in it take a week to run the disk check. Can you do an "info log t" from the command line? If you can, and are seeing stuff like: 12/04/2008 7:14:21 37 D SYS | DISK: req=0xDC1A88 dev=0xC0000 fn=1 blk=0x2504620 sts=19 12/04/2008 7:14:21 37 D SYS | DISK: req=0xDC1A88 dev=0x80000 fn=1 blk=0x2504620 sts=19 12/04/2008 7:14:25 37 D SYS | DISK: req=0xDC2758 dev=0xC0000 fn=1 blk=0x2506990 sts=19 12/04/2008 7:14:30 37 D SYS | DISK: req=0xDC2758 dev=0xC0000 fn=1 blk=0x2506990 sts=19 12/04/2008 7:14:30 37 D SYS | DISK: req=0xDC2758 dev=0x80000 fn=1 blk=0x2506990 sts=19 Where the block numbers keep changing over time then you may be in the same boat I was. In that case you'll just need to sit back and wait for it to complete because there's no way to get around it. It will continue to say 5% until it finishes. |
![]() |
![]() |
![]() |
#3 |
Cooling Neophyte
Join Date: Mar 2010
Location: NJ
Posts: 4
|
![]()
The disks are 60 GB. I've run a disk check before, and it took a long time, and the percentage complete was never very accurate.
I'm seeing similar things in the log, but I see the following in the log repeated over and over: 03/23/2010 14:57:06 104 E D[80070000] | Disk Driver : Cannot Read Device 80070000 Block 48448384 03/23/2010 14:57:06 104 E L01 | File System Check : Cannot Read: Blk 48448384 03/23/2010 14:57:17 104 D SYS | DISK: req=0x3F741C dev=0xC0000 fn=1 blk=0x2F18E30 sts=20 03/23/2010 14:57:22 104 D SYS | DISK: req=0x3F741C dev=0xC0000 fn=1 blk=0x2F18E30 sts=20 03/23/2010 14:57:22 104 D SYS | DISK: req=0x3F741C dev=0x80000 fn=1 blk=0x2F18E30 sts=20 The front LEDs all show green when lit. I see the Disk 1 LED flash green every once in a while when I do look at it. One thing that might be affecting this is when I ran the disk check, I didn't choose the destructive option. I ran one of the other disk checks that don't attempt to repair all errors. It seems that it keeps on getting to this bad block and instead of fixing it or marking it as bad and moving on, it just keeps trying over and over from what I can tell. |
![]() |
![]() |
![]() |
#4 |
Cooling Savant
Join Date: Apr 2006
Location: Tennessee
Posts: 157
|
![]()
If the block numbers never change, then I'd say it looks bad. The non-destructive repair options should normally just give you an error message and move on. I would expect the Repair All Errors option would give you the same as what you're seeing now. If it can't read the block, then it can't repair it either.
I've never tried my 4100 as a JBOD. When it's configured this way, does it come up as four individual drives, or does it span the drives and display it as a single drive? If you were seeing it as four individual drives, then you could try disconnecting each drive one at a time to see if you can nail down which one is causing the error. It's your call as to what to do next. We have a few resident experts that can give you better advice than I. |
![]() |
![]() |
![]() |
#5 |
Cooling Neophyte
Join Date: Mar 2010
Location: NJ
Posts: 4
|
![]()
All four drives are listed. I actually know which disk is the problem, so I could remove it.
To give some history, I had separated the drives from a mirror RAID config with two drives/shares available. I saw some problems, so I broke down RAID and made it JBOD. That was a few weeks ago. The drive showed it was available when I first started seeing the problem, and it didn't show any errors in the SnapOS log, but I couldn't explore the drive from Windows. Other drives worked fine. That's when I decided to run the disk check. What file system does the SnapOS use? I'm thinking about removing the drive and see if I can get to some of the files by connecting it to a USB drive dongle that has an IDE connector. |
![]() |
![]() |
![]() |
#6 |
Cooling Savant
Join Date: Apr 2006
Location: Tennessee
Posts: 157
|
![]() |
![]() |
![]() |
![]() |
#7 |
Thermophile
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
|
![]()
If it's hanging in the 5% area, this is where the inodes and super blocks are. This is where the HD's will fail. Some have left the units up and it took over 10 day if I recall to finish the check. SnapOS is an modified bsd file system, nothing reads these except another snap or recovery service.
Also read the FAQ's on 4100's MB patch/fix. If your was an original 160 (4x40gig) from snap it was/should have the mod or a rev3+ to correct the problem. If it was upgraded at a later date the low capacity units were not patched because the problem only showed up on the higher cap models.
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820 |
![]() |
![]() |
![]() |
#8 |
Cooling Neophyte
Join Date: Mar 2010
Location: NJ
Posts: 4
|
![]()
Thanks everyone for the help. I'm going to let it finish the disk check. With the weekend coming up and the several days it has already been running, hopefully by next week it will have completed.
blue68f100, I went looking through the FAQ for the fix you mentioned, but I could not find it. Do you have a link to it? Mine is a 240 GB model. |
![]() |
![]() |
![]() |
#9 | |
Cooling Savant
Join Date: Apr 2006
Location: Tennessee
Posts: 157
|
![]() Quote:
|
|
![]() |
![]() |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|