Jump to content


Photo

HDD failure

Vu+Duo

  • Please log in to reply
32 replies to this topic

Re: HDD failure #21 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+542
Excellent

Posted 5 January 2013 - 10:05

Yes indeed, you will need to "swapoff" that file as well.

* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: HDD failure #22 krister67

  • Senior Member
  • 92 posts

0
Neutral

Posted 5 January 2013 - 10:10

Yes indeed, you will need to "swapoff" that file as well.


Yeah, of course it´s the swapfile creating the "Device busy" :wacko:
Turned it off and now I´m running e2fsck.... :P

Re: HDD failure #23 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 5 January 2013 - 10:19

Try this: fuser -mk /hdd (or wherever you mounted your harddisk). This may kill important processes, so you may need to reboot afterwards.

I have no swap-file, and still get the device busy.
And 'fuser -mk /dev/sda1' restarts E2. Did I use a wrong command?

Re: HDD failure #24 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 5 January 2013 - 10:22


Try this: fuser -mk /hdd (or wherever you mounted your harddisk). This may kill important processes, so you may need to reboot afterwards.

I have no swap-file, and still get the device busy.
And 'fuser -mk /dev/sda1' restarts E2. Did I use a wrong command?

Grrrhhhhh, I had PTS active......... Check running now.

Re: HDD failure #25 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+542
Excellent

Posted 5 January 2013 - 10:33

Also I suggested to do a init "4" first, which stops enigma anyway.

* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: HDD failure #26 krister67

  • Senior Member
  • 92 posts

0
Neutral

Posted 5 January 2013 - 10:51

Also I suggested to do a init "4" first, which stops enigma anyway.


I did "init 4" before unmounting the drive.
Here are the result of the scan:

root@vuduo:~# e2fsck -f -v /dev/sda1
e2fsck 1.42 (29-Nov-2011)
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 390 has zero dtime. Fix<y>? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(230400--230407) -(230412--230419) -(230424--230432) -(230434--230436) -(230438--230440) -(230442--230444) -(230446--230448) -(230450--230452) -(230454--230457) -(230459--2
30461) -230463 -(230465--230467) -(230469--230471) -(230473--230475) -(230477--230484) -(230518--230529) -(230531--230533) -(230535--230537) -(230539--230541) -(230543--230545) -(230547--230552) -(230
554--230557) -230559 -(230562--230575) -(230577--230579) -(230581--230583) -(230585--230587) -(230589--230592) -(230594--230596) -(230598--230601) -(230603--230605) -(230607--230609) -(230611--230613)
-(230615--230617) -(230619--230621) -(230623--230625) -(230627--230629) -(230631--230633) -(230635--230638) -(230640--230642) -(230644--230646) -(230648--230650) -230652 -(230912--230914) -230916 -(2
30924--230927) -(230930--230945) -(230947--230949) -(230951--230953) -(230955--230957) -(230959--230961) -(230963--230965) -(230967--230969) -(230971--230973) -230975 -(231232--231234) -(231237--23123
9) -(231241--231246) -(231252--231254) -(231256--231258) -(231260--231266) -(231268--231270) -(231272--231274) -(231276--231278) -(231280--231282) -(231284--231286) -(231288--231290) -(231292--231294)
-(231425--231428) -(231430--231432) -(231434--231436) -(231438--231440) -(231442--231444) -(231446--231447) -231468 -(231470--231472) -(231474--231476) -(231478--231480) -(231482--231484) -(231486--2
31489) -(231491--231506) -(231937--231939) -(231941--231943) -(231945--231947) -(231949--231951) -(231953--231955) -(231957--231959) -(231961--231963) -231965 -(231982--231983) -(231985--231988) -(231
990--231992) -(231994--231996) -(231998--231999) -234008 -(234025--234026) -(234028--234030) -(260953--260956) -(260958--260960) -(260962--260964) -(260966--260968) -(260970--260972) -(260974--260976)
-(260978--260980) -(260982--260984) -(260986--260988) -(260990--260991) -(8749168--8749183) -(8749472--8749535) -(8750720--8750975) -(8753152--8759295) -(8761344--8765439) -(8765472--8765503) -(87655
68--8765695) -(8765952--8767487) -(8769536--8775679) -(8779776--8781823) -(8783872--8787967) -(8790016--8794111) -(8796160--8798207) -(8800256--8808447) -(8810496--8814591) -(8818688--8822783) -(88248
32--8830975) -(8833024--8835071) -(8837120--8841215) -(8843264--8847359) -(8849408--8853503) -(8855552--8857599) -(8859648--8867839) -(8869888--8876031) -(8882176--8886271) -(8890368--8896511) -(89006
08--8904703) -(8906752--8908799) -(8910848--8912895) -(8916992--8919039) -(8921088--8927231) -(8929280--8931327) -(8933376--8935423) -(8941568--8945663) -(8947712--8949759) -(8953856--8959999) -(89620
48--8964095) -(8966144--8968191) -(8972288--8974335) -(8984576--8986623) -(8992768--8994815) -(9000960--9003007) -(9013248--9015295) -(9019392--9021439) -(9029632--9031679) -(9037824--9039871) -(90501
12--9052159) -(9054208--9056255) -(9070592--9072639) -(9074688--9076735) -(9086976--9089023) -(9095168--9097215) -(9105408--9107455) -(9111552--9115647) -(9127936--9132031) -(9144320--9146367) -(91566
08--9158655) -(9170944--9172991) -(9177088--9179135) -(9195520--9197567) -(9205760--9207807) -(9209856--9211903) -(9224192--9226239) -(9230336--9232383) -(9238528--9240575) -(9603072--9605119) -(96071
68--9611263) -(9617408--9621503) -(9625600--9627647) -(9631744--9633791) -(9635840--9637887) -(9639936--9644031) -(9652224--9658367) -(9660416--9664511) -(9670656--9672703) -(9678848--9680895) -(96870
40--9689087) -(9697280--9699327) -(9701376--9703423) -(9707520--9709567) -(9711616--9717759) -(9721856--9723903) -(9730048--9732095) -(9734144--9738239) -(9740288--9744383) -(9756672--9758719) -(97628
16--9764863) -(9766912--9768959) -(9773056--9775103) -(9783296--9785343) -(9789440--9791487) -(9795584--9797631) -(9805824--9807871) -(9809920--9811967) -(9816064--9818111) -(9820160--9822207) -(98365
44--9838591) -(9840640--9842687) -(9846784--9848831) -(9854976--9857023) -(9861120--9863167) -(9869312--9871359) -(9875456--9877503) -(9879552--9881599) -(9883648--9885695) -(9900032--9902079) -(99061
76--9908223) -(9910272--9912319) -(9926656--9928703) -(9932800--9934847) -(9936896--9938943) -(9949184--9951231) -(9965568--9967615) -(9969664--9971711) -(9979904--9981951) -(9986048--9988095) -(99901
44--9992191) -(10006528--10008575) -(10012672--10014719) -(10016768--10018815) -(10024960--10027007) -(10033152--10035199) -(10039296--10041343) -(10049536--10051583) -(10053632--10055679) -(10063872-
-10065919) -(10074112--10076159) -(10078208--10080255) -(10088448--10090495) -(10094592--10096639) -(10102784--10104831) -(10108928--10110975) -(10113024--10115071) -(10123264--10125311) -(10129408--1
0131455) -(10135552--10137599) -(10141696--10143743) -(10145792--10147839) -(10156032--10158079) -(10168320--10170367) -(10172416--10174463) -(10176512--10178559) -(10186752--10188799) -(10192896--101
94943) -(10196992--10199039) -(10207232--10209279) -(10211328--10213375)
Fix<y>? yes

Free blocks count wrong for group #7 (40, counted=427).
Fix<y>? yes
Free blocks count wrong for group #267 (2058, counted=22522).
Fix<y>? yes
Free blocks count wrong for group #268 (2026, counted=24554).
Fix<y>? yes
Free blocks count wrong for group #269 (2042, counted=22522).
Fix<y>? yes
Free blocks count wrong for group #270 (2010, counted=22490).
Fix<y>? yes
Free blocks count wrong for group #271 (2042, counted=20474).
Fix<y>? yes
Free blocks count wrong for group #272 (2042, counted=18426).
Fix<y>? yes
Free blocks count wrong for group #273 (1994, counted=16330).
Fix<y>? yes
Free blocks count wrong for group #274 (2042, counted=8186).
Fix<y>? yes
Free blocks count wrong for group #275 (2042, counted=10234).
Fix<y>? yes
Free blocks count wrong for group #276 (2026, counted=10218).
Fix<y>? yes
Free blocks count wrong for group #277 (2042, counted=8186).
Fix<y>? yes
Free blocks count wrong for group #278 (2042, counted=10234).
Fix<y>? yes
Free blocks count wrong for group #279 (2010, counted=8154).
Fix<y>? yes
Free blocks count wrong for group #280 (2042, counted=8186).
Fix<y>? yes
Free blocks count wrong for group #281 (2042, counted=10234).
Fix<y>? yes
Free blocks count wrong for group #293 (5109, counted=19445).
Fix<y>? yes
Free blocks count wrong for group #294 (2042, counted=18426).
Fix<y>? yes
Free blocks count wrong for group #295 (3061, counted=11253).
Fix<y>? yes
Free blocks count wrong for group #296 (2042, counted=16378).
Fix<y>? yes
Free blocks count wrong for group #297 (5535, counted=17823).
Fix<y>? yes
Free blocks count wrong for group #298 (1914, counted=12154).
Fix<y>? yes
Free blocks count wrong for group #299 (3061, counted=11253).
Fix<y>? yes
Free blocks count wrong for group #300 (2042, counted=12282).
Fix<y>? yes
Free blocks count wrong for group #301 (3061, counted=11253).
Fix<y>? yes
Free blocks count wrong for group #302 (2042, counted=10234).
Fix<y>? yes
Free blocks count wrong for group #303 (3061, counted=9205).
Fix<y>? yes
Free blocks count wrong for group #304 (2042, counted=12282).
Fix<y>? yes
Free blocks count wrong for group #305 (3061, counted=11253).
Fix<y>? yes
Free blocks count wrong for group #306 (2042, counted=10234).
Fix<y>? yes
Free blocks count wrong for group #307 (5109, counted=13301).
Fix<y>? yes
Free blocks count wrong for group #308 (2042, counted=12282).
Fix<y>? yes
Free blocks count wrong for group #309 (5109, counted=15349).
Fix<y>? yes
Free blocks count wrong for group #310 (1786, counted=9978).
Fix<y>? yes
Free blocks count wrong for group #311 (3061, counted=11253).
Fix<y>? yes
Free blocks count wrong (32235860, counted=32615111).
Fix<y>? yes
Inode bitmap differences: -390
Fix<y>? yes
Free inodes count wrong for group #3 (120, counted=121).
Fix<y>? yes
Free inodes count wrong (952435, counted=952436).
Fix<y>? yes

/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
1548 inodes used (0.16%)
255 non-contiguous files (16.5%)
7 non-contiguous directories (0.5%)
# of inodes with ind/dind/tind blocks: 344/155/63
211574897 blocks used (86.64%)
0 bad blocks
98 large files
1485 regular files
51 directories
0 character device files
0 block device files
0 fifos
0 links
3 symbolic links (3 fast symbolic links)
0 sockets
--------
1539 files
root@vuduo:~#


No serious issues I persume?

Re: HDD failure #27 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+542
Excellent

Posted 5 January 2013 - 11:00

This means the consistency of the filesystem is fine now, there won't come any NEW file corruptions (unless another problem comes up). It also means that existing files may very well still be corrupt (in the sense that they may contain invalid or missing data). I think you'd best check all files you rely on.

* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: HDD failure #28 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 5 January 2013 - 11:50

Also I suggested to do a init "4" first, which stops enigma anyway.

Yes, I know, but if PTS was active this still gives the device busy report. So I have to stop PTS, reboot the box, and then the init 4/unmount/check sequence.

Re: HDD failure #29 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+542
Excellent

Posted 5 January 2013 - 12:11

AFAIK pts is implemented as plugin in enigma?!

* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: HDD failure #30 krister67

  • Senior Member
  • 92 posts

0
Neutral

Posted 5 January 2013 - 14:38


Also I suggested to do a init "4" first, which stops enigma anyway.

Yes, I know, but if PTS was active this still gives the device busy report. So I have to stop PTS, reboot the box, and then the init 4/unmount/check sequence.


If you put the box in "standby" you don´t have to stop PTS, "init 4" will do fine.
Also remember to turn off any swapfile using the device.

This is how I did it, (I´m also running PTS)
init 4
swapoff -a
umount /dev/sda1
e2fsck -f -v /dev/sda1


Re: HDD failure #31 krister67

  • Senior Member
  • 92 posts

0
Neutral

Posted 6 January 2013 - 11:28

This means the consistency of the filesystem is fine now, there won't come any NEW file corruptions (unless another problem comes up). It also means that existing files may very well still be corrupt (in the sense that they may contain invalid or missing data). I think you'd best check all files you rely on.


So "e2fsck -f -v" isn´t enough?
What other switches should I use with e2fsck to check all files?

Re: HDD failure #32 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+542
Excellent

Posted 6 January 2013 - 12:53

e2fsck checks and repairs the consistency of the file system. It can never know what's supposed to be in the files...

That's why I urge users to never switch of their box without properly shutting it down. Although ext3 and ext4 are journalled file systems, which mean they are a lot more robust against sudden power-offs, they can also fail.

* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: HDD failure #33 krister67

  • Senior Member
  • 92 posts

0
Neutral

Posted 6 January 2013 - 17:46

e2fsck checks and repairs the consistency of the file system. It can never know what's supposed to be in the files...

That's why I urge users to never switch of their box without properly shutting it down. Although ext3 and ext4 are journalled file systems, which mean they are a lot more robust against sudden power-offs, they can also fail.


Okay, I see.

Well, the drive are working perfect now, I hope it stays so for a long time :P

Thanks for all help Erik! :)



Also tagged with one or more of these keywords: Vu+Duo

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users