RHEL 4 not seeing ext3 label
-
Well
ddis moving right along.
I had to use their recovery CD to boot the hardware. It would not boot to any of my USB drives.
So that is
ddfrom RHEL 4. The USB disk it is writing to is formatted FAT. So a direct write puked at 4GB.The version of
spliton there only supports a size tag ofmat the largest. So I went with 650MB on the split to match what their normal process creates.
-
I'm monitoring the progress in console 2 (ctl+alt+f2) with
watch -n 1 "ls -lash /dd_manual/dd"
-
Process completed with no errors yesterday.
Now to merge it all back together and try to restore it to a VM.
-
It feels like I'm watching reality TV.
-
@JaredBusch said in RHEL 4 not seeing ext3 label:
Process completed with no errors yesterday.
Now to merge it all back together and try to restore it to a VM.
Do you need to merge it? just wondering?
-
@Dashrender said in RHEL 4 not seeing ext3 label:
Do you need to merge it? just wondering?
How else does it become a single disk image file to import into my hypervisor?
-
So back home, and I have the files backed up in like 4 places.
I recombined the .img files and then unzipped them.
Getting ready to setup a new VM on Proxmox, but I poked around
dmesgon the running system first.SCSI subsystem initialized Fusion MPT base driver 3.02.73rh Copyright (c) 1999-2006 LSI Logic Corporation Fusion MPT SPI Host driver 3.02.73rh ACPI: PCI Interrupt 0000:02:05.0[A] -> GSI 34 (level, low) -> IRQ 201 mptbase: Initiating ioc0 bringup ioc0: 53C1030: Capabilities={Initiator,Target} scsi0 : ioc0: LSI53C1030, FwRev=01032300h, Ports=1, MaxQ=255, IRQ=201 ACPI: PCI Interrupt 0000:02:05.1[B] -> GSI 33 (level, low) -> IRQ 209 mptbase: Initiating ioc1 bringup ioc1: 53C1030: Capabilities={Initiator,Target} scsi1 : ioc1: LSI53C1030, FwRev=01032300h, Ports=1, MaxQ=255, IRQ=209 Fusion MPT SAS Host driver 3.02.73rh megaraid cmm: 2.20.2.6rh (Release Date: Tue Jan 16 12:35:06 PST 2007) megaraid: 2.20.4.6-rh2 (Release Date: Wed Jun 28 12:27:22 EST 2006) megaraid: probe new device 0x1000:0x1960:0x1028:0x0518: bus 9:slot 4:func 0 ACPI: PCI Interrupt 0000:09:04.0[A] -> GSI 106 (level, low) -> IRQ 233 megaraid: fw version:[351S] bios version:[1.10] scsi2 : LSI Logic MegaRAID driver scsi[2]: scanning scsi channel 0 [Phy 0] for non-raid devices Vendor: PE/PV Model: 1x6 SCSI BP Rev: 1.0 Type: Processor ANSI SCSI revision: 02 scsi[2]: scanning scsi channel 1 [Phy 1] for non-raid devices scsi[2]: scanning scsi channel 2 [virtual] for logical drives Vendor: MegaRAID Model: LD 0 RAID1 69G Rev: 351S Type: Direct-Access ANSI SCSI revision: 02 SCSI device sda: 143114240 512-byte hdwr sectors (73274 MB) sda: asking for cache data failed sda: assuming drive cache: write through SCSI device sda: 143114240 512-byte hdwr sectors (73274 MB) sda: asking for cache data failed sda: assuming drive cache: write through sda: sda1 sda2 sda3 Attached scsi disk sda at scsi2, channel 2, id 0, lun 0 Vendor: MegaRAID Model: LD 1 RAID5 139G Rev: 351S Type: Direct-Access ANSI SCSI revision: 02 SCSI device sdb: 286228480 512-byte hdwr sectors (146549 MB) sdb: asking for cache data failed sdb: assuming drive cache: write through SCSI device sdb: 286228480 512-byte hdwr sectors (146549 MB) sdb: asking for cache data failed sdb: assuming drive cache: write through sdb: sdb1 Attached scsi disk sdb at scsi2, channel 2, id 1, lun 0I think this tells me that I should try the megaRAID controller this time. I swaer I already tried. But I have slept since then. Tuesday and Wednesday were crazy stressed getting data..
-
Well damnit. It does not see the second disk..
Looks like an error during boot
-
can you boot from a live image and see both disks?
I did a d2vm of a windows 2003 server and I had to run checkdisk like 10 times before it finally worked.. don't ask my why I tried it so many times... I think there is a thread around here somewhere about it.
-
@Dashrender said in RHEL 4 not seeing ext3 label:
can you boot from a live image and see both disks?
I did a d2vm of a windows 2003 server and I had to run checkdisk like 10 times before it finally worked.. don't ask my why I tried it so many times... I think there is a thread around here somewhere about it.
The restored drives are fine. Can be mounted as previously noted and the label reports correctly.
The issue seems to be that the kernel, as built, is not loading the drives correctly. Potentially because the VM is using a SCSI driver method the old ass kernel does not understand.
-
Didn't Dell "back in the day" use or require their own megaraid driver's on Linux?? Can't remember as its been ages since I delt with a 28XX series with a PERC raid card.
-
Using VirtIO SCSI (the default selection) the drives are not even seen by tthe recovery boot image. The onyl thing shown is the USB drive holding the data to restore.
-
Using VMWare PVSCSI the system won't even boot.
-
VirtIO SCSI Single is the same as VirtIO SCSI
-
The LSI 53C895A shows the drives, so attempting a restore..
Note: Even though it says "Default" this is not the default choice when you go through the wizard, VirtIO SCSI is the default selection.
-
Here is a video of the physical server booting. You can see the drives coming online at the 1:56 mark
-
@JaredBusch said in RHEL 4 not seeing ext3 label:
The LSI 53C895A shows the drives, so attempting a restore..
Note: Even though it says "Default" this is not the default choice when you go through the wizard, VirtIO SCSI is the default selection.
So the restore completed, but no boot drive detected I guess.
-
@JaredBusch or because I am getting cross eyed and did not notice that scsi0 was not selected in the boot order....
Fixed that.. Label not found.
-
CentOS 4.8 booting to rescue mode
The labels show as being correct.
-
This guy had a similar issue. he was moving from VMWare (old) instead of Physical to KVM.
https://serverfault.com/questions/1040265/cannot-migrate-ancient-vmBut his non-answer does not help.
Also, it appears my
scsi_modis loading first. so not the same issue he had.
