- Convert sata to IDE/VIRTIO
- Kamyk
- m.ardito
- Kamyk
- m.ardito
- Kamyk
- m.ardito
- m.ardito
- jmar83
- Linux Mint Forums
- SATA controller to IDE hard drives not recognized
- SATA controller to IDE hard drives not recognized
- Re: SATA controller to IDE hard drives not recognized
- Re: SATA controller to IDE hard drives not recognized
- Re: SATA controller to IDE hard drives not recognized
- Re: SATA controller to IDE hard drives not recognized
Convert sata to IDE/VIRTIO
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
Kamyk
New Member
I have a lot of VM’s with Linux systems on them. Somebody created SATA like a disk and i have problem with migrate it from one node to other. With IDE/VIRTIO i don’t have that problem.
How can i change SATA to IDE for example without reinstall system?
Thank you for help and answer.
m.ardito
Active Member
you just have to «reconnect» the existing disks. through the web gui or perhaps editing the config files.
Then each VM must be stopped and started (not just restarted).
Kamyk
New Member
What do you mean reconnect? I can only remove it, but i will lost all data there. How can i change it in linux env.?
m.ardito
Active Member
no, if you simply remove a connected disk it will be listed as «unused».
only removing an «unused» disk really destroys data.
you can «edit» the unused disk and reconnect changing channel type and number, as well as other settings.
note: if you’re testing, backup the vm (with all disks) first.
Kamyk
New Member
Sorry for that questions: but how can i do it? In Proxmox GUI i can go to VM and next Hardwer. And click on disk and i have only: Add / Remove / Edit / Resize / Move / Throttle. If i use Remove i will remove disk. There is nothing like Unused.
m.ardito
Active Member
no, if you click «remove» the disk will not be «destroyed», it will be listed below, as «unused», as I said above.
perhaps that label button could be changed to «detach» or «disconnect», when an used disk is selected, as this is what it does.
and perhaps it should be «destroy» on a «detached» (unused) disk, just to be more clear.
[edit]
when you click «remove» on a used disk you get a confirm request saying «Are you sure you want to remove entry ‘Hard Disk (ide0)'»
when you click «remove» on an unused disk you get a confirm request saying «Are you sure you want to remove entry ‘Unused Disk 0’ This will permanently erase all image data.»
m.ardito
Active Member
anyway, for completeness’s sake I just tested:
in the vm conf file, say /etc/pve/qemu-server/700.conf
you can simply change the channel type and save, eg: from
and after stop+start it works, but remember to change boot disk info there or in the web gui!
because the boot order is specified through channel type+order, like
in the example above change this line also to
otherwise your vm could be unable to boot.
jmar83
Active Member
«no, if you simply remove a connected disk it will be listed as «unused».
only removing an «unused» disk really destroys data.
you can «edit» the unused disk and reconnect changing channel type and number, as well as other settings.»
That is COMPLETELY wrong!! I’ve disconnected (remove a used disk) which will results a unused disk will be leaved.
A «re-connecting» of that unused disk with a new controller type (sata, virtio, scsi) will result in a blue screen or system recovery (depends from the used option of controller type) in my Windows Server 2008 R2.
Now i need to reinstall because of that.
The proxmox version i use is Virtual Environment 4.4-1/eb2d6f1e and a linux 4.8.0 kernel.
Linux Mint Forums
SATA controller to IDE hard drives not recognized
Forum rules
There are no such things as «stupid» questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.
SATA controller to IDE hard drives not recognized
Post by foxonly » Mon May 04, 2015 9:14 pm
I’M A BIKER AND NOT A TECHNO GEEK.
NEW TO LINUX, SO PLEASE. DETAILS. NO ASSUMPTIONS THAT I UNDERSTAND HOW TO NAVIGATE.
RESPOND BACK TO ME AS IF YOU ARE EXPLAINING TO A COMPUTER IGNORANT BIKER DUDE.
Linux Mint 17.1 Fresh Install
18 year old system with 266GHz Pentium 4 with max memory of 2GB, 533 BUS, nVidia graphics card with 1GB memory
Five stack dumb tower RAID RACK filled with FOUR (04) 160GB IDE hard drives and powered with its own 460 PSU
Intended setup is for a JBOD. NOT setting up as a RAID at this time.
Each hard drive is connected to a StarTech Bi-Directional SATA/IDE Adapter Converter and a SATA cable from each converter to a StarTech 4 Port PCI SATA RAID Controller Adapter (interface board) Card having four SATA connections on board.
I have tried every combination thereof of DIP switch settings and jumper pin settings on the hard drives, following both the hard drive manufacturer and SATA/IDE Adapter Converter manufacturer directions, and then some, to absolutely no avail.
Can’t access the interface card built in BIOS until the card and drives are recognized, and so that does nothing for me.
StarTech tells me to input dmesg | grep il and/or lspci | grep sil to ensure recognition, but when I input dmesg | grep il, I get the following message.
Anyone? Anyone? Bueller? Bueller?
[ 61.958638] WARNING: CPU: 0 PID: 23 at /build/buildd/linux-3.13.0/arch/x86/kernel/check.c:140 check_for_bios_corruption+0xbe/0xd0()
[ 508.925886] init: upstart-file-bridge main process (443) terminated with status 1
[ 508.925911] init: upstart-file-bridge main process ended, respawning
[ 923.650803] init: smbd main process (633) killed by TERM signal
[ 4686.727326] EXT4-fs (sdb): mounted filesystem with ordered data mode. Opts: (null)
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reorx Level 12
Posts: 4041 Joined: Tue Jul 07, 2009 7:14 pm Location: SE Florida, USA
Re: SATA controller to IDE hard drives not recognized
Post by Reorx » Mon May 04, 2015 9:30 pm
First — IGNORANT BIKER DUDES shouldn’t try to use Linux — it’s beyond them.
Second — you are clearly not an ignorant biker «dude».
Third — I fear that some of your 18 year old hardware is suffering from «no longer supported» in modern Linux kernels therefore I think that you may not be able to get any version of Mint to run on your hardware. If you want to try anyway, use Mint 13 XFCE. I have had best luck with distros specifically designed for old, anemic (by today’s standards) systems. You might consider LXLE or Peppermint OS.
Full time Linux Mint user since 2011 — Currently running LM21C on multiple Dell laptops — mostly Vostro models.
Re: SATA controller to IDE hard drives not recognized
Post by Mute Ant » Tue May 05, 2015 5:21 am
o A 2.66GHz Pentium 4 dates the motherboard August 2002 or later you are not as old as you thought.
o The PATA drive jumper(s) [Master|Slave|CS] are for two devices on one cable, where CS is the safe bet. If you have only one device on a cable you want ‘Single’ or ‘Master’.
o You can install Mint to a PATA drive connected directly to the motherboard and appearing as /dev/sda for example. Then power-off and try the same drive connected via PCI-SATA-PATA, where it should still appear as /dev/sda/ Linux can’t see the wires, just the signals.
o You are supposed to be able to boot from a single SATA drive attached to the PCI adaptor; no OS at all, just the BIOS and the PCI card. Get that to work and I think the rest will follow.
o If the BIOS can’t offer the PCI-SATA card as a boot device, the last resort is to consider the BIOS version you have and the most recent BIOS available. Has the manufacturer made any relevant changes?
Re: SATA controller to IDE hard drives not recognized
Post by foxonly » Tue May 05, 2015 11:10 am
Reorx wrote: First — IGNORANT BIKER DUDES shouldn’t try to use Linux — it’s beyond them.
Second — you are clearly not an ignorant biker «dude».
Third — I fear that some of your 18 year old hardware is suffering from «no longer supported» in modern Linux kernels therefore I think that you may not be able to get any version of Mint to run on your hardware. If you want to try anyway, use Mint 13 XFCE. I have had best luck with distros specifically designed for old, anemic (by today’s standards) systems. You might consider LXLE or Peppermint OS.
«. therefore I think that you may not be able to get any version of Mint to run on your hardware. » I’m thinking you may be misunderstanding my issue. The hardware runs any kind of Ubuntu or Linux OS I throw at it, save a slight issue it has with the nVidia board and drivers. Aside from that, the Mint OS runs fine. It’s not the OS I am having the problem with. It’s the OS’s ability to recognize the four SATA cables to the four SATA to IDE adapters, each one attached to the hard drives.
As for lighter distros, I was under the distinct impression that Mint was considered on the lighter side of the many thousands of them out there.
And yes. I AM an ignorant biker and have been since ’67. But that’s not the issue. Why shouldn’t virtually anyone with the heart honestly and fairly be able to try their hand at something? If things in life were meant only for the ‘upper crust, white collard’, or similarly thereof, then you’re speaking of a limited two tier society, and anyone of intelligence knows through the study of history where THAT ends up.
In any event, I know the JBOD can work with this setup. I’m just missing something, which is why I came here to pick some brains in the first place. Afterall, that IS why I AM just a dumb ‘ol biker dude. An ‘ol graybeard as they are called.
Re: SATA controller to IDE hard drives not recognized
Post by foxonly » Tue May 05, 2015 11:38 am
Mute Ant wrote: o A 2.66GHz Pentium 4 dates the motherboard August 2002 or later you are not as old as you thought.
o The PATA drive jumper(s) [Master|Slave|CS] are for two devices on one cable, where CS is the safe bet. If you have only one device on a cable you want ‘Single’ or ‘Master’.
o You can install Mint to a PATA drive connected directly to the motherboard and appearing as /dev/sda for example. Then power-off and try the same drive connected via PCI-SATA-PATA, where it should still appear as /dev/sda/ Linux can’t see the wires, just the signals.
o You are supposed to be able to boot from a single SATA drive attached to the PCI adaptor; no OS at all, just the BIOS and the PCI card. Get that to work and I think the rest will follow.
o If the BIOS can’t offer the PCI-SATA card as a boot device, the last resort is to consider the BIOS version you have and the most recent BIOS available. Has the manufacturer made any relevant changes?
You are correct. The system is from May 2004. I have no idea how I got 17 years. Elevator gets stuck now and again at my age. Thanks for that. So then, the ‘computer’ is ‘you are not as old as you thought’. Just wish I could say the same for me! LOL
As for the jumpers, yes, I do understand they are for two drives on one cable, and yes, the current setup does in fact have a single SATA cable from the interface card to one each on each hard drive, while those jumpers are also set to Master. (No where that I see do they use the term Single) To be noted: There is a SATA to IDE converter sandwiched in between to make that leap from SATA to IDE, and each is powered and has DIP switches, while each are set to Master/Single as both the instructions and manufacturer state.
_____________________________________________________________________________
JUST DISCOVERED problem. Interface card was not completely seated, and I didn’t notice it because it was so slightly not pushed all the way in that looking at it one would never think of it not making contact. Just goes to ‘lern’ me somphin’
I know we are supposed to write SOLVED somewhere in the forum, but I don’t understand the structure and how and where to go for that. If someone could do that for me and it’s allowed, I would appreciate it very much. Thank you all.
«You are supposed to be able to boot from a single SATA drive attached to the PCI adapter; no OS at all». I have to think about that one. it means moving physical hardware and cables around, and I’m thinking that to be a last resort. But thank you very much for that insight.
Also, you are correct in stating the ability to use the SATA to be able to boot to. But therein lies the issue. I can not get to the SATA BIOS UNTIL the interface card and at least one attached hard drive are working. So it’s a catch 22 for me right now.
The system is a Dell Dimension 2400 tower and has had the latest BIOS for years now. That last update for this thing was years ago. And the BIOS doesn’t exactly offer a plethora of options either in my humble opinion.
It’s something relatively simple. I know it. I can just feel it. But as my computer ignorance hampers me, not to mention my complete ignorance with Linux, that doesn’t help me much either. Thanks for you input. Very much appreciated guy.