Hot answers tagged sata
12
Depending on your SATA driver and your distribution's configuration, they might show up as /dev/hda and /dev/hdb, or /dev/hda and /dev/sda, or /dev/sda and /dev/sdb. Distributions and drivers are moving towards having everything hard disk called sd?, but PATA drivers traditionally used hd? and a few SATA drivers also did.
The device names are determined by ...
6
You write to the disk (/dev/sdb), not to the file system you created (/dev/sdb1).
Since an ISO image already contains a file system (which you don't want) you can simply mount the ISO (with option -o loop) and copy the data to /dev/sdb1. That way the file system is preserved.
6
Naturally, you need to unmount any filesystems on the disk, and it'd be a good idea to deactivate any LVM groups (vgchange -an), and generally make sure nothing is using the disk for anything.
Once you've done that, it should be safe to unplug. If you want to be extra cautious, do echo 1 > /sys/block/(whatever)/device/delete first. That'll unregister ...
6
They show up as SCSI devices because the drivers speak SCSI to the next kernel layer (the generic disk driver). This isn't actually true of all SATA drivers on all kernel versions with all kernel compile-time configurations, but it's common. Even PATA devices can appear as SCSI at that level (again, that depends on the kernel version and kernel compile-time ...
5
To see the device description for the controller (assuming an internal (PCI) controller), which usually contains SATA for SATA controllers:
lspci -d $(cat /sys/block/sda/device/../../../vendor):$(cat /sys/block/sda/device/../../../device)
If you want to type less, just browsing the output of lspci is likely to give you the answer in a laptop (many desktop ...
4
I puzzled a bit around what would be the enumeration scheme on my systems and I've came up with following algorithm:
The /dev/sdY devices are created in the same order as the ataX identifiers are enumerated in the kern.log while ignoring non-disk devices (ATAPI) and not-connected links.
Thus, following command displays the mapping:
$ grep '^May 28 2' ...
3
Those two sections are for different things.
The first is for unplugging. The second is for plugging.
For unplugging, the OS will sync the data during the unmount operation. Thus, if the disk is unmounted (assuming you in fact do have full hardware support) you can power off the disk then unplug it without risk of data loss or corruption.
For plugging, ...
2
I don't see any points on doing so, you want a Volume Group that contains both SATA and SSD, that's possible.
Just create multiple PVs, with pvcreate /dev/partition_name
And create a volume group that use those PVs, with vgcreate
And do the partition of that VG.
2
The default order in which sda, sdb, sdc are assigned is unpredictable. But it can be overridden through udev. You can control the name of the block device files by adding directives in /etc/udev/rules.d/local.rules (some (older?) systems may only support /etc/udev/rules.conf). Better, you can add directives to create symbolic links, and use those symbolic ...
2
To answer the first question: Yes
But anyway, it should be easy to generate a backup entry in your boot manager (with the original initrd and working kernel), in case something goes wrong.
To answer the second one - you can use
$ lsmod
Module Size Used by
...
On your running systems to see, if ata_generic is loaded and if it is, which ...
2
That's not what dd is for and that's not how dd works. If you want the contents of the ISO then you can loopback mount it and copy the individual files.
However, you seem to be wanting to copy the contents of the Ubuntu installer onto a hard disk that presumably you'll want to boot from. Again, that's not how it works.
Optical disks (CD/DVD) use the ISO ...
2
Here's my version, modified from above. Since I don't know the exact date the system was booted (for testing this it was 27 days ago), and I don't know which kern.log contains the data I need (some may be gzipped on my system), I use uptime and date to calculate an approximate system boot date (to the day, anyway), then use zgrep to search through all ...
1
I assume your laptop has a CDROM drive. If so, could you install your netbook's drive in your laptop (as opposed to connecting it via USB) and then install Ubuntu on it. After that put it back in your netbook.
Not sure how dependent an Ubuntu installtion is on the actual hardware so you might need to do something after the drive is back in the netbook to ...
1
As a rule of thumb, always turn off fakeraid (RAID which is declared in the BIOS but actually performed by an OS driver). Fakeraid only exists for two reasons:
because some OSes have no native RAID capabilities and need some external assistance;
because it lets hardware manufacturers advertise a feature that they aren't really implementing.
There is no ...
1
There are two indications from this output that it is. First it indicates that the driver is in use(sata_via). The second is that it says what kind of card it is after the PCI address in the first line. If the driver is not loaded properly it'll say something like "Unknown Device ID 4000x288...".
1
Update: For the record, @Giles answer is better.
If it's a PATA (ide) drive, then you will see it under /proc/ide. Here is my IDE DVD-Drive, for example.
$ cat /proc/ide/hdb/model
Optiarc CDRWDVD CRX890A
If it is a SATA drive, it will show up under /proc/scsi. You might be surprised to find it under 'scsi'. I forget the exact reason (I'm going to ask ...
1
If I'm understanding your question correctly, the first parallel ATA hard drive under Linux will be /dev/hda, the second will be /dev/hdb, followed by /dev/hdc, etc.
Serial ATA devides will show up the same way SCSI and USB devices do: /dev/sda will be the first one, followed by /dev/sdb, /dev/sdc/, etc.
Only top voted, non community-wiki answers of a minimum length are eligible
