Hello all, I have some problems with my workstation, I got a Dell Precision 390 with Core2Duo 2.4GHz and 4GB DDR2 ECC, 2x 1TB drives in fake-raid 1. A few days ago I made an upgrade and after that my system is not booting up. I started a thread on Google+ but with no luck untill now. Some users said that was some hardware issue, but I tested the ram with 3 different programs and no errors. I was able to boot the 12.3 dvd into the Rescue mode but my drives are mounted like this
/parts/mp_0000
/parts/mp_0001
/mounts/mp_0000
/mounts/mp_0001
/mounts/mp_0002
A user suggested to blacklist the edac_core module in order to bypass the kernel bug, but the drives are mounted read only
mount -o remount,rw / = mount.bin: / notmounted or bad option
and
mount -o remount,rw /mounts/mp_0000 = mount.bin cannot remount /dev/loop2 read-write, is write protected
I dont know what to do right now, and I don’t want to lost all my data
The link to the G+ thread is:](https://plus.google.com/109294183351259381678/posts/2dmYUKPXQjt)https://plus.google.com/109294183351259381678/posts/2dmYUKPXQjt
I don’t understand what you’ve posted.
The 2 images describe 2 different types of problems…
The first screen describes a GPU related problem, but I’m not sure how you could have gotten to that point (after selecting your kernel) if the second screen error happened (pretty sure that should have happened <before> or <immediately after> selecting a kernel in the GRUB menu. Or, maybe the first screen is attempting to boot normally and the second is attempting to boot in Emergency/Recovery Mode?
So,
I guess the main questions are
What are you upgrading from (what OS, OS version)?
What procedure did you follow attempting to upgrade?
What is your GPU?
PS - “Enterprise” approach to upgrading any kind of RAID is to do a full backup, then build a new “empty/default” machine, then restore your old files to the new machine… But the errors you posted don’t give me any hint you’ve run into a storage related problem… yet. Your problems are separate and before storage is an issue.
Hi Tsu, the two images above are errors that I recive upon the startup of the operating system (openSuSE 12.3). The errors appeared after a zypper dup command, the last time when I reinstalled my whole system was right after 12.1 was released and then I setup my 2 drives ( 1 TB ) into software raid 1, no problems sience then. I was running only openSuSE from 10.2 until the latest 12.3, no other OS were installed on the computer.
So what I did next: I tryed to boot up with 12.2 as Carlos suggested but with no luck the same error appeared on Live KDE, then I booted with 12.1 Live KDE and the system started up, I was able to read and write into the /, /home partitions, so I decided to replace the 12.3 with 12.1 and see if I can do a backup of my data (400GB+). The installation went OK, I was able to finish it but right after the first reboot the booting process stoped asked for the root password, the system was unable to mount the /home partition, then I executed e2fsck -b 8193 /dev/md1. So eveytime that i booted up the system the same problem with the mount of the /home partition. Now I run a surface test of the hard drives ( the first one is OK, and the second one just reached 380GB tested and it is ok ). I will let you know if the drives are ok. As I said the ram is ok, the video test went ok. So my only conclusion is that the ext4 filesystem has broken for unknow reason.
The surface tests went ok and the drives have no bad sectors.
Running the command ***fdisk -l *** gives me this:
linux-8xwg:/home/ovidiu # fdisk -l
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xd72dd72d
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 31455231 15726592 fd Linux raid autodetect
/dev/sda2 31455232 1949327359 958936064 fd Linux raid autodetect
/dev/sda3 1949327360 1953523711 2098176 fd Linux raid autodetect
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00097cd3
Device Boot Start End Blocks Id System
/dev/sdb1 * 2048 31455231 15726592 fd Linux raid autodetect
/dev/sdb2 31455232 1949327359 958936064 fd Linux raid autodetect
/dev/sdb3 1949327360 1953523711 2098176 fd Linux raid autodetect
Disk /dev/sdc: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xda22da22
Device Boot Start End Blocks Id System
/dev/sdc1 2048 156301311 78149632 83 Linux
Disk /dev/md0: 16.1 GB, 16103956480 bytes
2 heads, 4 sectors/track, 3931630 cylinders, total 31453040 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/sdd: 499.8 GB, 499844669440 bytes
255 heads, 63 sectors/track, 60769 cylinders, total 976259120 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x08607e59
Device Boot Start End Blocks Id System
/dev/sdd1 63 976249951 488124944+ 7 HPFS/NTFS/exFAT
Disk /dev/md2: 4296 MB, 4296998912 bytes
2 heads, 4 sectors/track, 1049072 cylinders, total 8392576 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 32768 bytes / 65536 bytes
Disk identifier: 0x00000000
Disk /dev/md2 doesn't contain a valid partition table
Disk /dev/md1: 982.0 GB, 981950390272 bytes
2 heads, 4 sectors/track, 239733982 cylinders, total 1917871856 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/md1 doesn't contain a valid partition table
right now I was able to mount the partition manualy and I’m trying to copy my important data to an external drive.
I even did a video memory stress test and all 10 tests were successfully.
On 2013-06-16 15:26, morbidwar wrote:
>
> The surface tests went ok and the drives have no bad sectors.
> Running the command -*fdisk -l *- gives me this:
> Disk /dev/md0 doesn't contain a valid partition table
> Disk /dev/md2 doesn't contain a valid partition table
> Disk /dev/md1 doesn't contain a valid partition table
> --------------------
Hello Carlos, right now I finished to copy all my data to the external storage. It taked long because the system from time to time gave me errors. And if the copy folder exceeded 10GB the system hatled with error. But in the end every file was saved.
i will format the drives with low level format. But right now I will wait to see whos fault was. It was the kernel update, the software raid, the drives… a lot of questions rised after this incident.
Hello Carlos, well I will format the drives with low level because I want to be sure that the surface is OK, even if the surface test went OK with no errors. But I don’t understand why the kernel is “oopsing” is something wrong with my hardware? or the partition table isn’t ok on the disk? The software-raid was made during openSuSE installation, end everything went ok.
Thank you for your time and support.
Best regards
Ovidiu
So I come back with an update. After installing Debian on the same computer I noticed some strange errors in the /var/log/messages regarding memory module B0 and after a deep investigation I found out that one of my memory modules was broken and the correction module inside the memory was trying to repair the problems. The problem I clear now, but what I don’t understand why the file system was affected?
Thank you for your support.
Any memory problem is a real problem. Each OS uses memory in a different way so some may not run into the bad memory at first others may put an important system file flat at the bad memory thus breaking the program.
