Mageia forum

My notebook with Mageia2 installed recently lost the mother board
wanting to test the HDD[500g], I used a sata to USB converter & plugged it in saw all the files no problem

I shut down my PC & plugged the HDD into the sata to IDE [pata] converter [the normal hdd is a full sized sata running through said converter]

I got an error message from bios, telling me I had a 64bit kernal & that it wasn't going to run on the 32 bit cpu
shut down plugged the original hdd back in, booted up no problem
connected HDD to USB converter
I can no longer see the home folder [SDB6]
I can see 12g of SDB1
the other 480g of HDD aren't visible
How do I regain access?

Garthhh wrote:How do I regain access?

first it is necessary to understand why it has been disappared

the command

Code: Select all

mount


shown which disks/partition are currently mounted

the file

Code: Select all

/etc/fstab


contains what the system will try to mount at boot time or later

the optput of the command

Code: Select all

dmesg

should tell a lot about your boot (better if you post only the relevant part)

mount

Code: Select all

[mlogar@localhost ~]$ mount
/dev/sda1 on / type ext4 (rw,commit=0)
none on /proc type proc (rw)
/dev/sda6 on /home type ext4 (rw,commit=0)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
gvfs-fuse-daemon on /home/mlogar/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=mlogar)
/dev/sdb1 on /media/e255c3bd-dd98-4d8a-8a26-d3dac332be80 type ext4 (rw,nosuid,nodev,uhelper=udisks)
[mlogar@localhost ~]$


I don't know what you consider relevant from dmesg?

Code: Select all

Actions configured
usb 1-5: USB disconnect, address 3
usb 1-5: new high speed USB device using ehci_hcd and address 4
usb 1-5: New USB device found, idVendor=14cd, idProduct=6116
usb 1-5: New USB device strings: Mfr=1, Product=3, SerialNumber=2
usb 1-5: Product: USB 2.0  SATA BRIDGE   
usb 1-5: Manufacturer: Super Top   
usb 1-5: SerialNumber: M6116018VF16
scsi3 : usb-storage 1-5:1.0
scsi 3:0:0:0: Direct-Access     ST950032 5AS                   PQ: 0 ANSI: 0
sd 3:0:0:0: Attached scsi generic sg2 type 0
sd 3:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
sd 3:0:0:0: [sdb] Write Protect is off
sd 3:0:0:0: [sdb] Mode Sense: 03 00 00 00
sd 3:0:0:0: [sdb] Assuming drive cache: write through
sd 3:0:0:0: [sdb] Assuming drive cache: write through
 sdb: sdb1 sdb2 < sdb5 sdb6 >
sd 3:0:0:0: [sdb] Assuming drive cache: write through
sd 3:0:0:0: [sdb] Attached SCSI disk
EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
usb 1-5: USB disconnect, address 4
Buffer I/O error on device sdb1, logical block 0
lost page write due to I/O error on sdb1
usb 1-6: new high speed USB device using ehci_hcd and address 5
usb 1-6: New USB device found, idVendor=0bc2, idProduct=2100
usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-6: Product: FreeAgent
usb 1-6: Manufacturer: Seagate
usb 1-6: SerialNumber: 2GE336NR
scsi4 : usb-storage 1-6:1.0
scsi 4:0:0:0: Direct-Access     Seagate  FreeAgent Go     102F PQ: 0 ANSI: 4
sd 4:0:0:0: Attached scsi generic sg2 type 0
sd 4:0:0:0: [sdb] 488397168 512-byte logical blocks: (250 GB/232 GiB)
sd 4:0:0:0: [sdb] Write Protect is off
sd 4:0:0:0: [sdb] Mode Sense: 1c 00 00 00
sd 4:0:0:0: [sdb] Assuming drive cache: write through
sd 4:0:0:0: [sdb] Assuming drive cache: write through
 sdb: sdb1
sd 4:0:0:0: [sdb] Assuming drive cache: write through
sd 4:0:0:0: [sdb] Attached SCSI disk
render error detected, EIR: 0x00000010
[drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking
render error detected, EIR: 0x00000010
sd 4:0:0:0: [sdb] Assuming drive cache: write through
 sdb: sdb1
usb 1-6: USB disconnect, address 5
usb 1-6: new high speed USB device using ehci_hcd and address 6
usb 1-6: New USB device found, idVendor=14cd, idProduct=6116
usb 1-6: New USB device strings: Mfr=1, Product=3, SerialNumber=2
usb 1-6: Product: USB 2.0  SATA BRIDGE
usb 1-6: Manufacturer: Super Top
usb 1-6: SerialNumber: M6116018VF16
scsi5 : usb-storage 1-6:1.0
scsi 5:0:0:0: Direct-Access     ST950032 5AS                   PQ: 0 ANSI: 0
sd 5:0:0:0: Attached scsi generic sg2 type 0
sd 5:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
sd 5:0:0:0: [sdb] Write Protect is off
sd 5:0:0:0: [sdb] Mode Sense: 03 00 00 00
sd 5:0:0:0: [sdb] Assuming drive cache: write through
sd 5:0:0:0: [sdb] Assuming drive cache: write through
 sdb: sdb1 sdb2 < sdb5 sdb6 >
sd 5:0:0:0: [sdb] Assuming drive cache: write through
sd 5:0:0:0: [sdb] Attached SCSI disk
EXT4-fs (sdb1): recovery complete
EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)

your /home is mounted from /dev/sda6,
you says it is in /dev/sdb6

is it correct?

in the past adding a disk was a probable cause of panic because sda
could be renamed into sdb,
but today the disk name is managed by UUID in /etc/fstab

tom_ wrote:your /home is mounted from /dev/sda6,
you says it is in /dev/sdb6

is it correct?

in the past adding a disk was a probable cause of panic because sda
could be renamed into sdb,
but today the disk name is managed by UUID in /etc/fstab

sdb6 is what I'm trying to access [there is a working home on sda6]

Garthhh wrote:
I don't know what you consider relevant from dmesg?

EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
usb 1-5: USB disconnect, address 4
Buffer I/O error on device sdb1, logical block 0
lost page write due to I/O error on sdb1
[...]
usb 1-6: USB disconnect, address 5
usb 1-6: new high speed USB device using ehci_hcd and address 6

Did you pull that disk out in the meantime, or what it plugged the whole time? That I/O error could be a sign that the drive is dieing.

I suppose anything is possible
it is quite a coincidence that the drive would have died as a result of trying to boot to it

Well, if a drive is damaged, any access, be it reading or writing to it can make it worse or so that you recognize it.
To check for hints about this, install gsmartcontrol and run it on that disk, it will give you some sensor data under the "Attributes" tab, please post that here.

Otherwise you should do something like scanning the drive with http://www.hdat2.com/ or with a diagnostic tool from the drive manufacturer.
For a seagate drive that would be Seatools. FWIW, both programs are contained on Hirens Bootdisk: http://www.hirensbootcd.org/download/