Skip to main content

Accidental Reboot / Shutdown Causes Errors In The Hard Drive

I accidentally pressed the hardware reset because it's too close to the headphone jacks. I've got big fingers what can I say. So it's a couple of seconds later that I noticed that the computer (the monitor) has restarted. Except that the initial restart sequence is throwing me to a console with a bad ata status:DRDY message. I've seen this before. It's a bad shutdown for one or more of the hard drives / raid device.
I checked the status of the RAID device and confirmed it. I've got an inactive array. So I issued:

#mdadm /dev/md0 --stop

to stop the array and restart it with:

#mdadm --assemble /dev/md0 /dev/sdb1 /dev/sdc1 /dev/sdd1

but no go, so again i tried this:

#mdadm --assemble --force /dev/md0 /dev/sdb1 /dev/sdc1 /dev/sdd1

I check the status of the array after I started it.

#mdadm --detail /dev/md0

root@desktop:~# mdadm --detail /dev/md0
/dev/md0:
        Version : 1.2
  Creation Time : Tue Sep  6 02:59:21 2016
     Raid Level : raid5
     Array Size : 1953260544 (1862.77 GiB 2000.14 GB)
  Used Dev Size : 976630272 (931.39 GiB 1000.07 GB)
   Raid Devices : 3
  Total Devices : 2
    Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Sun Dec  4 22:59:12 2016
          State : clean, degraded
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 512K

           Name : desktop:0  (local to host desktop)
           UUID : e3284314:1258cac3:1b6c243c:748be2fe
         Events : 2849

    Number   Major   Minor   RaidDevice State
       0       8       17        0      active sync   /dev/sdb1
       1       8       33        1      active sync   /dev/sdc1
       4       0        0        4      removed

One of the devices comprising this array is removed. Maybe due to corrupt data or something else. I figured i could do more if I reboot with this degraded array into my desktop. So I did. I used the Gnome SMART checker (it's what I call it). Refreshed the status and the devices checks out.

So figuring out that the device is not really bad (according to SMART). I added it back to the array with:

#mdadm --manage --add /dev/md0 /dev/sdd1

I checked the status of the array with:

#mdadm --detail /dev/md0

/dev/md0:
        Version : 1.2
  Creation Time : Tue Sep  6 02:59:21 2016
     Raid Level : raid5
     Array Size : 1953260544 (1862.77 GiB 2000.14 GB)
  Used Dev Size : 976630272 (931.39 GiB 1000.07 GB)
   Raid Devices : 3
  Total Devices : 3
    Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Sun Dec  4 23:11:48 2016
          State : clean, degraded, recovering
 Active Devices : 2
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 1

         Layout : left-symmetric
     Chunk Size : 512K

 Rebuild Status : 4% complete

           Name : desktop:0  (local to host desktop)
           UUID : e3284314:1258cac3:1b6c243c:748be2fe
         Events : 2853

    Number   Major   Minor   RaidDevice State
       0       8       17        0      active sync   /dev/sdb1
       1       8       33        1      active sync   /dev/sdc1
       3       8       49        2      spare rebuilding   /dev/sdd1

All I have to do now is wait for it to rebuild the device back to the array.

/dev/md0:
        Version : 1.2
  Creation Time : Tue Sep  6 02:59:21 2016
     Raid Level : raid5
     Array Size : 1953260544 (1862.77 GiB 2000.14 GB)
  Used Dev Size : 976630272 (931.39 GiB 1000.07 GB)
   Raid Devices : 3
  Total Devices : 3
    Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Sun Dec  4 23:14:22 2016
          State : clean
 Active Devices : 3
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 512K

           Name : desktop:0  (local to host desktop)
           UUID : e3284314:1258cac3:1b6c243c:748be2fe
         Events : 2890

    Number   Major   Minor   RaidDevice State
       0       8       17        0      active sync   /dev/sdb1
       1       8       33        1      active sync   /dev/sdc1
       3       8       49        2      active sync   /dev/sdd1

It took just 10 minutes.

Comments

Post a Comment

Popular posts from this blog

Password Issues On Ubuntu Login

I found myself unable to enter my login credentials when prompted to do so in Ubuntu. I think I might have changed it then forget about it. I've been running the current session for more days than I should have. I forget. So what's the solution to my problem. How do I get in to my system now? It involved getting into the grub menu somehow. I am uncertain as to how to do that exactly in your system. So there's a couple of ways to do it (finger's crossed). When booting at system start, use the esc key or the shift key. The first one worked for me. The timing is key. Wait until the bios banner shows then hit the esc key once. I am using Ubuntu 22.04.4 here. I have a current version of grub. The grub menu will give you options and the one you want is: root. Yes you want root privileges to set the root password. It should give you a terminal access where you can issue commands. Type: #mount -rw -o -s remount / ==> this command mounts the filesyste...
Post a Comment
Read more

Pacman Has to Get Better

I finally got my printers working. I got cups (and cupsd in the /etc/rc.conf) I installed hpoj and a group of printer drivers. So to get my Arch linux to recognize there's a usb printer connected to my system I have to run a daemon (ptal-init setup) and include it in /etc/rc.conf. That finally enabled (after a reboot) my GNOME control center to acknowledge that there is indeed an HP-3900 at the end of my usb port. The real personal story behind my saga with a printer is pacman. It is now throwing 'network not reachable' everytime I start it. Every download and sync. I ran --debug and ping ip addresses and so far I will conclude that it's a really really slow ftp server. The server is so slow pacman is timing out connections. It's unusable guys. My first rolling release distro and I've decided that Arch rises and falls with the performance of their package manager. Great distro for the DIY community. But sorry I can't recommend Arch linux to my mother who jus...
Post a Comment
Read more

Webapps in Unity

So it has been 4 months since Ubuntu 14.04 came out. This is LTS and supported for 6 years by Canonical. The first mobile device with Ubuntu pre-installed is promised to come out later this year, 2014. It's time to check out how the apps perform so far. It is a good idea. I use Gmail and Twitter and Facebook. Why not a webapp in a desktop? So I start the Twitter and Gmail webapp. So far it has crashed my computer 6 times. Not a very good sign. On the other hand it does work but not as stable as opening them in Firefox. -- Use my PGP key if you want to encrypt your replies/messages to me. You are invited to also send me your PGP keys so we can communicate in private.
Post a Comment
Read more