Sponsored Content
Full Discussion: reading the hard drive
Top Forums UNIX for Advanced & Expert Users reading the hard drive Post 33957 by norsk hedensk on Monday 27th of January 2003 04:03:21 PM
Old 01-27-2003
what did you edit in the /etc/ directory? since you say your machine wont read the drive, 2 things come to mind, either, 1. you didnt shutdown the computer properly, resulting in a corrupt filesystem, or 2. you edited the file /etc/fstab and messed up your mount points.
if the case is number 2, then it shouldnt be too hard to fix, what OS are you running on the machine? if you bought it in a store, it might have come with a sort of "rescue disk" where you will boot from that floppy and you may be able to manually mount the drive and restore your /etc/fstab file. if its the first one, a corrupt filesystem, then fsuck (hopefully) would be able to clear things up when you boot the machine. what happens when you boot? provide more info including your OS and what exactly you did, and what happens when you try to boot, and we can help you better.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

currupted my hard drive

Hello, earlier tonight I was installing BETA version of Mandrake Linux 9.0 and I realised I needed to partition my drive. I tried making the partition within mandrake but ther wasnt an option within the mandrake setup. So i go into my WindowsXP and do the disk management option but there want a... (5 Replies)
Discussion started by: xcaliber
5 Replies

2. Linux

hard drive specs?

Does anybody know what command will bring up my harddrive and how much room is left on it? (13 Replies)
Discussion started by: byblyk
13 Replies

3. UNIX for Dummies Questions & Answers

Removing hard drive

Hi, Can someone answer to my question.I' totally new to Unix. What is the command for removing the hard drive from the system? Thanks a lot, Puja (2 Replies)
Discussion started by: pujathakral
2 Replies

4. UNIX for Dummies Questions & Answers

Trying to copy old hard drive to new hard drive.

:confused: ........I have a new hard drive and I need to copy ALL info from the old to the new. I would like to use the dd command. I know the command is as follows...... dd if=/dev/rdsk/c1t1d0s0 of=/dev/rdsk/???????? Where I have the question marks is the problem. How do I find out what the... (4 Replies)
Discussion started by: shorty
4 Replies

5. Filesystems, Disks and Memory

The best partitioning schem for a 250GB Sata hard drive & a 75GB SCSI hard drive

Hi I have 2 75GB SCSI hard drives and 2 250GB SATA hard drives which are using RAID Level 1 respectively. I wana have both FTP and Apache installed on them as services. I'm wondering what's the best partitioning schem? I wana use FC3 as my OS, so, I thought I can use the 75GB hard drive as the /... (0 Replies)
Discussion started by: sirbijan
0 Replies

6. Solaris

wiping hard drive

I'm looking for a utility that will wipe data clean from a Solaris hard drive and make the data unreadable and unrecoverable. Any suggestions? Does SUN have something? (3 Replies)
Discussion started by: dangral
3 Replies

7. Solaris

Using the rest of my hard drive

Hi When I installed opensolaris, I installed it on a 20GB partition. How do I make use of the other 300GB I have spare? format shows:- -bash-3.2# format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c3d0 <DEFAULT cyl 2607 alt 2 hd 255 sec 63> ... (12 Replies)
Discussion started by: hellotommy
12 Replies

8. Filesystems, Disks and Memory

mount old hard drive

Hi guys, I have been looking around and searching for the past hour and did not see anything. but please forgive me if I missed something. I had a sparc 10 ultra cpu die on me, I got a replacement server from a very generous guy here, now I am getting around to remounting my old hard drive with... (0 Replies)
Discussion started by: DrDarkMatter
0 Replies

9. Hardware

checking non sequential reading/writing of hard drive

what command check that? Does it depend in the time it take to access the file? (1 Reply)
Discussion started by: programAngel
1 Replies
SYSTEMD-FSTAB-GENERATOR(8)				      systemd-fstab-generator					SYSTEMD-FSTAB-GENERATOR(8)

NAME
systemd-fstab-generator - Unit generator for /etc/fstab SYNOPSIS
/lib/systemd/system-generators/systemd-fstab-generator DESCRIPTION
systemd-fstab-generator is a generator that translates /etc/fstab (see fstab(5) for details) into native systemd units early at boot and when configuration of the system manager is reloaded. This will instantiate mount and swap units as necessary. The passno field is treated like a simple boolean, and the ordering information is discarded. However, if the root file system is checked, it is checked before all the other file systems. See systemd.mount(5) and systemd.swap(5) for more information about special /etc/fstab mount options this generator understands. One special topic is handling of symbolic links. Historical init implementations supported symlinks in /etc/fstab. Because mount units will refuse mounts where the target is a symbolic link, this generator will resolve any symlinks as far as possible when processing /etc/fstab in order to enhance backwards compatibility. If a symlink target does not exist at the time that this generator runs, it is assumed that the symlink target is the final target of the mount. systemd-fstab-generator implements systemd.generator(7). KERNEL COMMAND LINE
systemd-fstab-generator understands the following kernel command line parameters: fstab=, rd.fstab= Takes a boolean argument. Defaults to "yes". If "no", causes the generator to ignore any mounts or swap devices configured in /etc/fstab. rd.fstab= is honored only by the initial RAM disk (initrd) while fstab= is honored by both the main system and the initrd. root= Takes the root filesystem to mount in the initrd. root= is honored by the initrd. rootfstype= Takes the root filesystem type that will be passed to the mount command. rootfstype= is honored by the initrd. rootflags= Takes the root filesystem mount options to use. rootflags= is honored by the initrd. mount.usr= Takes the /usr filesystem to be mounted by the initrd. If mount.usrfstype= or mount.usrflags= is set, then mount.usr= will default to the value set in root=. Otherwise, this parameter defaults to the /usr entry found in /etc/fstab on the root filesystem. mount.usr= is honored by the initrd. mount.usrfstype= Takes the /usr filesystem type that will be passed to the mount command. If mount.usr= or mount.usrflags= is set, then mount.usrfstype= will default to the value set in rootfstype=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrfstype= is honored by the initrd. mount.usrflags= Takes the /usr filesystem mount options to use. If mount.usr= or mount.usrfstype= is set, then mount.usrflags= will default to the value set in rootflags=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrflags= is honored by the initrd. systemd.volatile= Controls whether the system shall boot up in volatile mode. Takes a boolean argument or the special value state. If false (the default), this generator makes no changes to the mount tree and the system is booted up in normal mode. If true the generator ensures systemd-volatile-root.service(8) is run as part of the initial RAM disk ("initrd"). This service changes the mount table before transitioning to the host system, so that a volatile memory file system ("tmpfs") is used as root directory, with only /usr mounted into it from the configured root file system, in read-only mode. This way the system operates in fully stateless mode, with all configuration and state reset at boot and lost at shutdown, as /etc and /var will be served from the (initially unpopulated) volatile memory file system. If set to state the generator will leave the root directory mount point unaltered, however will mount a "tmpfs" file system to /var. In this mode the normal system configuration (i.e. the contents of "/etc") is in effect (and may be modified during system runtime), however the system state (i.e. the contents of "/var") is reset at boot and lost at shutdown. Note that in none of these modes the root directory, /etc, /var or any other resources stored in the root file system are physically removed. It's thus safe to boot a system that is normally operated in non-volatile mode temporarily into volatile mode, without losing data. Note that enabling this setting will only work correctly on operating systems that can boot up with only /usr mounted, and are able to automatically populate /etc, and also /var in case of "systemd.volatile=yes". SEE ALSO
systemd(1), fstab(5), systemd.mount(5), systemd.swap(5), systemd-cryptsetup-generator(8), kernel-command-line(7) systemd 237 SYSTEMD-FSTAB-GENERATOR(8)
All times are GMT -4. The time now is 08:27 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy