[17:29] <nixnine> Hey guys, need help.  Trying to log into studio 14.04 but I get an error at start up about busybox and initramfs
[17:29] <nixnine> Can someone help?
[17:30] <holstein> nixnine: sounds like that could be any error from hardware failing to corrupt filesystem.. or kernel panic..
[17:30] <nixnine> that bad?
[17:30] <holstein> nixnine: i would isolate and test.. run the memtest from a live CD.. test the hard drive.. and "repair" if possible..
[17:31] <nixnine> how do i do that?
[17:31] <holstein> nixnine: then, i would run a live CD and see how the desktop responds. see if the hardware seems good.. GPU and CPU and all that.. listening for fans, etc
[17:31] <holstein> nixnine: from the live CD, there are tests
[17:31] <holstein> https://help.ubuntu.com/community/MemoryTest
[17:32] <holstein> http://askubuntu.com/questions/317241/can-i-use-ubuntu-to-diagnose-hard-drive-or-ram-problems-in-windows
[17:33] <nixnine> running from external hd now
[17:33] <holstein> nixnine: you are running what from what?
[17:33] <nixnine> I have booted into another system
[17:33] <holstein> you mean, you are booting an OS that is located on a different hard drive?
[17:33] <nixnine> yes
[17:34] <holstein> then, as i suggested, the hard drive can be bad or failing
[17:34] <nixnine> can I check like that?
[17:34] <holstein> nixnine: i use "gsmartcontrol" to test the hard drive
[17:34] <nixnine> don't have that
[17:35] <holstein> i typically run the short self-test, then, i'll run the long one.. i spend literally hours testing each drive
[17:35] <holstein> nixnine: i would install a tool, as the one i suggested, which will  allow you to test the drive
[17:35] <holstein> !info gsmartcontrol
[17:36] <nixnine> reading something about superblock
[17:36] <nixnine> what is that?
[17:37] <holstein> http://www.linfo.org/superblock
[17:37] <nixnine> http://askubuntu.com/questions/137655/boot-drops-to-a-initramfs-prompts-busybox?answertab=votes#tab-top
[17:37] <holstein> A superblock is a record of the characteristics of a filesystem, including its size, the block size, the empty and the filled blocks and their respective counts, the size and location of the inode tables, the disk block map and usage information, and the size of the block groups.
[17:37] <nixnine> could that page work?
[17:37] <holstein> nixnine: i would "repair" the filesystem after first testing and backing up any data i can locate that i need
[17:38] <nixnine> so what should I do first?
[17:38] <holstein> nixnine: ?
[17:38] <holstein> nixnine: friend, i would test my hard ware
[17:38] <holstein> nixnine: i use the tools i outlined above to do so
[17:39] <nixnine> ok.  let me see
[17:39] <holstein> nixnine: i would have backups before proceeding. and if i could access the drive from a live CD, i would make copies of data *first*
[17:39] <holstein> then, i would test.. i would read reports, and go from there
[17:39] <holstein> i wouldnt be interested in repairing the filesystem on a drive that is failing.. i would use my time to replace the hardware
[17:40] <nixnine> ok
[17:41] <holstein> if the drive reports that its doing well, i would then repair the file system
[17:41] <holstein> http://www.maketecheasier.com/check-repair-filesystem-fsck-linux/ for example
[17:41] <holstein> if you want to skip that step, and just fsck the drive, you can. but, you should try and recover any data *first*
[17:42] <holstein> if you have no data, or proper backups,then, you can either test or recover..
[17:42] <holstein> for me, even if the filesystem repair works, i want to test the drive and make sure its physically not failing or bad
[17:42] <nixnine> checking through disk utility.  already installed.  Say warning on reallocated sector count
[17:43] <holstein> right..
[17:43] <holstein> so, you can count those up and read the reports..
[17:43] <nixnine> non repairable?
[17:43] <holstein> nixnine: i would have to see your data..
[17:43] <nixnine> says 569 bad sectors
[17:43] <holstein> yeah.. thats not good
[17:44] <nixnine> but the overall assessment says good.  Just that disk has a few bad sectors
[17:44] <holstein> so, you know where the problem is
[17:44] <holstein> nixnine: 500+ is not "a few"
[17:44] <nixnine> So that's the hard drive going bad
[17:45] <nixnine> few is how it states it
[17:45] <holstein> nixnine: you have reported bad sectors.. that can cause data loss, and that data loss can cause the errors you are seeing
[17:45] <nixnine> can't be repaired?
[17:45] <holstein> nixnine: its up to you to research and parse the data
[17:45] <holstein> nixnine: the physical drive cannot be repaired.. no
[17:46] <holstein> nixnine: you can run the filesystem repairs i linked above
[17:46] <holstein> *after* recovering any data from the drive, i might try that, and run a long test.. the test i run takes hours. and is more thorough
[17:46] <holstein> i run the long test from gsmartcontrol...
[17:46] <holstein> but, i dont trust drives like that.. and that *is* what is causing your issue
[17:47] <holstein> at a different time, when drives were more expensive, i would try and partition around where i thought the broken parts were.. but, it was always a temporary fix that i didnt trust
[17:49] <holstein> you'd think i get a kick-back from seagate or something ;)
[20:20] <piero> hi
[20:20] <piero> my X is bug
[20:20] <piero> help me