Can't find ext3 filesystem on B2 hard drive

[Moloko]

Hi all,

The other day the blue LED on my BubbaTwo was constantly blinking. I restarted it, same blinking and I also noticed Bubba was not accessible via web page. I attached the Bubba hard drive to a Ubuntu computer via SATA cable, and tried to mount the hard drive in Ubuntu.

Checking

Code: Select all

dmesg|tail

gave the error messages as seen below.

The disk is currently mounted to the Ubuntu computer and readable. I have copied everything from the /home area to another hard drive.


Now my question is:
How reliable is the Bubbas hard drive that failed, if I use it for every 24/7/365 operation?
Can reformat it and use it again in BubbaTwo? Will it fail me again?
Or should I throw it away, buying a new hard drive, just to play safe??

Code: Select all

EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: sda1: orphan cleanup on readonly fs
ext3_orphan_cleanup: deleting unreferenced inode 848653
ext3_orphan_cleanup: deleting unreferenced inode 848649
ext3_orphan_cleanup: deleting unreferenced inode 656422
ext3_orphan_cleanup: deleting unreferenced inode 655087
ext3_orphan_cleanup: deleting unreferenced inode 848652
ext3_orphan_cleanup: deleting unreferenced inode 848650
ext3_orphan_cleanup: deleting unreferenced inode 848648
ext3_orphan_cleanup: deleting unreferenced inode 848647
ext3_orphan_cleanup: deleting unreferenced inode 848646
ext3_orphan_cleanup: deleting unreferenced inode 848645
ext3_orphan_cleanup: deleting unreferenced inode 848644
EXT3-fs: sda1: 11 orphan inodes deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 168k init
Adding 1156672k swap on /dev/sda3.  Priority:-1 extents:1 across:1156672k
EXT3 FS on sda1, internal journal
fuse init (API version 7.9)
kjournald starting.  Commit interval 5 seconds
EXT3 FS on dm-0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.



sd 5:0:0:0: [sdb] Assuming drive cache: write through
 sdb: sdb1 sdb2
sd 5:0:0:0: [sdb] Attached SCSI disk
sd 5:0:0:0: Attached scsi generic sg1 type 0
usb-storage: device scan complete
kjournald starting.  Commit interval 5 seconds EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Can't find ext3 filesystem on dev sdb2.

[tor]

Hi Moloko,

The most likely reason that you don't find any ext3 filesystem on your /dev/sdb2 is that we use LVM out of the box for Bubba.

You should install the lvm2 tools for ubuntu and then you should be able to access the home partition by manually mounting /dev/bubba/storage

/Tor

[Moloko]

The problem is not that I could find the file system, the problem is that Bubba itself couldn't find its own file system!

I am worried, as you can understand...


My question is:
How reliable is the Bubbas hard drive that failed, if I contine to use it for 24/7/365 operation?

Can reformat it and use it again in BubbaTwo?
Will it fail me again?

Or should I throw it away, buying a new hard drive, just to play safe??